search for: pamtest

...172.20.1.1 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Pamtester does not exhibit this behaviour. The PAM module code, for reference: https://github.com/SURFscz/pam-weblogin -- You are receiving this mail because: You are watching the assignee of the bug.

...developed a custom PAM module which only allows a user to authenticate to the server only if another user of the same machine also authenticates succesfully. It's currently a simple module which also works as a PAM aware application since it authenticates each user with PAM itself. Both the pamtester utility and su can use this module correctly. However, when I try to use it with my openssh server the authentication fails after the first prompt. To give you an example of a session I've attached below both the logs server-side[0] and client-side[1]. A correct authentication flow should...

Has anyone else seen a problem recently (like, the last few weeks) with anacron? We've got a couple of recently-built systems and we're seeing Mar 4 17:20:01 <system> crond[25767]: (root) PAM ERROR (Failure setting user credentials) Mar 4 17:20:01 <system> crond[25767]: (root) FAILED to authorize user with PAM (Failure setting user credentials) mark

...t hit every line in /etc/security/access.conf, and authentication fails. +:unbound:cron crond was already in the file, and at the top, after looking at the rpm, I added +:root:cron crond :0 tty1 tty2 tty3 tty4 tty5 tty6 and it just strolls past in its listwalk, and says nope. I did try installing pamtester, and that's completely useless - even with -v, it just tells me it failed. Any clues, folks? mark

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can anyone reproduce this on a Solaris 8 system with 4.2p1: openssh is configured to use PAM and sshd_config has "UsePam" set to "yes" pam.conf has something like this: other auth required pam_get_authtok other auth sufficient pam_krb5.so.1 use_first_pass other auth required pam_unix.so.1 use_first_pass Now, If I log in via

John Olsson M wrote: > What about changing the dialog like this? (The instructions matches better I think there's a good case to be made for OpenSSH to not provide any instructions at all unless it is in charge of the dialog itself. Have you checked that the current instructions are actually output by OpenSSH? The string seems to be in openbsd-compat/bsd-cray.c inside #ifdef _UNICOS

http://bugzilla.mindrot.org/show_bug.cgi?id=1165 Summary: 'groups' command fails on AIX when logged in as root user via SSH. Product: Portable OpenSSH Version: 4.2p1 Platform: Other OS/Version: AIX Status: NEW Severity: major Priority: P2 Component: Miscellaneous

http://bugzilla.mindrot.org/show_bug.cgi?id=1065 Summary: password expiration and SSH keys don't go well together Product: Portable OpenSSH Version: 4.1p1 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: PAM support AssignedTo: bitbucket at mindrot.org

...Vgcc_ntox86 -shared" ./Configure zlib-dynamic QNX6-i386 --prefix=/home/mpal/ws2/dawn_v1/3dParty/build_apal make clean make make install *3. openpam(20120526 Micrampelis)(with some modifications- added source codes of vasprintf and asprintf):* ./configure --enable-shared --without-doc --with-pamtest --host=i386-pc-linux-gnu --enable-debug --enable-debugging-symbols CC=qcc CFLAGS="-Vgcc_ntox86" --prefix=/home/mpal/ws2/dawn_v1/3dParty/build_apal make clean make make install *The libraries were installed in /home/mpal/ws2/dawn_v1/3dParty/build_apal/lib * *4. openssh:* CC=qcc CFLAGS...

https://bugzilla.mindrot.org/show_bug.cgi?id=2876 Bug ID: 2876 Summary: PAM_TEXT_INFO and PAM_ERROR_MSG conversation not honoured during PAM authentication Product: Portable OpenSSH Version: 7.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5

Hi, The main (and probably the only) use case of this PAM module is to let sudo authenticate users via their ssh-agent, therefore without having to type any password and without being tempted to use the NOPASSWD sudo option for such convenience. The principle is originally implemented by an existing module [0][1] and many pages that explain how to use it for such purpose can be found online.