update build config

update to 7.9p1

Update OpenSSH to 7.5p1. This removes protocol 1

fix merge issues

remove unneeded files

set to null

dont do that

update defaults

update config.h

Due to improper handling of alert packets, OpenSSL would consume an excessive
amount of CPU time processing undefined alert messages.

OpenSSL security patch

A malicious client can send an excessively large OCSP Status Request extension.
If that client continually requests renegotiation, sending a large OCSP Status
Request extension each time, then there will be unbounded memory growth on the
server. [CVE-2016-6304]

An overflow can occur in MDC2_Update() either if called directly or through
the EVP_DigestUpdate() function using MDC2. If an attacker is able to supply
very large amounts of input data after a previous call to EVP_EncryptUpdate()
with a partial block then a length check can overflow resulting in a heap
corruption. [CVE-2016-6303]

If a server uses SHA512 for TLS session ticket HMAC it is vulnerable to a
DoS attack where a malformed ticket will result in an OOB read which will
ultimately crash. [CVE-2016-6302]

The function BN_bn2dec() does not check the return value of BN_div_word().
This can cause an OOB write if an application uses this function with an
overly large BIGNUM. This could be a problem if an overly large certificate
or CRL is printed out from an untrusted source. TLS is not affected because
record limits will reject an oversized certificate before it is parsed.
[CVE-2016-2182]

The function TS_OBJ_print_bio() misuses OBJ_obj2txt(): the return value is
the total length the OID text representation would use and not the amount
of data written. This will result in OOB reads when large OIDs are presented.
[CVE-2016-2180]

Some calculations of limits in OpenSSL have used undefined pointer arithmetic.
This could cause problems with some malloc implementations. [CVE-2016-2177]

Operations in the DSA signing algorithm should run in constant time in order to
avoid side channel attacks. A flaw in the OpenSSL DSA implementation means that
a non-constant time codepath is followed for certain operations. [CVE-2016-2178]

In a DTLS connection where handshake messages are delivered out-of-order those
messages that OpenSSL is not yet ready to process will be buffered for later
use. Under certain circumstances, a flaw in the logic means that those messages
do not get removed from the buffer even though the handshake has been completed.
An attacker could force up to approx. 15 messages to remain in the buffer when
they are no longer required. These messages will be cleared when the DTLS
connection is closed. The default maximum size for a message is 100k. Therefore
the attacker could force an additional 1500k to be consumed per connection.
[CVE-2016-2179]

A flaw in the DTLS replay attack protection mechanism means that records that
arrive for future epochs update the replay protection "window" before the MAC
for the record has been validated. This could be exploited by an attacker by
sending a record for the next epoch (which does not have to decrypt or have a
valid MAC), with a very large sequence number. This means that all subsequent
legitimate packets are dropped causing a denial of service for a specific
DTLS connection. [CVE-2016-2181]

In OpenSSL 1.0.2 and earlier some missing message length checks can result in
OOB reads of up to 2 bytes beyond an allocated buffer. There is a theoretical
DoS risk but this has not been observed in practice on common platforms.
[CVE-2016-6306]

OpenSSL security patch

The padding check in AES-NI CBC MAC was rewritten to be in constant time
by making sure that always the same bytes are read and compared against
either the MAC or padding bytes. But it no longer checked that there was
enough data to have both the MAC and padding bytes. [CVE-2016-2107]

An overflow can occur in the EVP_EncodeUpdate() function which is used for
Base64 encoding of binary data. [CVE-2016-2105]

An overflow can occur in the EVP_EncryptUpdate() function, however it is
believed that there can be no overflows in internal code due to this problem.
[CVE-2016-2106]

When ASN.1 data is read from a BIO using functions such as d2i_CMS_bio()
a short invalid encoding can casuse allocation of large amounts of memory
potentially consuming excessive resources or exhausting memory.
[CVE-2016-2109]

Security patch OpenSSL for DROWN

A cross-protocol attack was discovered that could lead to decryption of TLS
sessions by using a server supporting SSLv2 and EXPORT cipher suites as a
Bleichenbacher RSA padding oracle.  Note that traffic between clients and
non-vulnerable servers can be decrypted provided another server supporting
SSLv2 and EXPORT ciphers (even with a different protocol such as SMTP, IMAP
or POP3) shares the RSA keys of the non-vulnerable server.  This vulnerability
is known as DROWN.  [CVE-2016-0800]

A double free bug was discovered when OpenSSL parses malformed DSA private
keys and could lead to a DoS attack or memory corruption for applications that
receive DSA private keys from untrusted sources.  This scenario is considered
rare.  [CVE-2016-0705]

The SRP user database lookup method SRP_VBASE_get_by_user had confusing memory
management semantics; the returned pointer was sometimes newly allocated, and
sometimes owned by the callee.  The calling code has no way of distinguishing
these two cases.  [CVE-2016-0798]

In the BN_hex2bn function, the number of hex digits is calculated using an int
value |i|.  Later |bn_expand| is called with a value of |i * 4|.  For large
values of |i| this can result in |bn_expand| not allocating any memory because
|i * 4| is negative.  This can leave the internal BIGNUM data field as NULL
leading to a subsequent NULL pointer dereference.  For very large values of
|i|, the calculation |i * 4| could be a positive value smaller than |i|.  In
this case memory is allocated to the internal BIGNUM data field, but it is
insufficiently sized leading to heap corruption.  A similar issue exists in
BN_dec2bn.  This could have security consequences if BN_hex2bn/BN_dec2bn is
ever called by user applications with very large untrusted hex/dec data.  This
is anticipated to be a rare occurrence.  [CVE-2016-0797]

The internal |fmtstr| function used in processing a "%s" formatted string in
the BIO_*printf functions could overflow while calculating the length of
a string and cause an out-of-bounds read when printing very long strings.
[CVE-2016-0799]

A side-channel attack was found which makes use of cache-bank conflicts on the
Intel Sandy-Bridge microarchitecture which could lead to the recovery of RSA
keys. [CVE-2016-0702]

s2_srvr.c did not enforce that clear-key-length is 0 for non-export ciphers.
If clear-key bytes are present for these ciphers, they displace encrypted-key
bytes.  [CVE-2016-0703]

s2_srvr.c overwrites the wrong bytes in the master key when applying
Bleichenbacher protection for export cipher suites.  [CVE-2016-0704]

Obtained from: OpenSSL & FreeBSD

disable roaming in the source code

fix 3 security issues with OpenSSL

fix os

syncup remaining fixes

remove files not used.

add kerberos configuration for OpenSSH

more cleanup

remove some unused code and disable some code that is causing issues

drop not makefile

merge heimdal 1.5.2

rename xlist

merge openssl 1.0.1o

openssl 0.9.8zf

merge OpenSSL 0.9.8zc

merge

Upgrade to OpenSSH 6.6p1 in 0.6-CURRENT

OpenSSL security updates.

remove cvs2svn prop

Merge in OpenSSH 6.4p1

tag

fix tag

Security update for OpenSSL to 0.98y

refresh config.h for 5.8

This commit was generated by cvs2svn to compensate for changes in r5698,
which included commits to RCS files with non-trunk default branches.

remove fbsd tag

remove unused files

remove unused files

remove unused files

remove unused file

resolve conflicts

Revise previous OpenSSL patch:

add SGC and BUF_MEM_grow_clean(3) bug fixes.

telnetd: fix a root exploit from a fixed buffer that was not checked

Restore moduli files from botched OpenSSH update

woot

wow i hate this thing.

add missin files?

What a mess.

revert.

readd entropy.h

readd platform.h

restore includes.h

Resolve merge conflicts.

Resolve merge conflicts

This commit was generated by cvs2svn to compensate for changes in r3677,
which included commits to RCS files with non-trunk default branches.

A double free exists in the SSL client ECDH handling code, when
processing specially crafted public keys with invalid prime
numbers. [CVE-2010-2939]

Enable the new GLOB_LIMIT flag to fix a security vulnerability that is remotely exploitable with sftp daemon.
This enables the patch to libc/gen/glob.c

Update symbols.

resolve merge conflicts

Fix the illegal instructions with libcrytpo stuff linking to openssl.  (sendmail, dovecot, or anything else...)

This is a "feature" of gcc4 that adds illegal instructions to discourage casting certain ways.  How nice.

$MidnightBSD$ (and make the date newer than moduli.c)

Add changes to ssh_namespace.h as new symbols were added since 5.0

re-add files we need lost as part of the botched merge.  DOH.

root == no

-j flags suck.

This commit was generated by cvs2svn to compensate for changes in r2859,
which included commits to RCS files with non-trunk default branches.

OpenSSL security patch

Fix typo. That's what happens when I play WoW and commit at the same time.

Add more missing files.

Move us closer to compiling.

*** empty log message ***

This commit was generated by cvs2svn to compensate for changes in r1963,
which included commits to RCS files with non-trunk default branches.

This commit was generated by cvs2svn to compensate for changes in r1961,
which included commits to RCS files with non-trunk default branches.

Add the blacklists.

Add blacklist feature to OpenSSH to look for Debian style keys

Update for 5.0p1

I gotta be more careful.

$MidnightBSD$

Fix merge conflicts with the version.

Ugh... the default for root login was changed during the course of updating this.  Disable it in the config file by default for now.

$MidnightBSD$

Re-importing Makefile.inc and ssh_namespace.h which were incorrectly removed
when merging earlier.

After configure was run on 4.6p1

adjust the config file a bit.

Merging changes between the the last OpenSSH and 4.6p1

$MidnightBSD$

commit the config change.

Fix OpenSSH import

Fix authentication files based on FreeBSD stable changes.

Change directions for OpenSSH 4.4

Fixing problems with 4.4p1 import

Fix a number of security vulnerabilities in OpenSSL as reported on their website Septmeber 28, 2006.

Adding last few additions for OpenSSH

OpenSSH 4.3 patched files

Upgrade to OpenSSH 4.3 through modified FreeBSD-current sources.

This commit was generated by cvs2svn to compensate for changes in r2, which
included commits to RCS files with non-trunk default branches.