summaryrefslogtreecommitdiffstats
path: root/crypto/openssh/auth-chall.c
Commit message (Collapse)AuthorAgeFilesLines
* Upgrade to 6.3p1.des2013-09-211-11/+11
|\ | | | | | | Approved by: re (gjb)
| * Properly flatten openssh/dist.des2008-07-221-123/+0
| |
| * Revert part of 180714 - the intent was to flatten dist, not to nuke it.des2008-07-221-0/+123
| |
| * Flatten the OpenSSH vendor tree for 3.x and newer.des2008-07-221-123/+0
| |
| * Vendor import of OpenSSH 4.4p1.des2006-09-301-2/+8
| |
| * Vendor import of OpenSSH 4.0p1.des2005-06-051-0/+7
| |
| * Vendor import of OpenSSH 3.8p1.des2004-02-261-21/+23
| |
| * Vendor import of OpenSSH 3.7.1p2.des2004-01-071-0/+26
| |
| * Vendor import of OpenSSH 3.1des2002-03-181-66/+44
| |
* | More files which no longer have any local changes.des2008-08-011-1/+0
| |
* | Merge conflicts.des2006-09-301-3/+9
| | | | | | | | MFC after: 1 week
* | Resolve conflicts.des2005-06-051-0/+7
| |
* | Resolve conflicts.des2004-02-261-21/+23
| |
* | Return the correct error value when a null query fails.des2003-09-241-1/+1
| |
* | If an ssh1 client initiated challenge-response authentication but diddes2003-03-311-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | not respond to challenge, and later successfully authenticated itself using another method, the kbdint context would never be released, leaving the PAM child process behind even after the connection ended. Fix this by automatically releasing the kbdint context if a packet of type SSH_CMSG_AUTH_TIS is follwed by anything but a packet of type SSH_CMSG_AUTH_TIS_RESPONSE. MFC after: 1 week
* | Fix keyboard-interactive authentication for ssh1. The problem was twofold:des2003-01-311-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - The PAM kbdint device sometimes doesn't know authentication succeeded until you re-query it. The ssh1 kbdint code would never re-query the device, so authentication would always fail. This patch has been submitted to the OpenSSH developers. - The monitor code for PAM sometimes forgot to tell the monitor that authentication had succeeded. This caused the monitor to veto the privsep child's decision to allow the connection. These patches have been tested with OpenSSH clients on -STABLE, NetBSD and Linux, and with ssh.com's ssh1 on Solaris. Sponsored by: DARPA, NAI Labs
* | Forcibly revert to mainline.des2002-06-271-1/+0
| |
* | Fix conflicts.des2002-03-181-66/+44
| |
* | Fix conflicts for OpenSSH 2.9.green2001-05-041-5/+6
|/
* Say "hi" to the latest in the OpenSSH series, version 2.9!green2001-05-041-0/+104
Happy birthday to: rwatson
OpenPOWER on IntegriCloud