| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes: #28982
|
|
|
|
|
|
|
|
| |
As I noticed a lot of missing information when trying to implement checking
for missing info. I reimplemented the version information script to be more
robust, and here is the result.
Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
|
|
|
|
|
|
|
|
| |
This tries to add information about when each option was added. It goes
back to version 183.
The version info is included from a separate file to allow generating it,
which would allow more control on the formatting of the final output.
|
|
|
|
|
|
| |
The article "a" goes before consonant sounds and "an" goes before vowel
sounds. This commit changes an to a for UKI, UDP, UTF-8, URL, UUID, U-Label, UI
and USB, since they start with the sound /ˌjuː/.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Fixes #22966. Since there are competing conventions, let's not
change our code, but make the docs match what is implemented.
|
|
|
|
|
| |
* Some authenticators(like Yubikey) support credential algorithm other than ES256
* Introduce a new option so users can make use of it
|
|
|
|
| |
Fixes #22432.
|
|
|
|
|
| |
Let's add an explicit, synchronous command to request immediate rebalancing and
wait for it.
|
| |
|
|
|
|
| |
The code and --help text got this right, hence fix the man page
|
|\
| |
| | |
homed: also support minimizing/maximizing home dirs when creating them
|
| | |
|
|/ |
|
|
|
|
|
| |
* man: document FIDO2 device removal
Indicate to users how to remove FIDO2 device in the --fido2-device=path section by setting path to an empty string (""). Tested on systemd 249 (249.6-3-arch)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Fixes: #20857
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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".
|
|
|
|
|
| |
The usual: the test wasn't testing, so we didn't notice that the
command wasn't returning as expected.
|
|
|
|
| |
Some are not about less, e.g. $SYSTEMD_URLIFY.
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes #17177.
|
|
|
|
|
|
|
| |
"keyed by" is indeed a bit jargony. Say " a HMAC hash of the salt combined with
an internal secret key" instead.
For #17177.
|
|\
| |
| | |
Fix links in man pages
|
| |
| |
| |
| | |
As usual, linkchecker ftw!
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Let's explicitly deactivate all home dirs on shutdown, in order to
properly synchronizing unmounting and avoiding blocking devices.
Previously, we'd rely on automatic deactivation when home directories
become unused. However, that scheme is asynchronous, and ongoing
deactviations might conflicts with attempts to unmount /home. Let's fix
that by providing an explicit service systemd-homed-activate.service
whose only job is to have a ExecStop= line that explicitly deactivates
all home directories on shutdown. This service can the be ordered after
home.mount and similar, ensuring that we'll first deactivate all homes
before deactivating /home itself during shutdown.
This is kept separate from systemd-homed.service so that it is possible
to restart systemd-homed.service without deactivating all home
directories.
Fixes: #16842
|
|
|
|
| |
This is almost all of #17177.
|
|
|
|
|
|
|
|
|
|
|
| |
Also, reword the description a bit. "As a string" is meaningless in the context
of commandline arguments, where evyrything is a string. This is not a
strongly-typed programming language where 5 is a number but "5" is something
completely different. Here both 5 and "5" are indistinguishable. The original
text was trying to say that a location name should be given and not a number,
so say "time zone location name".
For #17177.
|
|
|
|
|
|
|
|
|
|
|
|
| |
--image-path=/dev/some-block-device is not supported
The directory backend needs a file system path, and not a raw block
device. That's only supported for the LUKS2 backend.
Let's make this clearer in the man page and also generate a better error
message if attempted anyway.
Fixes: #17068
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently both Fedora and suse default to btrfs now, it should hence be
good enough for us too.
This enables a bunch of really nice things for us, most importanly we
can resize home directories freely (i.e. both grow *and* shrink) while
online. It also allows us to add nice subvolume based home directory
snapshotting later on.
Also, whenever we mention the three supported types, alaways mention
them in alphabetical order, which is also our new order of preference.
|
| |
|
|
|
|
|
| |
This is confusing because the reader might think that processes and threads are
counted separately. Another issue pointed out in #16363.
|
|
|
|
| |
Also from #16363.
|
|
|
|
| |
Fixes #16363. Also includes some changes where I generalized the pattern.
|
|\
| |
| | |
add fido2 authentication support to homed
|
| | |
|
|/ |
|
|
|
|
|
| |
Currently the manual doesn't clearly say whether `homectl update username -G group` will append the group to the user, or overwrite the list and remove user from the groups that aren't specified.
Fix this by updating the manual, basing the change on the usermod manual.
|
| |
|
| |
|
|
|
|
|
|
| |
Based on a report from Fossies.org using Codespell.
Followup to #15436
|