linux/poky.git/meta/recipes-extended/pam/libpam, branch master-test

libpam: support usrmerge

2021-01-08T10:10:15+00:00

(From OE-Core rev: d7864a46092b8030accbc8c9a1c9055a762d69ba) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

libpam: Drop musl patches

2021-01-01T23:15:13+00:00

These issues are addressed in libpam overtime and no longer needed thusly in 1.5.x (From OE-Core rev: 488c554623839d17436333894f9f4b244347de9d) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

libpam: update 1.3.1 -> 1.5.1

2020-12-31T11:53:26+00:00

Remove crypt_configure.patch, issue fixed upstream. Remove pam-security-abstract-securetty-handling.patch and pam-unix-nullok-secure.patch, patches coming from debian, difficult to rebase, and their purpose is unclear. Disable doc generation, as libpam messes up native and target compiler options. Adjust dependencies and packaging. (From OE-Core rev: 43e3d014748b1ccff25c232b1e6d9345859c0f29) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

libpam: Remove option 'obscure' from common-password

2020-06-16T22:39:28+00:00

libpam does not support 'obscure' checks to password, there are the same checks in pam_cracklib module. And this fix can remove the below error message while updating password with 'passwd': pam_unix(passwd:chauthtok):unrecognized option[obscure] (From OE-Core rev: ea761dbac90be77797308666fe1586b05e3df824) Signed-off-by: Haiqing Bai Signed-off-by: Richard Purdie

libpam: consolidate a patch to a patch

2019-12-28T23:25:41+00:00

(From OE-Core rev: 6d79a39856c1b325d0ed6f057d8eaef64e31569f) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libpam: Upgrade 1.3.0 -> 1.3.1

2019-06-04T08:09:42+00:00

Remove patch applied upstream. Upstream tarball location changed. (From OE-Core rev: 40b1825a4434334f3513f94775b176545f8d2f3a) Signed-off-by: Adrian Bunk Signed-off-by: Richard Purdie

libpam: refresh patches

2018-03-09T17:17:03+00:00

The patch tool will apply patches by default with "fuzz", which is where if the hunk context isn't present but what is there is close enough, it will force the patch in. Whilst this is useful when there's just whitespace changes, when applied to source it is possible for a patch applied with fuzz to produce broken code which still compiles (see #10450). This is obviously bad. We'd like to eventually have do_patch() rejecting any fuzz on these grounds. For that to be realistic the existing patches with fuzz need to be rebased and reviewed. (From OE-Core rev: 994e43acc67efeb33d859be071609daa844e9b77) Signed-off-by: Ross Burton Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: Drop remnants of uclibc support

2017-06-22T08:16:00+00:00

uclibc support was removed a while ago and musl works much better. Start to remove the various overrides and patches related to uclibc which are no longer needed. uclibc support in a layer would still be possible. I have strong reasons to believe nobody is still using uclibc since patches are missing and I doubt the metadata even parses anymore. (From OE-Core rev: 653704e9cf325cb494eb23facca19e9f05132ffd) Signed-off-by: Richard Purdie

libpam: update to 1.3.0

2016-05-30T14:58:12+00:00

1.2.1 -> 1.3.0 Remove upstreamed patch: a) pam-no-innetgr.patch Refreshed the following patches for 1.3.0: a) crypt_configure.patch b) pam-unix-nullok-secure.patch (From OE-Core rev: ac512ff9fbe41428e3d71d3e943aaa871d8b155a) Signed-off-by: Maxin B. John Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libpam: Fix build with musl

2015-12-12T23:42:55+00:00

Define strndupa if not available in libc additionally fix headers to explicitly needed include files which glibc was including indirectly (From OE-Core rev: 24097d8bb481ed1312c45b2e93527a271f56e4be) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie