summaryrefslogtreecommitdiffstats
path: root/test/TEST-85-NETWORK (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-08-01test: attempt to install sshd-session from multiple placesFrantisek Sumsal2-2/+2
On Fedora the sshd-session binary is under /usr/libexec/openssh/ so cover this path as well in the old framework. Follow-up for aaa7b36bd15ca3a96a1e11a557482b0bc59c769f.
2024-08-01build(deps): bump github/codeql-action from 3.25.11 to 3.25.15dependabot[bot]2-4/+4
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.25.11 to 3.25.15. - [Release notes](https://github.com/github/codeql-action/releases) - [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md) - [Commits](https://github.com/github/codeql-action/compare/b611370bb5703a7efb587f9d136a52ea24c5c38c...afb54ba388a7dca6ecae48f608c4ff05ff4cc77a) --- updated-dependencies: - dependency-name: github/codeql-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
2024-08-01build(deps): bump meson from 1.4.1 to 1.5.1 in /.github/workflowsdependabot[bot]1-3/+3
Bumps [meson](https://github.com/mesonbuild/meson) from 1.4.1 to 1.5.1. - [Release notes](https://github.com/mesonbuild/meson/releases) - [Commits](https://github.com/mesonbuild/meson/compare/1.4.1...1.5.1) --- updated-dependencies: - dependency-name: meson dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-08-01build(deps): bump systemd/mkosidependabot[bot]1-1/+1
Bumps [systemd/mkosi](https://github.com/systemd/mkosi) from 4eba736412c702bbbe2c6d4a58a92fa977219249 to 63fc1fde5b1aac1abf07ac499068c2b62263dafb. - [Release notes](https://github.com/systemd/mkosi/releases) - [Changelog](https://github.com/systemd/mkosi/blob/main/NEWS.md) - [Commits](https://github.com/systemd/mkosi/compare/4eba736412c702bbbe2c6d4a58a92fa977219249...63fc1fde5b1aac1abf07ac499068c2b62263dafb) --- updated-dependencies: - dependency-name: systemd/mkosi dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
2024-08-01build(deps): bump redhat-plumbers-in-action/differential-shellcheckdependabot[bot]1-1/+1
Bumps [redhat-plumbers-in-action/differential-shellcheck](https://github.com/redhat-plumbers-in-action/differential-shellcheck) from 5.3.0 to 5.4.0. - [Release notes](https://github.com/redhat-plumbers-in-action/differential-shellcheck/releases) - [Changelog](https://github.com/redhat-plumbers-in-action/differential-shellcheck/blob/main/docs/CHANGELOG.md) - [Commits](https://github.com/redhat-plumbers-in-action/differential-shellcheck/compare/60c9f2b924a9c5a2ddbb25e7b23e8e11b56faab9...cc6721c45a8800cc666de45493545a07a638d121) --- updated-dependencies: - dependency-name: redhat-plumbers-in-action/differential-shellcheck dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-08-01build(deps): bump ossf/scorecard-action from 2.3.3 to 2.4.0dependabot[bot]1-1/+1
Bumps [ossf/scorecard-action](https://github.com/ossf/scorecard-action) from 2.3.3 to 2.4.0. - [Release notes](https://github.com/ossf/scorecard-action/releases) - [Changelog](https://github.com/ossf/scorecard-action/blob/main/RELEASE.md) - [Commits](https://github.com/ossf/scorecard-action/compare/dc50aa9510b46c811795eb24b2f1ba02a914e534...62b2cac7ed8198b15735ed49ab1e5cf35480ba46) --- updated-dependencies: - dependency-name: ossf/scorecard-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2024-08-01journalctl: fix compile error on i386Yu Watanabe1-1/+1
Fixes the following error: === In file included from ../src/basic/macro.h:13, from ../src/basic/dirent-util.h:8, from ../src/journal/journalctl-misc.c:3: ../src/journal/journalctl-misc.c: In function 'show_log_ids': ../src/journal/journalctl-misc.c:107:22: error: comparison is always true due to limited range of data type [-Werror=type-limits] 107 | assert(n_ids < INT64_MAX); | ^ ../src/fundamental/macro-fundamental.h:70:44: note: in definition of macro '_unlikely_' 70 | #define _unlikely_(x) (__builtin_expect(!!(x), 0)) | ^ ../src/basic/macro.h:165:22: note: in expansion of macro 'assert_message_se' 165 | #define assert(expr) assert_message_se(expr, #expr) | ^~~~~~~~~~~~~~~~~ ../src/journal/journalctl-misc.c:107:9: note: in expansion of macro 'assert' 107 | assert(n_ids < INT64_MAX); | ^~~~~~ cc1: all warnings being treated as errors === Follow-up for 0a8c1f6212a874b542a57ed5416e7d3575d2da93.
2024-08-01test: add test for journalctl --list-invocations and --invocation=Yu Watanabe2-0/+68
2024-08-01journalctl: add --list-invocations command and -I/--invocation optionsYu Watanabe9-11/+244
The --list-invocations command is similar to --list-boots, but shows invocation IDs of specified unit. This should be useful when showing a specific invocation of a unit. The --invocation option is similar to --boot, but takes a invocation ID or an offset. The -I option is equivalent to --invocation=0.
2024-08-01logs-show: extend journal_get_boots() and friends to find invocation IDsYu Watanabe2-54/+235
Currently the extended features are not used, but will be used later.
2024-08-01logs-show: introduce several helper functionsYu Watanabe2-34/+71
Currently these are not used, but will be used later.
2024-08-01use int64_t for index in show_log_ids()Yu Watanabe1-5/+6
2024-08-01journalctl: split out show_log_ids() from action_list_boots()Yu Watanabe1-21/+31
No functional change, just refactoring and prepraration for later change.
2024-08-01journalctl: update log messagesYu Watanabe1-2/+2
2024-08-01logs-show: rename BootId -> LogIdYu Watanabe4-78/+78
The struct itself is generic, and can be used for other ID. Let's rename it to more generic one. No functional change, just refactoring and preparation for later commits.
2024-07-31core/socket: stop hardcoding every service inactive stateMike Yuan1-14/+27
History (c068650fcfc69aebb35be1c71f35dbc25b22030a, 941a12dcba57f6673230a9c413738c51374d2998) has proven that we're not good at keeping socket and service states in sync. Instead, let's query the high-level unit_active_state() first, and only hardcode the two special auto-restart service states. Additionally, allow returning to listening state on SERVICE_CLEANING.
2024-07-31core/cgroup: use UNIT_IS_INACTIVE_OR_FAILED where appropriateMike Yuan1-1/+1
2024-07-31core/unit: merge use of LOG_CONTEXT_SET_LOG_LEVEL into LOG_CONTEXT_PUSH_UNITMike Yuan2-7/+7
No functional change, since LOG_CONTEXT_PUSH_UNIT is only used in exec_spawn().
2024-07-31core: clean up ambient capability loggingMike Yuan2-3/+6
Follow-up for e0ebc81b2d194206c519375394bd67baa19e67ce
2024-07-31mkosi: Beef up testuser a bitDaan De Meyer2-1/+15
Give it a password and add it to some common groups.
2024-07-31mkosi: Switch to autologin via credentialsDaan De Meyer1-2/+6
Let's use the newly added credentials to only enable autologin for /dev/console (systemd-nspawn) and /dev/hvc0 (qemu) instead of enabling autologin for every tty.
2024-07-31socket: fix socket activation of stopped services with pinned FD storeMichal Sekletar2-2/+12
2024-07-31units: Import tty specific credentials for each getty unitDaan De Meyer4-0/+8
As explained in the previous commit, this allows us to configure agetty and login for individual ttys instead of globally.
2024-07-31core: Add support for renaming credentials with ImportCredential=Daan De Meyer12-45/+339
This allows for "per-instance" credentials for units. The use case is best explained with an example. Currently all our getty units have the following stanzas in their unit file: """ ImportCredential=agetty.* ImportCredential=login.* """ This means that setting agetty.autologin=root as a system credential will make every instance of our all our getty units autologin as the root user. This prevents us from doing autologin on /dev/hvc0 while still requiring manual login on all other ttys. To solve the issue, we introduce support for renaming credentials with ImportCredential=. This will allow us to add the following to e.g. serial-getty@.service: """ ImportCredential=tty.serial.%I.agetty.*:agetty. ImportCredential=tty.serial.%I.login.*:login. """ which for serial-getty@hvc0.service will make the service manager read all credentials of the form "tty.serial.hvc0.agetty.xxx" and pass them to the service in the form "agetty.xxx" (same goes for login). We can apply the same to each of the getty units to allow setting agetty and login credentials for individual ttys instead of globally.
2024-07-31exec-credential: Skip duplicate credentials in load_credential_glob()Daan De Meyer2-5/+15
We document that when multiple credentials of the same name are found, we use the first one found so let's actually implement that behavior.
2024-07-31exec-credential: Log if we skip duplicate credentialDaan De Meyer1-1/+3
2024-07-31Drop EEXIST handling in load_credential_glob()Daan De Meyer1-2/+0
Credentials are written to a temporary file and renamed to the destination with renameat() which will replace existing files so EEXIST should not happen so drop the handling for EEXIST.
2024-07-31cgroup-util: Don't try to open pidfd for kernel threadsDaan De Meyer1-1/+3
The kernel might start returning -EINVAL when trying to open pidfd's for kernel threads so let's not try to open pidfd's for kernel threads.
2024-07-31log: Fix size calculation for number of iovecsDaan De Meyer1-3/+3
Each log context field can expand to up to three iovecs (key, value and newline) so let's fix the size calculation to take this into account.
2024-07-31execute: Drop log level to unit log level in exec_spawn()Daan De Meyer3-2/+15
All messages logged from exec_spawn() are attributed to the unit and as such we should set the log level to the unit's max log level for the duration of the function.
2024-07-31Revert "execute: Call capability_ambient_set_apply even if ambient set is 0"Łukasz Stelmach1-1/+1
With ambient capabilities being dropped at the start of process managers (both system and user) as well as systemd-executor it isn't necessary to drop them here. Moreover, at this point also the inheritable set can be preserved. This makes it possible to assign a user session manager inheritable capabilities which combined with file capabilites (ei sets) of service executables enable running user services with capabilities but only when started by the manager. This reverts commit 943800f4e7728feb2416dd57b8c296614497b94f.
2024-07-31core: drop ambient capabilities in systemd-executorŁukasz Stelmach4-5/+43
Since the commit 963b6b906e ("core: drop ambient capabilities in user manager") systemd running as the session manager has dropped ambient capabilities retaining other sets allowing user services to be started with elevated capabilities. This, worked fine until the introduction of sd-executor. For a non-root process to be started with elevated capabilities by a non-root parent it either needs file capabilities or ambient capabilities in the parent process. Thus, systemd needs to allow sd-executor to inherit its ambient capabilities and sd-executor should drop them as systemd did before. The ambient set is managed for both system and session managers, but with the default set for PID#1 being empty, this code does not affect operation of PID#1. Fixes: bb5232b6a3 ("core: add systemd-executor binary")
2024-07-31man: suggest to enable global IPv6Forwarding= setting to make IPv6 packets ↵Yu Watanabe1-1/+9
forwarded Closes #33414.
2024-07-31NEWS: mention that udevadm test and test-builtin are now non-destructiveYu Watanabe1-0/+7
Follow-up for 089bef66316e5bdc91b9984148e5a6455449c1da. Prompted by https://github.com/systemd/systemd/issues/33619#issuecomment-2257576579.
2024-07-31network: mention that IPv4 ACD is enabled by default for 169.254.0.0/16Yu Watanabe1-3/+11
Prompted by #33824.
2024-07-31network: request non-NULL SSID when a wlan interface is configured as stationYu Watanabe1-0/+1
To avoid conflicts with user .network file for the wlan interface with Bond=. See https://github.com/systemd/systemd/issues/19832#issuecomment-857661200.
2024-07-31efi: fix link to legacy EFI handover protocolLuca Boccassi1-1/+1
2024-07-31stub: allocate and zero enough space in legacy x86 handover protocolLuca Boccassi6-10/+29
A PE image's memory footprint might be larger than its file size due to uninitialized memory sections. Normally all PE headers should be parsed to check the actual required size, but the legacy EFI handover protocol is only used for x86 Linux bzImages, so we know only the last section will require extra memory. Use SizeOfImage from the PE header and if it is larger than the file size, allocate and zero extra memory before using it. Fixes https://github.com/systemd/systemd/issues/33816
2024-07-30network: shorten code a bitYu Watanabe1-3/+0
2024-07-30network: call link_handle_bound_by_list() before trying to reconfigure interfaceYu Watanabe1-4/+7
Otherwise, when an interface gained its carrier, the interface may not have matching .network file yet, then link_reconfigure_impl() returns zero, and link_handle_bound_by_list() is skipped. Fixes #33837.
2024-07-30Revert "network/ndisc: ignore most fields of RA header when lifetime is zero"Ivan Shapovalov1-6/+0
This reverts commit ffef01acddcac27caaef02f7f28bff03d7799e5e. Similar to 2d393b1b6d8 ("network: IPv6 Compliance: Router Advertisement Processing, Reachable Time [v6LC.2.2.15]"), Extract from: https://www.ietf.org/rfc/rfc4861.html#section-4.2, p.21, first paragraph: The Router Lifetime applies only to the router's usefulness as a default router; it does not apply to information contained in other message fields or options. So it does not make sense to prevent DHCPv6 when Router Lifetime is 0. Fixes #33357.
2024-07-30Fix detection of TDX confidential VM on Azure platformDaniel P. Berrangé3-6/+15
The original CVM detection logic for TDX assumes that the guest can see the standard TDX CPUID leaf. This was true in Azure when this code was originally written, however, current Azure now blocks that leaf in the paravisor. Instead it is required to use the same Azure specific CPUID leaf that is used for SEV-SNP detection, which reports the VM isolation type. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2024-07-30test-network: add test case for preferred source with peerYu Watanabe2-0/+13
For issue #31950.
2024-07-30network: make link_get_address() provide matching address with peerYu Watanabe6-37/+63
As all callers do not care if the address has peer address. This also drops prefixlen argument as it is always zero. Fixes a bug introduced by 42f8b6a80878e688b821adfb315c0a1f0a7076ce. Fixes #31950.
2024-07-30network/ipv4acd: manage ACD engines with Address objectYu Watanabe3-31/+44
IPv4 addresses are managed with local and peer addresses and prefix length. So, potentially, the same address with different prefix length can be assigned on a link, e.g. 192.168.0.1/24 and 192.168.0.1/26. If one of the address is configured with ACD but the other is not, then previously ACD might be unexpectedly disabled or enabled on them, as we managed ACD engines with only local addresses. This makes ACD engines managed with the corresponding Address objects.
2024-07-30network: do not bring down bound interfaces immediatelyYu Watanabe1-19/+11
Even if a timespan specified to IgnoreCarrierLoss= for an interface, when the carrier of the interface lost, bound interfaces might be bring down immediately. Let's also postpone bringing down bound interfaces with the specified timespan.
2024-07-30document how TimeoutStartSec= affects notify-reload (#33653)Arian van Putten1-0/+6
* document how TimeoutStartSec= affects notify-reload
2024-07-30nspawn: remove macvlan interfaces before network namespace diedYu Watanabe3-0/+55
This is similar to what we do for veth interfaces in remove_veth_links(). When a container rebooted, macvlan interfaces created by the previous boot may still exist in the kernel, and that causes -EADDRINUSE after reboot. Hopefully fixes #680.
2024-07-30cgroup-util: Ignore kernel threads in cg_kill_items()Daan De Meyer1-0/+6
Similar to the implementation of cgroup.kill in the kernel, let's skip kernel threads in cg_kill_items() as trying to kill kernel threads as an unprivileged process will fail with EPERM and doesn't do anything when running privileged.
2024-07-29kernel-install: Try some more initrd variants in 90-loaderentry.installDaan De Meyer1-2/+12
On CentOS/Fedora, dracut is configured to write the initrd to /boot/initramfs-$KERNEL_VERSION...img so let's check for that as well if no initrds were supplied.