| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Allows for links to work both on systemd.io (or forks) and
when viewed on https://github.com/systemd/systemd/tree/main/docs
Note that the markdown links are converted by jekyll-relative-links[1]
to html. This plugin is enabled by default on github pages[2][3].
Due to a bug in jekyll-relative-links – see
https://github.com/benbalter/jekyll-relative-links/issues/61 –
we need to avoid line-wrapped links when using relative markdown links.
[1] https://github.com/benbalter/jekyll-relative-links
[2] https://github.blog/2016-12-05-relative-links-for-github-pages/
[3] https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll#plugins
|
|
|
|
|
| |
Fix typos and improve the language by
adding a few commas and a missing word.
|
| |
|
| |
|
| |
|
|\
| |
| | |
homed: report actual home dir access mode and fs type in effect
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
| |
backend
This is useful since certain shares can only be mounted with additional
mount flags. For example the SMB share in modern AVM Fritz!Boxes
requires "noserverino" to be set to work from Linux.
|
|
|
|
|
|
|
|
|
|
| |
Allow specifying CIFS services in the format //host/service/subdir/… to
allow multiple homedirs on the same share, and not in the main dir of
the share.
All other backends allow placing the data store at arbitrary places,
let's allow this too for the CIFS backend. This is particularly useful
for testing.
|
|
|
|
|
|
| |
I have no idea if this is going to cause rendering problems, and it is fairly
hard to check. So let's just merge this, and if it github markdown processor
doesn't like it, revert.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This catches up homed's FIDO2 support with cryptsetup's: we'll now store
the uv/up/clientPin configuration at enrollment in the user record JSON
data, and use it when authenticating with it.
This also adds explicit "uv" support: we'll only allow it to happen when
the client explicity said it's OK. This is then used by clients to print
a nice message suggesting "uv" has to take place before retrying
allowing it this time. This is modelled after the existing handling for
"up".
|
| |
|
| |
|
|
|
|
| |
Also, explain GECOS syntax requirements.
|
| |
|
|
|
|
|
| |
This is confusing because the reader might think that processes and threads are
counted separately. Another issue pointed out in #16363.
|
| |
|
| |
|
|
|
|
|
|
|
| |
We'd like to use it for FIDO2 tokens too, and the concept is entirely
generic, hence let's just reuse the field, but rename it. Read the old
name for compatibility, and treat the old name and the new name as
identical for most purposes.
|
|
|
|
| |
Fixes: #16172
|
| |
|
|
|
|
|
| |
We have so many different docs on various facets of user/group stuff,
let's add our own category for it.
|
|
|
|
|
| |
(Also correct the set of names we accept in User=, which was forgotten
to be updated in ae480f0b09aec815b64579bb1828ea935d8ee236.
|
| |
|
|
|
|
|
|
| |
I assume it’s supposed to be “see Home Directories for details” and not
“… and embeds these JSON records directly in the home directory images …
for details”, but the previous text suggested the latter reading to me.
|
| |
|
|
|
| |
fixes formatting in the last paragraph of the 'General Structure' chapter.
|
|
|
|
|
|
| |
fix 2 more broken links.
GROUP_RECORD now points to https://systemd.io/GROUP_RECORD/ and
USER_GROUP_API to https://systemd.io/USER_GROUP_API/
|
|
|