| Age | Commit message (Collapse) | Author |
|---|
|
|
|
ask-password: do no print password when storing in keyring
|
|
keymap fixes
|
|
systemd-ask-password can store passwords in kernel keyring. However it
uses to print the passwords to standard output nevertheless. Depending
on where systemd-ask-password is called passwords may end on display
or in log, leaking sensitive information.
This allows to make systemd-ask-password quiet, effectively disabling
printing passwords to standard output.
|
|
Apparently the vendor string for newer models now uses "svnHP" instead of
"svnHewlett-Packard", so add this alternative match to the global HP map.
Generalize matches for micmute key on ProBook 4xx.
Silence two hardwired keys on the ProBook 440 G3 that should not produce evdev
events. Thanks to Hermann Kraus for those! (See PR #2679)
|
|
https://launchpad.net/bugs/1535219
|
|
Use `PRIu64` to print `uint64_t` in log msgs
|
|
resolved iteration fix
|
|
systemctl: Fix warn: action_to_runlevel() is not used
|
|
|
|
core: use DUAL_TIMESTAMP_NULL to reset kernel_timestamp
|
|
Fixes for adjtime parsing
|
|
Close the FILE* instead of the underlying fd.
|
|
Don't escape the name of the container nspawn service
|
|
shorten hostname before checking for trailing dot
|
|
core: avoid compiler warning when compiling with -fexceptions
|
|
Use assert_se() to ensure that they don't get optimized away.
|
|
Don't use {} for single-line "then" blocks.
|
|
test-clock: fix fd "leak"
|
|
If HAVE_SYSV_COMPAT is not defined: ‘action_to_runlevel’ defined but not used
|
|
CID #1352301.
|
|
instead of direct reset of kernel_timestamp fields.
|
|
stdio-bridge: Correctly propagate error
|
|
Return EXIT_FAILURE and print the correct errno code if sd_bus_get_fd() or sd_bus_get_events() fail
|
|
Shortening can lead to a hostname that has a trailing dot.
Therefore it should be done before checking from trailing dots.
|
|
ISSUE_TEMPLATE: Use a list for submission type so that it appears as a checkbox
|
|
Trivial fixes
|
|
|
|
Initialize auto variables with cleanup attribute, otherwise we
get a compiler warning with -fexceptions.
./configure CFLAGS='-Wmaybe-uninitialized -fexceptions -O2'
|
|
|
|
|
|
When using `%I` for instances of `systemd-nspawn@.service`, the result
will be `systemd-nspawn` trying to launch a container named e.g.
`fedora/23` instead of `fedora-23`.
Using `%i` instead prevents escaping `-` in a container name and uses
the unmodified container name from the machine store.
|
|
Similarly to the previous commit, make context_write_data_local_rtc()
understand /etc/adjtime files with just one or two lines, with or without a
final newline.
Normalize the file to the current definition in hwclock(8), in the spirit of
"be liberal what you accept and strict what you produce": Add line terminators,
and set the second line to "0" if missing.
Fixes: #2638
|
|
As we default to "hardware clock is in UTC" if /etc/adjtime is not present, it
also makes sense to have that default if /etc/adjtime contains only one or two
lines.
Drop the "gibberish" test case, as this was just EIO because of not containing
three lines, which is already contained in other tests. clock_is_localtime()
never actually validated the format of the first two lines, and there is little
point in doing that.
This addresses the reading half of issue #2638.
|
|
Add path argument to clock_is_localtime() and default to "/etc/adjtime" if it's
NULL. This makes the function testable.
Add test-clock: initial test cases for some scenarios, using a temporary file.
This also checks the behaviour with a NULL (i. e. the system's /etc/adjtime)
file.
|
|
a checkbox
|
|
tree-wide: merge pager_open_if_enabled() to the pager_open()
|
|
Many subsystems define own pager_open_if_enabled() function which
checks '--no-pager' command line argument and open pager depends
on its value. All implementations of pager_open_if_enabled() are
the same. Let's merger this function with pager_open() from the
shared/pager.c and remove pager_open_if_enabled() from all subsytems
to prevent code duplication.
|
|
sd-dhcp-server: Send replies to BOOTP relay server port
|
|
RFC 2131 Section 4.1 says that
"If the ’giaddr’ field in a DHCP message from a client is non-zero,
the server sends any return messages to the ’DHCP server’ port on the
BOOTP relay agent whose address appears in ’giaddr’."
Fix this by adding a destination port when sending unicast UDP packets
and provide the server port when a BOOTP relay agent is being used.
|
|
treewide: fix typos and then/that use
|
|
|
|
tests: various fixes
|
|
dnssec: only run tests that require gcrypt if we have it
|
|
man: clarify unit ordering language
|
|
|
|
|
|
tree-wide: minor formatting inconsistency cleanups
|
|
|
|
Bugfix set virt=none when running on XEN Dom0
|
