| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Allows the system administrator to configure what fields the user is
allowed to edit about themself, along with hard-coded defaults.
|
| | |
|
| |
|
|
|
|
|
| |
These will be used by display managers to pre-select the user's
preferred desktop environment and display server type. On homed, the
display manager will also be able to set these fields to cache the
user's last selection.
|
| |
|
|
|
|
| |
These fields are used to connect a JSON user record to its blob
directory, and to include the directory's contents in the record's
signature
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This field is like preferredLanguage, but takes a priority list of
languages instead. If an app isn't translated into a user's primary
language, it can fall back to one of the other languages in the list
thus making the app more accessible to the user.
For instance: in my experience, many Ukrainians are fluent in Russian,
often significantly better than English (especially if they are of a
generation that grew up during the USSR). Such a person might set this
new variable to ["uk_UA.UTF-8", "ru_UA.UTF-8"] so that software that
lacks Ukrainian translations will first try Russian translations before
defaulting to English.
Fixes #31290
|
| |
|
|
|
| |
In particular the ambieht caps field is useful: we can use it later to
pass caps such as CAP_WAKE_ALARM to regular users on login.
|
| | |
|
| | |
|
| |
|
|
| |
Signed-off-by: wineway <wangyuweihx@gmail.com>
|
| |
|
|
| |
This also avoids multiple evaluations in STRV_FOREACH_BACKWARDS()
|
| |
|
|
|
| |
(#21308)
userdbctl: fix "Password OK" shown even when password is empty or locked
|
| | |
|
| | |
|
| |
|
|
|
|
| |
user record field
Fixes: #15120
|
| |
|
|
| |
Follow-up for 4c2ee5c7f26fda41d7eb1250c61c85cc869a90de
|
| | |
|
| |
|
|
|
| |
These are not defined by us, but are defined as proper UUIDs by their
respective specs, hence show them as such.
|
| |
|
|
| |
Fixes: #20857
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The RTC is like just off, it's a weird system state, let's continue
without requiring pw change.
|
| |
|
|
|
| |
This might happen if the system clock is wrong, and we should allow
access in this case (though certainly log about it).
|
| |
|
|
|
| |
It is natural to include both, and in total they declared three
functions. Let's merge them for simplicity.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We make this entirely independent of the regular discard field, i.e. the
one that controls discard behaviour when the home directory is online.
Not all combinations make a ridiculous amount of sense, but most do.
Specifically:
online-discard = yes, offline-discard = yes
→ Discard when activating explicitly, and during runtime using
the "discard" mount option, and discard explicitly when logging
out again.
online-discard = no, offline-discard = yes
→ The new default: when logging in allocate the full backing
store, and use no discard while active. When loging out discard
everything. This provides nice behaviour: we take minimal storage
when offline but provide allocation guarantees while online.
online-discard = no, offline-discard = no
→ Never, ever discard, always operate with fully allocated
backing store. The extra safe mode.
|
| | |
|
| |
|
