Package Details: pam_ssh 2.3-3

Git Clone URL: https://aur.archlinux.org/pam_ssh.git (read-only, click to copy)
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: tajacobsen
Maintainer: pancho
Last Packager: pancho
Votes: 52
Popularity: 0.000000
First Submitted: 2007-10-07 14:44 (UTC)
Last Updated: 2020-11-13 06:18 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

Libbum commented on 2017-05-07 15:33 (UTC)

Confirmed working. Thanks pancho!

pancho commented on 2017-05-07 08:11 (UTC)

Fixed. I've worked around the issue with the include dir by leveraging CPPFLAGS env var, as described in the recent comments on the git-crypt AUR package. Cheers!

pancho commented on 2017-05-07 07:39 (UTC) (edited on 2017-05-07 07:39 (UTC) by pancho)

Hi again. I've managed to get it to build again, with this admittedly hackish workaround: 1) Add --with-ssl-dir=/usr/lib/openssl-1.0 to the ./configure call on PKGBUILD 2) sudo ln -snf ../../include/openssl-1.0 /usr/lib/openssl-1.0/include Step 2 is needed because pam_ssh expects an include dir under the path specified for --with-ssl-dir; if that dir does not exist, it will end up using the include files for OpenSSL 1.1.0, and thus fail. The bad news is that I cannot upload these changes like that (the 'sudo ln ...' part comes to mind). Changes will be needed either on the openssl-1.0 arch package, to include the include dir or symlink, or on upstream pam_ssh autoconf code to allow for a --with-ssl-include-files flag to be specified, so that we can call configure with --with-ssl-include-files=/usr/include/openssl-1.0, besides the aforementioned --with-ssl-dir=/usr/lib/openssl-1.0 Comments, suggestions and/or help is welcome!

pancho commented on 2017-05-04 18:33 (UTC)

Hi, folks. Thanks for reporting the issue. I'll take a look at it as soon as I can, and possibly report it upstream as well.

Libbum commented on 2017-05-03 08:23 (UTC)

@medman826 yes, looks like it's an upstream issue. May be as simple as the way the configure script checks the version values in the openssl headers. Seems that the upstream repo hasn't been active since 2013, so we may not have a quick response there. I'll take a look at some modifications when I have the time.

medman826 commented on 2017-05-01 19:45 (UTC)

I am also getting the configure error that Libbum mentioned. This happens even if I download the source and run ./configure manually.

Libbum commented on 2017-05-01 10:57 (UTC)

I'm getting a configure error: `Your OpenSSL headers do not match your library` when trying to install. Any idea how I can rectify this? $ openssl version `OpenSSL 1.1.0e 16 Feb 2017`

pancho commented on 2015-05-10 18:45 (UTC)

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 (UTC)

Done. Thanks jstjohn for the heads up!

jstjohn commented on 2014-03-03 22:46 (UTC)

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.

« First ‹ Previous 1 2 3 4 Next › Last »