Summary: | sys-auth/pam_ssh-2.3: fatal: key_load_private: memory allocation failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jan Essert <netz> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | RESOLVED PKGREMOVED | ||
Severity: | normal | CC: | chrylis, flow, jasmin+gentoo, treecleaner |
Priority: | Normal | Keywords: | PMASKED |
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 797325 |
Description
Jan Essert
2023-01-25 19:55:28 UTC
I can't find anyone else still packaging this, although FreeBSD has it in base. Someone could compare our one vs https://github.com/freebsd/freebsd-src/blob/d643925a79caab5c6de62b066e374935b60bcaf1/lib/libpam/modules/pam_ssh/pam_ssh.c, I suppose. hm, opensuse has it still but no patches... Could you humour me and try CFLAGS="-O2 -fno-strict-aliasing" emerge -v1 pam_ssh and tell me if it helps? debian still ship it too, with these patches: https://sources.debian.org/src/libpam-ssh/2.3%2Bds-6/debian/patches/. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bd4987694728ce81e8f05197ee1688ff1fdfff1d commit bd4987694728ce81e8f05197ee1688ff1fdfff1d Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2024-03-26 14:02:16 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2024-03-26 14:03:58 +0000 package.mask: Last rite sys-auth/pam_ssh Bug: https://bugs.gentoo.org/892031 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/base/package.use.mask | 4 ++++ profiles/package.mask | 5 +++++ 2 files changed, 9 insertions(+) Removing. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b09685143c47821d891ed166e6c96df17d4256c5 commit b09685143c47821d891ed166e6c96df17d4256c5 Author: Michał Górny <mgorny@gentoo.org> AuthorDate: 2024-05-08 09:09:41 +0000 Commit: Michał Górny <mgorny@gentoo.org> CommitDate: 2024-05-08 09:17:28 +0000 sys-auth/pam_ssh: Remove last-rited pkg Bug: https://bugs.gentoo.org/892031 Signed-off-by: Michał Górny <mgorny@gentoo.org> profiles/package.mask | 5 -- sys-auth/pam_ssh/Manifest | 1 - .../pam_ssh/files/pam_ssh-2.1-dot-ssh-check.patch | 22 ------- sys-auth/pam_ssh/files/pam_ssh-gcc10-fix.patch | 11 ---- sys-auth/pam_ssh/files/pam_symbols.ver | 4 -- sys-auth/pam_ssh/metadata.xml | 8 --- sys-auth/pam_ssh/pam_ssh-2.3-r1.ebuild | 75 ---------------------- 7 files changed, 126 deletions(-) This appears to be a major breaking change with virtually no warning or documentation (one month from masking to removal for a longstanding authentication package whose absence will lock users out of their accounts). What's the replacement? (Web search provides no useful results whatsoever.) (In reply to Christopher Smith from comment #8) > What's the replacement? (Web search provides no useful results whatsoever.) I'd say the a common approach these days is a pam module that uses the provided password to unlock the SSH key [1]. Which means that the passphrase for your private SSH key and your Unix password must be identical. For example, by gnome-keyring, provides such a PAM module. 1: Note that this is subtle different from pam_ssh's approach which grants access if the provided password unlocks the private SSH key *while* it also starts an ssh-agent. (In reply to Christopher Smith from comment #8) > This appears to be a major breaking change with virtually no warning or > documentation (one month from masking to removal for a longstanding > authentication package whose absence will lock users out of their accounts). > What's the replacement? (Web search provides no useful results whatsoever.) The bug here suggested it didn't even work at all for the last 2 years. My most recent reinstall of it is timestamped October 30, 2023. (And I have seen the "auto-add" options, but I specifically have kept my SSH key passphrases and my login passwords distinct.) |