Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On Thu, 16 Aug 2012 03:01:33 +0200 Jerome Benoit g62993...@rezozer.net wrote: Package: wnpp Severity: wishlist Owner: Jerome Benoit g62993...@rezozer.net * Package name: libpam-ssh Version : 1.97 Upstream Author : Akorty Rosenauer * URL : http://pam-ssh.sourceforge.net/ * License : BSD Programming Lang: C Description : Authenticate using SSH keys This PAM module provides single sign-on behavior for SSH. The user types an SSH passphrase when logging in and is authenticated if the passphrase successfully decrypts the user's SSH private key. In the PAM session phase, an ssh-agent process is started and keys are added. For the entire session, the user can SSH to other hosts that accept key authentication without typing any passwords. Is this about using removable media to store the SSH private key to login to machines which only have the public key? That would be useful (but isn't that covered by existing PAM support?) Is this some form of hot-desking support? If not, why is this better than a user having a different password for login and for the SSH key? Why tie login to one of my SSH private keys? The homepage doesn't make this clear, it sounds like the module just maps the user login via a graphical desktop manager to a particular SSH key the private key for which has to live on the system behind the login anyway. What's the point? -- Neil Williams = http://www.linux.codehelp.co.uk/ pgpQWPIsobSOV.pgp Description: PGP signature
Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On 08/16/2012 09:01 AM, Jerome Benoit wrote: Package: wnpp Severity: wishlist Owner: Jerome Benoit g62993...@rezozer.net * Package name: libpam-ssh Version : 1.97 Upstream Author : Akorty Rosenauer * URL : http://pam-ssh.sourceforge.net/ * License : BSD Programming Lang: C Description : Authenticate using SSH keys This PAM module provides single sign-on behavior for SSH. The user types an SSH passphrase when logging in and is authenticated if the passphrase successfully decrypts the user's SSH private key. In the PAM session phase, an ssh-agent process is started and keys are added. For the entire session, the user can SSH to other hosts that accept key authentication without typing any passwords. As much as I can see, the package is still in Debian (though removed from Wheezy). You shouldn't open an ITP for a package that is already in the archive. If your intention is to adopt the package, then you should follow the MIA process, have the package orphaned, then rename the orphaned bug as ITA (Intention To Adopt) adopt it by uploading new versions. And for that, there's no need for an ITP. Thanks for your intention to adopt this package, Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/502cbd76.6080...@debian.org
Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
Hello: On 16/08/12 11:29, Thomas Goirand wrote: On 08/16/2012 09:01 AM, Jerome Benoit wrote: Package: wnpp Severity: wishlist Owner: Jerome Benoitg62993...@rezozer.net * Package name: libpam-ssh Version : 1.97 Upstream Author : Akorty Rosenauer * URL : http://pam-ssh.sourceforge.net/ * License : BSD Programming Lang: C Description : Authenticate using SSH keys This PAM module provides single sign-on behavior for SSH. The user types an SSH passphrase when logging in and is authenticated if the passphrase successfully decrypts the user's SSH private key. In the PAM session phase, an ssh-agent process is started and keys are added. For the entire session, the user can SSH to other hosts that accept key authentication without typing any passwords. As much as I can see, the package is still in Debian (though removed from Wheezy). You shouldn't open an ITP for a package that is already in the archive. If your intention is to adopt the package, then you should follow the MIA process, have the package orphaned, then rename the orphaned bug as ITA (Intention To Adopt) adopt it by uploading new versions. And for that, there's no need for an ITP. According to its PTS ( http://packages.qa.debian.org/libp/libpam-ssh.html ): [2011-12-03] libpam-ssh REMOVED from testing (Britney) [2011-12-02] Removed 1.92-14 from unstable (Alexander Reichle-Schmehl) So the ITP is justified. Best regards, Jerome Thanks for your intention to adopt this package, Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/502d0f77.5060...@rezozer.net
Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
Package: wnpp Severity: wishlist Owner: Jerome Benoit g62993...@rezozer.net * Package name: libpam-ssh Version : 1.97 Upstream Author : Akorty Rosenauer * URL : http://pam-ssh.sourceforge.net/ * License : BSD Programming Lang: C Description : Authenticate using SSH keys This PAM module provides single sign-on behavior for SSH. The user types an SSH passphrase when logging in and is authenticated if the passphrase successfully decrypts the user's SSH private key. In the PAM session phase, an ssh-agent process is started and keys are added. For the entire session, the user can SSH to other hosts that accept key authentication without typing any passwords. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120816010133.21735.66903.report...@nen.dnsalias.org
