../
|
apache/
|
7721
(7 years ago)
by laffer1:
update cstd
|
bin/
|
8803
(7 years ago)
by laffer1:
document P_PTRACE.
|
cddl/
|
8842
(7 years ago)
by laffer1:
Fix a bunch of ZFS issues. zpool create/syseventd race yield non-importable pool. first write to new zvol can fail with EFBIG. Type change in refcount.h vendor zfs fix for arc_read. fix panic in arc_read, add tunable to allow block allocation on degraded vdevs. SA rounding, header size and lyout fix. fix rounding issues. merge zfs_ioctl.c code that was never commited from ZFS v28.
|
contrib/
|
8814
(7 years ago)
by laffer1:
add print-file-name=include
|
crypto/
|
8594
(7 years ago)
by laffer1:
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]
|
etc/
|
8851
(7 years ago)
by laffer1:
remove largest suffix instead of smallest
|
games/
|
8731
(7 years ago)
by laffer1:
delete politcal stuff
|
gnu/
|
8813
(7 years ago)
by laffer1:
regen after header improvements.
|
include/
|
8699
(7 years ago)
by laffer1:
add write suspension mechanism.
|
kerberos5/
|
8155
(7 years ago)
by laffer1:
partial revert of last commit
|
lib/
|
8855
(7 years ago)
by laffer1:
add link
|
libexec/
|
8833
(7 years ago)
by laffer1:
remove workarounds
|
nrelease/
|
6469
(10 years ago)
by laffer1:
remove cvs2svn prop
|
release/
|
7801
(7 years ago)
by laffer1:
add additional exclusions to src tarball
|
rescue/
|
8775
(7 years ago)
by laffer1:
Allow zfs jail and zfs unjail to use both jailnames and jailid
|
sbin/
|
8834
(7 years ago)
by laffer1:
teach dhclient to track changes in link state
|
secure/
|
7462
(8 years ago)
by laffer1:
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
|
share/
|
8850
(7 years ago)
by laffer1:
update man page
|
sys/
|
8857
(7 years ago)
by laffer1:
reshuffle the bios.h headers
|
tools/
|
8772
(7 years ago)
by laffer1:
add clang options
|
usr.bin/
|
8833
(7 years ago)
by laffer1:
remove workarounds
|
usr.sbin/
|
8856
(7 years ago)
by laffer1:
display the matrix of inter-domain distances in the SLIT table.
|
COPYRIGHT
|
7391
(8 years ago)
by laffer1:
Happy New Year.
|
Makefile
|
8512
(7 years ago)
by laffer1:
fix a goof
|
Makefile.inc1
|
8593
(7 years ago)
by laffer1:
add bin to path
|
ObsoleteFiles.inc
|
8557
(7 years ago)
by laffer1:
add old dirs
|
README
|
6517
(10 years ago)
by laffer1:
turn on svn keywords
|
UPDATING
|
8741
(7 years ago)
by laffer1:
update new feature list for today
|