linux/poky.git/meta/recipes-extended/shadow, branch halstead/hashclient

shadow: update 4.14.2 -> 4.15.0

2024-04-12T17:04:01+00:00

libcrack support was dropped. (From OE-Core rev: 2d00e17dfdfbbf8c301a63192ac1066c167f2bec) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

shadow: don't install libattr.so.* when xattr not in DISTRO_FEATURES

2024-03-23T10:18:20+00:00

Fixes the following issue: install: cannot stat '.../recipe-sysroot-native/usr/lib/libattr.so.*': No such file or directory ... ERROR: Task (virtual:native:.../shadow_4.14.2.bb:do_install) failed with exit code '1' (From OE-Core rev: b3afb80d07d97aaa786b6921fb6f61e316201367) Signed-off-by: Sam Van Den Berge Signed-off-by: Richard Purdie

shadow: fix copydir operation with 'pseudo'

2024-03-20T18:20:38+00:00

Calling 'useradd' through pseudo on (at least) Ubuntu 20 creates filesystem objects (.bashrc, .profile) with invalid attributes. It manifests as | tar: ./home/.../.bashrc: Unknown file type; file ignored or | Copying files into the device: __populate_fs: ignoring entry ".bashrc" | .bashrc: File not found by ext2_lookup while looking up ".bashrc" when building the image. This happens due to a bug in shadow which is caused by clobbering fstatat() results. (From OE-Core rev: 991f880e5cb3d30a1197711d44af2fdb1719ce82) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie

meta: Remove some not needed CVE_STATUS

2024-02-24T16:10:23+00:00

CVE_STATUS was set for those components, but meanwhile databases are updated with corrected information, so setting the CVE_STATUS is not needed anymore. (From OE-Core rev: 5ec6057cfa66ceeb33bec013e320f8e3fa7d7ecf) Signed-off-by: Simone Weiß Signed-off-by: Richard Purdie

shadow: add a packageconfig for logind support

2024-02-09T13:55:06+00:00

This was causing host contamination in particular, where libsystemd was installed on the host. (From OE-Core rev: fda06b441655cfa4e5f93e8f5587f27aa3610bb8) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

shadow: replace static linking with dynamic libraries in a custom location and bundled with shadow

2024-01-21T12:27:12+00:00

Despite our efforts to make static linking work, there have been new reports of bizarre build failures: https://lists.openembedded.org/g/openembedded-core/message/194006 https://lists.openembedded.org/g/openembedded-core/message/193907 This commit changes back to dynamic linking, but places the libraries in a custom location, per RP's suggestion. (From OE-Core rev: b93562937737e97dbc8cb7c874e9913f6a285a34) Signed-off-by: Alexander Kanavin Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

shadow: link executables statically for -native variant

2024-01-12T11:54:05+00:00

shadow 4.14.x adds a number of libraries it dynamically links with (md, bsd, attr). This causes troubles in setscene tasks where shadow executables are used (such as useradd), as pulling in the needed dynamic libraries needs unpleasant special-casing. (From OE-Core rev: 495ff95eae14a91c94187f78a0b30c7957c9b168) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

shadow: update 4.13 -> 4.14.2

2024-01-12T11:54:05+00:00

License-Update: formatting, spdx conversion Drop: 0001-Disable-use-of-syslog-for-sysroot.patch (issue fixed upstream) 0001-Fix-can-not-print-full-login.patch 0001-Overhaul-valid_field.patch CVE-2023-29383.patch (backports) libbsd is a new native dependency, as otherwise glibc >= 2.38 is needed. A similar fix is added to musl in order to define non-standard __BEGIN_DECLS/__END_DECLS. (From OE-Core rev: e85069acf304fe0b68583cf79fe3ec4f775dca68) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

shadow: Fix for CVE-2023-4641

2023-12-04T11:23:37+00:00

shadow-utils: possible password leak during passwd(1) change CVE: CVE-2023-4641 Upstream-Status: Backport [https://github.com/shadow-maint/shadow/commit/65c88a43a23c2391dcc90c0abda3e839e9c57904] (From OE-Core rev: 7942df17d9dfcf690106b8b86506d496e6251327) Signed-off-by: Xiangyu Chen Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

recipes: Drop remaining PR values from recipes

2023-09-22T06:45:17+00:00

We've been removing PR values from recipes at upgrade time for a while. In general anyone maintaining a binary distro would end up having to curate these themselves so the values in OE-Core aren't really that useful anymore. In many ways it makes sense to clear out the remaining ones (which are mostly for 'config' recipes that are unlikely to increase in PV) and leave a clean slate for anyone implementing a binary distro config. References are left in meta-selftest since the tests there do involve them and their removal upon upgrade. (From OE-Core rev: d4c346e8ab8f3cae25d1b01c7331ed9f6d4f96ef) Signed-off-by: Richard Purdie