summaryrefslogtreecommitdiffstats
path: root/crypto/openssh/sshconnect.c
Commit message (Collapse)AuthorAgeFilesLines
* Remove RCSID from files which have no other diffs to the vendor branch.des2003-05-011-1/+0
|
* Resolve conflicts.des2003-04-231-6/+6
|
* Resolve conflicts.des2002-10-291-31/+87
|
* Resolve conflicts.des2002-06-291-3/+3
| | | | Sponsored by: DARPA, NAI Labs
* Forcibly revert to mainline.des2002-06-271-2/+9
|
* Resolve conflicts. Known issues:des2002-06-231-48/+27
| | | | | | | | | | | - sshd fails to set TERM correctly. - privilege separation may break PAM and is currently turned off. - man pages have not yet been updated I will have these issues resolved, and privilege separation turned on by default, in time for DP2. Sponsored by: DARPA, NAI Labs
* Fix conflicts.des2002-03-181-324/+224
|
* Bug fix: When the client connects to a server and Kerberosnectar2001-07-131-0/+1
| | | | | | | | | | | | | | authentication is enabled, the client effectively ignores any error from krb5_rd_rep due to a missing branch. In theory this could result in an ssh client using Kerberos 5 authentication accepting a spoofed AP-REP. I doubt this is a real possiblity, however, because the AP-REP is passed from the server to the client via the SSH encrypted channel. Any tampering should cause the decryption or MAC to fail. Approved by: green MFC after: 1 week
* Get ssh(1) compiling with MAKE_KERBEROS5.green2001-05-041-2/+5
|
* Fix conflicts for OpenSSH 2.9.green2001-05-041-72/+143
|
* Backout completely canonical lookup modifications.green2001-05-031-13/+6
|
* Make password attacks based on traffic analysis harder by requiring thatgreen2001-03-201-0/+15
| | | | | | | "non-echoed" characters are still echoed back in a null packet, as well as pad passwords sent to not give hints to the length otherwise. Obtained from: OpenBSD
* (try_krb5_authentication): simplify code. from joda@netbsd.orgassar2001-03-131-47/+4
|
* Add code for being compatible with ssh.com's krb5 authentication.assar2001-03-041-5/+5
| | | | | | | | | It is done by using the same ssh messages for v4 and v5 authentication (since the ssh.com does not now anything about v4) and looking at the contents after unpacking it to see if it is v4 or v5. Based on code from Björn Grönvall <bg@sics.se> PR: misc/20504
* MFS: Don't use the canonical hostname here, too.green2001-02-041-0/+2
|
* Update to OpenSSH 2.3.0 with FreeBSD modifications. OpenSSH 2.3.0green2000-12-051-8/+15
| | | | | | | | | | | | | | | | | new features description elided in favor of checking out their website. Important new FreeBSD-version stuff: PAM support has been worked in, partially from the "Unix" OpenSSH version, and a lot due to the work of Eivind Eklend, too. This requires at least the following in pam.conf: sshd auth sufficient pam_skey.so sshd auth required pam_unix.so try_first_pass sshd session required pam_permit.so Parts by: Eivind Eklend <eivind@FreeBSD.org>
* Resolve conflicts and update for OpenSSH 2.2.0kris2000-09-101-21/+30
| | | | Reviewed by: gshapiro, peter, green
* Resolve conflictskris2000-06-031-17/+2
|
* Resolve conflicts and update for FreeBSD.kris2000-05-151-1299/+330
|
* Resolve conflicts.kris2000-03-261-46/+46
|
* 1) Add kerberos5 functionality.markm2000-02-281-15/+283
| | | | | | by Daniel Kouril <kouril@informatics.muni.cz> 2) Add full LOGIN_CAP capability by Andrey Chernov
* The includes must be <openssl/.*\.h>, not <ssl/.*\.h>.green2000-02-251-2/+2
|
* Add the patches fom ports (QV: ports/security/openssh/patches/patch-*)markm2000-02-241-0/+4
|
* Vendor import of OpenSSH.markm2000-02-241-0/+1639
OpenPOWER on IntegriCloud