8673d1eda12e44803cd17ed976aedb91834c20b3
260
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
8673d1eda1 |
Merge pull request 'feat(log-forwarding): each forwarding rule names its template' (#116) from feat/forward-rule-template into main
driver / lint (push) Successful in 16s
driver / test (3.13) (push) Successful in 1m13s
driver / lowest (push) Successful in 43s
driver / build (push) Successful in 31s
driver / security (push) Successful in 1m3s
driver / publish (push) Skipped
driver / types (push) Successful in 1m8s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m22s
CI / driver (push) Successful in 2m33s
|
||
|
|
46d7125aa6 |
refactor(log-forwarding): a legacy rule's template is read on its own
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m4s
CI / driver (pull_request) Successful in 2m57s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 58s
driver / test (3.12) (pull_request) Successful in 1m21s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
The quality ratchet holds _Reader.legacy at complexity 10. |
||
|
|
8e43fe2ed9 |
feat(log-forwarding): each forwarding rule names its template
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Failing after 2m38s
driver / standard (pull_request) Failing after 17s
driver / types (pull_request) Successful in 1m9s
driver / test (3.13) (pull_request) Successful in 1m15s
driver / test (3.12) (pull_request) Successful in 1m30s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
A rule's template decides the timestamp it sends: rsyslog's default, RFC 3164, carries the host's local time without a zone, which a collector such as Graylog files shifted by the host's UTC offset (NetOrk/netork#493). The rule now says which template it uses: its own (`@host;Name`, `action(... template="...")`), else the default set before it (`$ActionForwardDefaultTemplate`, or `module(load="builtin:omfwd" template="...")` for omfwd actions), else None. |
||
|
|
1b04818982 |
Merge pull request 'fix(dhcp): a refused subnet no longer stops the rest of the set' (#114) from fix/dhcp-subnet-apply-tolerance into main
driver / lint (push) Successful in 13s
driver / lowest (push) Successful in 43s
driver / test (3.13) (push) Successful in 1m6s
driver / build (push) Successful in 29s
driver / security (push) Successful in 1m5s
driver / publish (push) Skipped
driver / types (push) Successful in 56s
driver / standard (push) Successful in 14s
driver / test (3.12) (push) Successful in 1m12s
CI / driver (push) Successful in 2m44s
|
||
|
|
65991d0930 |
fix(dhcp): a refused subnet no longer stops the rest of the set
driver / build (pull_request) Successful in 35s
driver / security (pull_request) Successful in 1m13s
CI / driver (pull_request) Successful in 3m15s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m19s
driver / test (3.12) (pull_request) Successful in 1m32s
driver / test (3.13) (pull_request) Successful in 1m16s
driver / lowest (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
apply_dhcp_subnetset called apply_dhcp_subnet for each add and update
and committed only at the end, so one refused write raised before the
commit: the subnets written ahead of it stayed saved but inactive, and
as the device reports them as configured, no later diff committed them.
It now behaves like apply_dhcp_reservationset since 4.35.1: a refused
subnet gets a [failed] line, the others are written, any non-empty diff
is committed, then DhcpApplyError is raised. DhcpApplyError takes an
optional kind ("reservation" by default) for its message.
Closes #113
|
||
|
|
9dfb5596bc |
Merge pull request 'fix(dhcp): release an address before another reservation takes it' (#112) from fix/dhcp-reservation-apply-order into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m9s
driver / lowest (push) Successful in 40s
driver / build (push) Successful in 30s
driver / security (push) Successful in 1m9s
driver / publish (push) Skipped
driver / types (push) Successful in 1m1s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m17s
CI / driver (push) Successful in 2m59s
|
||
|
|
b4cdcfd347 |
fix(dhcp): release an address before another reservation takes it
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m10s
CI / driver (pull_request) Successful in 3m6s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m3s
driver / test (3.12) (pull_request) Successful in 1m25s
driver / test (3.13) (pull_request) Successful in 1m13s
driver / lowest (pull_request) Successful in 45s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
apply_dhcp_reservationset wrote adds first, then updates in the order of the desired set. Kea keeps addresses unique at each write, so when an address moved from one reservation to another, the reservation taking it was refused as a duplicate whenever it came first. The changes are now ordered (_dhcp_order): an update that moves a reservation off its address goes before the change that takes that address, along a chain from its free end, and adds come after every update. A swap or rotation of addresses has no such order; its changes are still tried, so a server that checks only at the commit takes them, and a refused one's [failed] line says it was a swap and with which reservations. Nothing is moved to a temporary address: the contract knows no free one, and a failed second write would leave it there. The diff is computed against one read of the reservations, shared with diff_dhcp_reservations. Refused rows still do not stop the others, the rest is committed and DhcpApplyError follows, as since 4.35.1. Closes #106 |
||
|
|
5258a43dc9 |
Merge pull request 'feat(updates): the CVEs a host's installed advisories close (4.37.0)' (#111) from feature/installed-advisories into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m16s
driver / lowest (push) Successful in 39s
driver / build (push) Successful in 28s
driver / security (push) Successful in 1m6s
driver / publish (push) Successful in 28s
driver / types (push) Successful in 59s
driver / standard (push) Successful in 15s
driver / test (3.12) (push) Successful in 1m12s
CI / driver (push) Successful in 6m6s
|
||
|
|
f3cb3601a8 |
feat(updates): the CVEs a host's installed advisories close (4.37.0)
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m0s
CI / driver (pull_request) Successful in 2m29s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m2s
driver / test (3.13) (pull_request) Successful in 1m11s
driver / test (3.12) (pull_request) Successful in 1m24s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
UpdateMixin declares get_installed_advisory_cves(): per package, the CVEs the installed security advisories close -- the distribution's word that a backport is in although the upstream version did not move. The command (DNF_INSTALLED_CVES_COMMAND, dnf 4, from the cache) and its parser (parse_dnf_installed_cves) live here for every dnf driver, as the security read's do. netOrk reads it where its knowledge base holds no records of the host's release (NetOrk/netork#2394). |
||
|
|
a8fedf299a |
Merge pull request 'fix(host-status): kernel releases compare the way rpm does (4.36.2)' (#110) from fix/rpm-kernel-version-order into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m13s
driver / lowest (push) Successful in 46s
driver / build (push) Successful in 40s
driver / security (push) Successful in 1m16s
driver / publish (push) Successful in 30s
driver / types (push) Successful in 1m4s
driver / standard (push) Successful in 15s
driver / test (3.12) (push) Successful in 1m20s
CI / driver (push) Successful in 3m36s
|
||
|
|
c736fb30d0 |
refactor(host-status): compare one version segment in a helper of its own
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 57s
CI / driver (pull_request) Successful in 2m30s
driver / standard (pull_request) Successful in 15s
driver / types (pull_request) Successful in 56s
driver / test (3.12) (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
The quality ratchet refused _version_cmp at complexity 12. Comparing one segment moves to _segment_cmp, which also takes 01 and 1 as equal, as rpm does. |
||
|
|
cf555d006d |
fix(host-status): kernel releases compare the way rpm does (4.36.2)
driver / build (pull_request) Successful in 28s
driver / security (pull_request) Successful in 1m3s
CI / driver (pull_request) Failing after 2m32s
driver / standard (pull_request) Failing after 15s
driver / types (pull_request) Successful in 1m5s
driver / test (3.13) (pull_request) Successful in 1m14s
driver / test (3.12) (pull_request) Successful in 1m19s
driver / lowest (pull_request) Successful in 42s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
_version_key compared the text between numbers as plain strings, so '.el' outranked '.' and 6.12.0-208.112.5.el9uek counted as newer than the running 6.12.0-208.112.5.1.el9uek: an Oracle Linux host asked to reboot into an older kernel, and a reboot never cleared it. The releases now compare like rpmvercmp: separators only separate, a number is newer than letters in its place, and '~' comes before anything. Checked against rpm.labelCompare on Oracle Linux 9. Closes #109 |
||
|
|
4e79cd1fc8 |
Merge pull request 'fix(host-status): an Oracle Linux host's UEK kernels are not an interrupted dnf (4.36.1)' (#108) from fix/dnf-installonly-defaults into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m12s
driver / lowest (push) Successful in 41s
driver / build (push) Successful in 30s
driver / security (push) Successful in 1m3s
driver / publish (push) Successful in 30s
driver / types (push) Successful in 1m0s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m17s
CI / driver (push) Successful in 3m21s
|
||
|
|
304f404567 |
fix(host-status): an Oracle Linux host's UEK kernels are not an interrupted dnf (4.36.1)
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 56s
CI / driver (pull_request) Successful in 2m26s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 59s
driver / test (3.13) (pull_request) Successful in 1m12s
driver / test (3.12) (pull_request) Successful in 1m17s
driver / lowest (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
The installonly packages were dnf's upstream defaults plus dnf.conf's. Oracle builds kernel-uek and its parts into libdnf's defaults, and the UEK packages provide nothing of upstream's list, so every host with more than one UEK kernel was reported as left halfway. The defaults are now also asked of the host's libdnf through its Python binding; upstream's list stays the floor for dnf 5 and yum. Closes #107 |
||
|
|
aaa9f0504a |
Merge pull request 'feat(time-sync): DHCP-provided NTP servers count and are read apart (4.36.0)' (#105) from feat/time-sync-dhcp-ntp-2380 into main
driver / lint (push) Successful in 15s
driver / test (3.13) (push) Successful in 1m11s
driver / build (push) Successful in 31s
driver / security (push) Successful in 1m2s
driver / publish (push) Successful in 31s
driver / types (push) Successful in 59s
driver / lowest (push) Successful in 42s
driver / standard (push) Successful in 18s
driver / test (3.12) (push) Successful in 1m16s
CI / driver (push) Successful in 3m17s
|
||
|
|
bc47220318 |
Merge remote-tracking branch 'origin/main' into feat/time-sync-dhcp-ntp-2380
driver / build (pull_request) Successful in 48s
driver / security (pull_request) Successful in 1m26s
CI / driver (pull_request) Successful in 3m17s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 1m34s
driver / test (3.13) (pull_request) Successful in 1m32s
driver / test (3.12) (pull_request) Successful in 1m52s
driver / lowest (pull_request) Successful in 1m3s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
# Conflicts: # CHANGELOG.md # pyproject.toml |
||
|
|
08a62838f7 |
Merge pull request 'fix(dhcp): one refused reservation no longer stops the apply' (#104) from fix/dhcp-reservations-partial-apply into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m9s
driver / lowest (push) Successful in 41s
driver / build (push) Successful in 33s
driver / security (push) Successful in 1m7s
driver / publish (push) Successful in 32s
driver / types (push) Successful in 1m4s
driver / test (3.12) (push) Successful in 1m18s
driver / standard (push) Successful in 18s
CI / driver (push) Successful in 3m29s
|
||
|
|
ac38c68feb |
feat(time-sync): DHCP-provided NTP servers count and are read apart
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 3m22s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m16s
driver / test (3.13) (pull_request) Successful in 1m29s
driver / test (3.12) (pull_request) Successful in 1m33s
driver / lowest (pull_request) Successful in 41s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 31s
A device that gets the site's time giver through DHCP option 42 is aligned (NetOrk/netork#2380): most clients already learn it that way. 4.35.0 switched that off on every write -- chrony's DHCP sourcedir was commented out, and systemd-timesyncd's link servers failed the verify step -- and folded DHCP's servers into ntp_servers, so an application could not tell configured from DHCP-provided servers. TimeSyncDict gains dhcp_ntp_servers (not required): the servers the device got by DHCP and uses, in its order; [] for none, absent or None where the driver cannot tell. ntp_servers keeps only the configured ones. PosixTimeSyncMixin reads chrony's sources from the DHCP client's sourcedir (CHRONY_DHCP_DIRS, /run/chrony-dhcp by default) as chronyd reads them, and systemd-timesyncd's LinkNTPServers; ntpd and OpenNTPD keep DHCP's servers in a configuration of their own, so there it is unknown. A chrony write now comments out only server, pool and peer lines and leaves every sourcedir and the DHCP client's files alone. A DHCP sourcedir that 4.35.0 commented out behind the mark is given back on the next write, with a restart, so hosts it aligned hear DHCP again. Version 4.36.0. |
||
|
|
8516f2a1ee |
refactor(dhcp): one reservation's write in a helper of its own
driver / build (pull_request) Successful in 37s
driver / security (pull_request) Successful in 1m9s
CI / driver (pull_request) Successful in 3m0s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m19s
driver / test (3.13) (pull_request) Successful in 1m10s
driver / lowest (pull_request) Successful in 42s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
apply_dhcp_reservationset grew to 59 lines with the per-write handling; the quality ratchet allows no new function that long. Refs NetOrk/netork#2381 |
||
|
|
c74173523a |
fix(dhcp): one refused reservation no longer stops the apply
driver / build (pull_request) Successful in 38s
driver / security (pull_request) Successful in 1m11s
CI / driver (pull_request) Failing after 2m57s
driver / standard (pull_request) Failing after 22s
driver / types (pull_request) Successful in 1m22s
driver / test (3.12) (pull_request) Successful in 1m28s
driver / test (3.13) (pull_request) Successful in 1m26s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 18s
apply_dhcp_reservationset wrote the diff one reservation at a time and committed only after the last. A write the device refused -- on OPNsense, an address in a subnet Kea does not manage -- ended the run before the commit: every later reservation went unwritten, and the earlier ones stayed saved but inactive. The next diff read those back as configured, reported no changes and never committed them. A refused change now gets a "[failed] <mac> -> <ip>: <reason>" line and the others are still written. Any non-empty diff commits, also one whose every write was refused, so writes an interrupted earlier run saved take effect. DhcpApplyError (a RuntimeError, exported) is raised after the commit with how many of how many changes were refused. Refs NetOrk/netork#2381 |
||
|
|
6c7f164004 |
Merge pull request 'feat(time-sync): TimeSyncMixin, PosixTimeSyncMixin and the posix_tz helpers' (#103) from feature/time-sync-2361 into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m7s
driver / lowest (push) Successful in 38s
driver / build (push) Successful in 26s
driver / security (push) Successful in 54s
driver / publish (push) Successful in 27s
driver / types (push) Successful in 59s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m12s
CI / driver (push) Successful in 3m3s
|
||
|
|
073087da69 |
feat(time-sync): TimeSyncMixin, PosixTimeSyncMixin and the posix_tz helpers
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 1m0s
CI / driver (pull_request) Successful in 2m23s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 57s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 19s
netOrk gets one list of NTP servers and a time zone per site and aligns every device that differs (NetOrk/netork#2360). The contract comes first, so the drivers can be built against it at the same time (#2361): TimeSyncMixin declares get_time_sync() -> TimeSyncDict (servers in the device's order, the zone as an IANA name, synchronised, the client) and carries configure_time_sync(ntp_servers=None, timezone=None) as a fix template: None leaves a value alone, the device ends up with exactly the servers given, and a verify step reads it back. time_sync_writes says which of the two values a driver writes; anything else, an unknown zone, a malformed server or an empty list is refused before anything is written. PosixTimeSyncMixin implements it over run_command for Linux-like hosts: one reading as the login user (timedatectl, chrony's configuration and chronyc, timedatectl show-timesync, ntpd and OpenNTPD), the zone through timedatectl set-timezone, chrony's servers in a file of their own with every other source commented out, systemd-timesyncd's in a drop-in that resets NTP= and empties FallbackNTP=. ntpd and OpenNTPD are read only. posix_tz moves here from netOrk, so OpenWrt can write the POSIX rule and a switch the UTC offset and summer-time rule (parse_posix_tz). It reads the tzdata package, now a dependency. Release 4.35.0: the drivers that implement it need it on PyPI. |
||
|
|
278a707157 |
Merge pull request 'feat(running-backups): the backups running on a device right now' (#102) from feature/running-backups-2318 into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 58s
driver / lowest (push) Successful in 35s
driver / build (push) Successful in 26s
driver / security (push) Successful in 56s
driver / publish (push) Successful in 26s
driver / types (push) Successful in 59s
driver / standard (push) Successful in 14s
driver / test (3.12) (push) Successful in 1m13s
CI / driver (push) Successful in 2m36s
|
||
|
|
56e5e82a59 |
feat(running-backups): the backups running on a device right now
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 59s
CI / driver (pull_request) Successful in 2m24s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 1m2s
driver / test (3.13) (pull_request) Successful in 1m5s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / lowest (pull_request) Successful in 37s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 17s
A restart aborts every backup that runs on the device it restarts, and a guest's restart breaks the backup its hypervisor is taking of it. netOrk asks right before it restarts a host after patching (NetOrk/netork#2318), so the reading belongs in the contract first: RunningBackupsMixin declares get_running_backups(), opt-in like VmStopRequestMixin, so hasattr tells a caller whether the driver can tell at all. Release 4.34.0: the drivers that implement it need it on PyPI. |
||
|
|
e6f145d4a3 |
Merge pull request 'chore(release): 4.33.0' (#101) from chore/release-4.33.0 into main
driver / lint (push) Successful in 16s
driver / test (3.13) (push) Successful in 1m10s
driver / build (push) Successful in 32s
driver / security (push) Successful in 1m5s
driver / publish (push) Successful in 33s
driver / types (push) Successful in 1m0s
driver / lowest (push) Successful in 54s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m16s
CI / driver (push) Successful in 3m28s
|
||
|
|
66037e878e |
chore(release): 4.33.0
driver / build (pull_request) Successful in 44s
driver / security (pull_request) Successful in 1m9s
CI / driver (pull_request) Successful in 2m57s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 1m7s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / lowest (pull_request) Successful in 39s
driver / test (3.13) (pull_request) Successful in 1m22s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
|
||
|
|
afffd0915c |
Merge pull request 'feat(host-status): tell an interrupted dnf, yum, apk or opkg' (#98) from feat/interrupted-pm-851 into main
driver / lint (push) Successful in 16s
driver / test (3.13) (push) Successful in 1m9s
driver / build (push) Successful in 35s
driver / security (push) Successful in 1m7s
driver / publish (push) Skipped
driver / types (push) Successful in 1m7s
driver / lowest (push) Successful in 41s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m17s
CI / driver (push) Successful in 2m34s
|
||
|
|
92891473be |
fix(host-status): keep models.py at its recorded size, one literal for the dnf query
driver / build (pull_request) Successful in 36s
driver / security (pull_request) Successful in 1m6s
CI / driver (pull_request) Successful in 2m38s
driver / standard (pull_request) Successful in 14s
driver / types (pull_request) Successful in 58s
driver / test (3.12) (pull_request) Successful in 1m11s
driver / test (3.13) (pull_request) Successful in 1m5s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
The quality ratchet records models.py at 1454 lines and the new comments had made it 1460. bandit read the dnf history query, built with an f-string for its path, as SQL put together from strings (B608); it is a fixed query, now one literal with the path spelt out, and a test holds it to DNF_HISTORY. Refs NetOrk/netork#851 |
||
|
|
658f1c8ab2 |
Merge remote-tracking branch 'origin/main' into feat/interrupted-pm-851
# Conflicts: # CHANGELOG.md |
||
|
|
aacde6be3f |
Merge pull request 'chore(release): 4.32.0' (#100) from chore/release-4.32.0 into main
driver / lint (push) Successful in 14s
driver / test (3.13) (push) Successful in 1m14s
driver / build (push) Successful in 30s
driver / security (push) Successful in 1m7s
driver / publish (push) Successful in 35s
driver / types (push) Successful in 1m6s
driver / lowest (push) Successful in 37s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m29s
CI / driver (push) Successful in 3m14s
|
||
|
|
58c7616401 |
chore(release): 4.32.0
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m16s
CI / driver (pull_request) Successful in 3m13s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 1m5s
driver / test (3.12) (pull_request) Successful in 1m23s
driver / test (3.13) (pull_request) Successful in 1m38s
driver / lowest (pull_request) Successful in 1m1s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
|
||
|
|
b7e31205d5 |
Merge pull request 'feat(ssh-server): read how sshd lets people log in' (#99) from feat/ssh-server-auth into main
driver / lint (push) Successful in 15s
driver / test (3.13) (push) Successful in 1m16s
driver / build (push) Successful in 33s
driver / security (push) Successful in 1m5s
driver / publish (push) Skipped
driver / types (push) Successful in 1m2s
driver / lowest (push) Successful in 42s
driver / standard (push) Successful in 19s
driver / test (3.12) (push) Successful in 1m22s
CI / driver (push) Successful in 2m40s
|
||
|
|
1d71ff8f91 |
feat(ssh-server): read how sshd lets people log in
driver / build (pull_request) Successful in 32s
driver / security (pull_request) Successful in 1m5s
CI / driver (pull_request) Successful in 2m48s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m10s
driver / test (3.13) (pull_request) Successful in 1m25s
driver / test (3.12) (pull_request) Successful in 1m32s
driver / lowest (pull_request) Successful in 44s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
SshServerAuthMixin.get_ssh_server_auth() reads the authentication settings from sshd -T as root (password, keyboard-interactive, public key, host-based, GSSAPI, AuthenticationMethods, PermitRootLogin, UsePAM) and, with PAM on, the modules of sshd's PAM auth stack from /etc/pam.d with its includes followed. It reports the facts; whether a module is a second factor is the consumer's call. OpenSshServerMixin carries it and both read sshd -T by the same fixed command, so every driver that can harden sshd can say this too. Refs NetOrk/netork#662 |
||
|
|
58ed0f0a94 |
feat(host-status): tell an interrupted dnf, yum, apk or opkg
driver / build (pull_request) Successful in 36s
driver / security (pull_request) Failing after 1m1s
CI / driver (pull_request) Failing after 2m42s
driver / standard (pull_request) Failing after 18s
driver / types (pull_request) Successful in 1m9s
driver / test (3.12) (pull_request) Successful in 1m22s
driver / lowest (pull_request) Successful in 39s
driver / test (3.13) (pull_request) Successful in 2m14s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 17s
get_host_status() read only dpkg's state. It now also reads the rpm database and dnf's history (or yum's journal), apk's installed database and opkg's status file, without root, and names the manager it read in the new package_manager field. While one of them runs, the answer is unknown, as for dpkg. Refs NetOrk/netork#851 |
||
|
|
c1a05d6dba |
Merge pull request 'chore(release): 4.31.1' (#97) from chore/release-4.31.1 into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m3s
driver / build (push) Successful in 32s
driver / security (push) Successful in 55s
driver / publish (push) Successful in 27s
driver / types (push) Successful in 59s
driver / lowest (push) Successful in 37s
driver / standard (push) Successful in 15s
driver / test (3.12) (push) Successful in 1m13s
CI / driver (push) Successful in 3m3s
|
||
|
|
fccf902c07 |
chore(release): 4.31.1
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 1m4s
CI / driver (pull_request) Successful in 3m0s
driver / standard (pull_request) Successful in 18s
driver / types (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m23s
driver / lowest (pull_request) Successful in 39s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
|
||
|
|
f5a2811333 |
Merge pull request 'fix(log-sources): attribute a file only to the process writing it' (#96) from fix/log-writers-only into main
driver / lint (push) Successful in 12s
driver / test (3.13) (push) Successful in 1m4s
driver / build (push) Successful in 35s
driver / security (push) Successful in 1m19s
driver / publish (push) Skipped
driver / types (push) Successful in 56s
driver / lowest (push) Successful in 36s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m12s
CI / driver (push) Successful in 2m39s
|
||
|
|
98d1dbef4c |
fix(log-sources): attribute a file only to the process writing it
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 59s
CI / driver (pull_request) Successful in 2m25s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m8s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / lowest (pull_request) Successful in 40s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 14s
A process that holds a log open only to read it -- CrowdSec's acquisition, Promtail, rsyslog imfile, a tail -F -- was named as the file's writer whenever it had the lower pid. The command now reads each descriptor's flags from /proc/<pid>/fdinfo in the same round trip, and only an O_WRONLY or O_RDWR holder is the producer. A file only readers hold stays listed without one; a file only a reader inside a container holds is its view of a mount and is left out. Refs: NetOrk/netork#2092 |
||
|
|
252ea3b81c |
Merge pull request 'feat: where a host's logs go beyond it (4.31.0)' (#95) from feat/log-forwarding-2053 into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m7s
driver / lowest (push) Successful in 37s
driver / build (push) Successful in 27s
driver / security (push) Successful in 53s
driver / publish (push) Successful in 27s
driver / types (push) Successful in 55s
driver / standard (push) Successful in 16s
driver / test (3.12) (push) Successful in 1m14s
CI / driver (push) Successful in 2m44s
|
||
|
|
b685b200cc |
refactor: the rsyslog reader's cutter and action in their own steps
driver / build (pull_request) Successful in 26s
driver / security (pull_request) Successful in 56s
CI / driver (pull_request) Successful in 2m31s
driver / standard (pull_request) Successful in 15s
driver / types (pull_request) Successful in 53s
driver / test (3.12) (pull_request) Successful in 1m7s
driver / test (3.13) (pull_request) Successful in 1m2s
driver / lowest (pull_request) Successful in 37s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 13s
Keeps _pieces and _Reader.call within the standard's complexity limit. |
||
|
|
8557710724 |
feat: where a host's logs go beyond it (4.31.0)
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Failing after 2m23s
driver / standard (pull_request) Failing after 17s
driver / types (pull_request) Successful in 1m8s
driver / test (3.13) (pull_request) Successful in 1m4s
driver / test (3.12) (pull_request) Successful in 1m15s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
get_log_sources() reads, in the same command, whether rsyslog runs, its forwarding rules (legacy @/@@/:omrelp: and RainerScript omfwd/omrelp, with selector, ruleset and whether they take every message), its imfile inputs, and whether the journal reaches it (imjournal, or imuxsock with journald's ForwardToSyslog; failing a setting, the default the distribution ships commented out). Returned as `forwarding`; parse_log_forwarding and parse_rsyslog are public (NetOrk/netork#2053). |
||
|
|
1b600416f0 |
Merge pull request 'feat: which logs a host writes, and who writes each (4.30.0)' (#94) from feature/log-sources-2049 into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m3s
driver / lowest (push) Successful in 36s
driver / build (push) Successful in 27s
driver / security (push) Successful in 55s
driver / publish (push) Successful in 27s
driver / types (push) Successful in 1m4s
driver / standard (push) Successful in 15s
driver / test (3.12) (push) Successful in 1m13s
CI / driver (push) Successful in 2m41s
|
||
|
|
e622b26d42 |
refactor: keep the log source shapes in log_sources, not in models
driver / build (pull_request) Successful in 29s
driver / security (pull_request) Successful in 1m7s
CI / driver (pull_request) Successful in 2m42s
driver / standard (pull_request) Successful in 16s
driver / types (pull_request) Successful in 59s
driver / test (3.13) (pull_request) Successful in 1m17s
driver / test (3.12) (pull_request) Successful in 1m20s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 15s
models.py is over the file size limit and may not grow (quality ratchet); the shapes sit with their mixin, as ScheduledJobDict does. Refs NetOrk/netork#2049 |
||
|
|
5daba5d37c |
feat: which logs a host writes, and who writes each (4.30.0)
driver / build (pull_request) Successful in 33s
driver / security (pull_request) Successful in 1m14s
CI / driver (pull_request) Failing after 2m45s
driver / standard (pull_request) Failing after 19s
driver / types (pull_request) Successful in 1m14s
driver / test (3.13) (pull_request) Successful in 1m11s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / lowest (pull_request) Successful in 38s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 20s
LogSourcesMixin.get_log_sources() reads, in one sh -c call as root, the units journald holds entries for, the log files running processes hold open (/proc/<pid>/fd: *.log, *.log.N, anything under /var/log) with size and last write from stat -L on the descriptor, and the engine's own file of each container's output as that container's stream. Each file names the service or container of its first writer from /proc/<pid>/cgroup; a file a container writes keeps the container's own path. journald's store, deleted files and a database's write-ahead log (LevelDB's 000004.log) are left out. Without root it reads again and says so (attributed: false); a host whose find cannot list open files (busybox) raises LogSourcesUnavailable rather than reading as no files. Refs NetOrk/netork#2049 |
||
|
|
dacd10fcce |
Merge pull request 'chore(release): 4.29.0' (#93) from chore/release-4.29.0 into main
driver / lint (push) Successful in 17s
driver / test (3.13) (push) Successful in 1m21s
driver / build (push) Successful in 36s
driver / security (push) Successful in 1m12s
driver / publish (push) Successful in 34s
driver / types (push) Successful in 1m13s
driver / lowest (push) Successful in 38s
driver / standard (push) Successful in 18s
driver / test (3.12) (push) Successful in 1m38s
CI / driver (push) Successful in 3m56s
|
||
|
|
8a54674e40 |
chore(release): 4.29.0
driver / build (pull_request) Successful in 37s
driver / security (pull_request) Successful in 1m11s
CI / driver (pull_request) Successful in 2m58s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m6s
driver / test (3.12) (pull_request) Successful in 1m14s
driver / test (3.13) (pull_request) Successful in 1m6s
driver / lowest (pull_request) Successful in 42s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
|
||
|
|
d45455adf1 |
Merge pull request 'feat(local-accounts): remove_local_account_keys can clear the password too' (#92) from feat/remove-keys-clear-password into main
driver / lint (push) Successful in 16s
driver / test (3.13) (push) Successful in 1m11s
driver / build (push) Successful in 34s
driver / security (push) Successful in 1m13s
driver / publish (push) Skipped
driver / types (push) Successful in 1m3s
driver / lowest (push) Successful in 42s
driver / standard (push) Successful in 19s
driver / test (3.12) (push) Successful in 1m20s
CI / driver (push) Successful in 2m43s
|
||
|
|
ac49e2b5d4 |
feat(local-accounts): remove_local_account_keys can clear the password too
driver / build (pull_request) Successful in 30s
driver / security (pull_request) Successful in 1m2s
CI / driver (pull_request) Successful in 2m36s
driver / standard (pull_request) Successful in 19s
driver / types (pull_request) Successful in 1m1s
driver / test (3.13) (pull_request) Successful in 1m15s
driver / test (3.12) (pull_request) Successful in 1m18s
driver / lowest (pull_request) Successful in 39s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
A person who deletes their key loses the password that went with it in netOrk, but the devices kept it, and sudo with it. remove_local_account_keys(name, keys, clear_password=True) takes the keys, the password and sudo in one call; the account stays open. Each step runs when another failed. See NetOrk/netork#2033. |
||
|
|
c967635cba |
Merge pull request 'chore(release): 4.28.0' (#91) from chore/release-4.28.0 into main
driver / lint (push) Successful in 13s
driver / test (3.13) (push) Successful in 1m4s
driver / build (push) Successful in 37s
driver / security (push) Successful in 1m17s
driver / publish (push) Successful in 34s
driver / types (push) Successful in 1m2s
driver / lowest (push) Successful in 43s
driver / standard (push) Successful in 17s
driver / test (3.12) (push) Successful in 1m12s
CI / driver (push) Successful in 3m33s
|
||
|
|
c470686305 |
chore(release): 4.28.0
driver / build (pull_request) Successful in 39s
driver / security (pull_request) Successful in 1m16s
CI / driver (pull_request) Successful in 3m2s
driver / standard (pull_request) Successful in 17s
driver / types (pull_request) Successful in 1m0s
driver / test (3.13) (pull_request) Successful in 1m10s
driver / test (3.12) (pull_request) Successful in 1m16s
driver / lowest (pull_request) Successful in 56s
driver / publish (pull_request) Skipped
driver / lint (pull_request) Successful in 16s
|