Package Details: pam_ssh 2.1-3

Git Clone URL: https://aur.archlinux.org/pam_ssh.git (read-only)
Package Base: pam_ssh
Description: PAM module providing single sign-on behavior for SSH.
Upstream URL: http://pam-ssh.sourceforge.net/
Keywords: pam ssh
Licenses: custom
Submitter: tkjacobsen
Maintainer: pancho
Last Packager: pancho
Votes: 51
Popularity: 0.033269
First Submitted: 2007-10-07 14:44
Last Updated: 2015-12-08 08:07

Latest Comments

pancho commented on 2015-05-10 18:45

In pam_ssh 2.1-2 I've enabled signature checking for the source tarball (signed by Wolfgang Rosenauer, the current maintainer). See https://wiki.archlinux.org/index.php/Makepkg#Signature_checking for instructions on how to handle this.

pancho commented on 2014-03-04 21:41

Done. Thanks jstjohn for the heads up!

jstjohn commented on 2014-03-03 22:46

You should change the pam_ssh.install file such that it contains a post_upgrade() function that (1) uses vercmp to see if the upgrade is from <anything> to version 2+ and (2) echoes the *current* contents of pam_ssh.install.

Alternatively, rename pam_ssh.install to README or INSTALL and remove the 'install=' line from the PKGBUILD.

pancho commented on 2014-03-01 12:27

Updated to pam_ssh 2.0. Read the provided pam_ssh.install for the actions required for updating.

pancho commented on 2013-12-26 16:44

pam-ssh 2.0 was released on 2013-11-18, featuring the load of all keys in ~/.ssh/login-keys.d, sparing you the need to list every one of them in the pam config file (keyfiles param). Actually, the keyfiles param has been removed.

All three patches {block-sigterm,empty-pw-segfault-gentoo,log}.patch have been applied upstream, so can be removed from this package.

I've done so, built and installed the package, and it works like a charm, once I moved my keys to ~/.ssh/login-keys.d.

From the ChangeLog:
* expect keys used for login in ~/.ssh/login-keys.d directory
(see README; this behaviour will cause old setups to fail
since the default keys are not used anymore for auth)

Thanks!

pancho commented on 2013-12-26 16:43

pam-ssh 2.0 was released on 2013-11-18, featuring the load of all keys in ~/.ssh/login-keys.d, sparing you the need to list every one of them in the pam config file (keyfiles param). Actually, the keyfiles param has been removed.

All three patches {block-sigterm,empty-pw-segfault-gentoo,log}.patch have been applied upstream, so can be removed from this package.
2013-11-18
I've done so, built and installed the package, and it works like a charm, once I moved my keys to ~/.ssh/login-keys.d.

From the ChangeLog:
* expect keys used for login in ~/.ssh/login-keys.d directory
(see README; this behaviour will cause old setups to fail
since the default keys are not used anymore for auth)

Thanks!

bender02 commented on 2013-03-26 10:25

Updated. Please let me know if it doesn't work (as I don't have a setup that I could test the problem).

Anonymous comment on 2013-03-22 21:36

I confirm, I just applied the patch mentioned in the previous comment to resolved the timeout issue on the shutdown.
If you can apply the patch with the other ones, it will be helpful.

Thanks :)

mrgrim commented on 2013-03-15 22:52

I think the current version is running into the issue documented here:

https://bugzilla.novell.com/show_bug.cgi?id=727246

Any chance this patch could be applied here?

bender02 commented on 2012-05-07 13:40

Thanks, updated.

All comments