Skip to content

pam: update to 1.7.3 - #63548

Open
r0man1an wants to merge 2 commits into
void-linux:masterfrom
r0man1an:pam
Open

r0man1an wants to merge 2 commits into
void-linux:masterfrom
r0man1an:pam

Conversation

@r0man1an

@r0man1an r0man1an commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, x86_64-glibc
  • I built this PR locally for these architectures (if supported. mark crossbuilds):
    • aarch64-glibc & -musl
    • x86_64-musl
    • armv7l

Fixes CVE-2025-6020 (CVSS 7.8)

@dogknowsnx

Copy link
Copy Markdown
Contributor

#60255 (no manpages..)

@Duncaen Duncaen added the core core package label Nov 13, 2026
@ahesford

Copy link
Copy Markdown
Member

Manual pages should be considered a hard requirement for this package.

@r0man1an

Copy link
Copy Markdown
Contributor Author

Manual pages should be considered a hard requirement for this package.

I'm currently working on it. Apparently it needs docbooks5 so I need to get that merged first.

@r0man1an

Copy link
Copy Markdown
Contributor Author

I managed to get the docs working.

CI will fail because it still needs docbook5-xml (#63622) merged in order to work.

@ahesford

Copy link
Copy Markdown
Member

The docbook5-xml addition needs to be in this PR, not separate.

@dogknowsnx

dogknowsnx commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Is there any particular reason as to why you're trying to package an older version?

EDIT: Do these changes create /etc/environment and /etc/security/*?

@r0man1an

Copy link
Copy Markdown
Contributor Author

The docbook5-xml addition needs to be in this PR, not separate.

Thank you for the advise.

@r0man1an

Copy link
Copy Markdown
Contributor Author

Is there any particular reason as to why you're trying to package an older version?

EDIT: Do these changes create /etc/environment and /etc/security/*?

1.7.3 needed more time & effort to get it working correctly (still testing it too) and 1.7.1 fixes all major PAM CVEs. The goal is security rather than getting the latest PAM.

@dogknowsnx

Copy link
Copy Markdown
Contributor

Please mark this PR as draft for the time being

@r0man1an
r0man1an marked this pull request as draft November 17, 2026 14:06
@ahesford

Copy link
Copy Markdown
Member

We should strive for updating to the latest release. Pulling an update that is outdated from the start kind of sucks.

@r0man1an r0man1an changed the title pam: update to 1.7.1 pam: update to 1.7.3 Nov 17, 2026
@dogknowsnx

Copy link
Copy Markdown
Contributor

dogknowsnx wrote:

EDIT: Do these changes create /etc/environment and /etc/security/*?

Probably shouldn't be set to be empty: -Dvendordir= -> -Dvendordir=/etc?

@r0man1an

Copy link
Copy Markdown
Contributor Author

dogknowsnx wrote:

EDIT: Do these changes create /etc/environment and /etc/security/*?

Probably shouldn't be set to be empty: -Dvendordir= -> -Dvendordir=/etc?

Yes Everything is there. I built pam-1.7.3_1 and checked the generated xbps file. /etc/environment and /etc/security/* are in pam along with the modules and the man5/man8 pages. pam-devel has the man3 pages, docs, .pc files and .so links. pam-libs and pam-userdb (with its man pagee are fine too. -Dvendordir= keeps the stock configs in /etc so /etc doesn't need to be set.

@r0man1an

Copy link
Copy Markdown
Contributor Author

Tested this release and it works too

@r0man1an
r0man1an marked this pull request as ready for review November 17, 2026 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core core package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants