MatrixSSL 1.8.5

API changes

• Internal API change to accommodate MatrixSSH users.

• Ignore TLS extensions sent with SSL 3.0 ClientHello. Thunderbird sends these extensions if negotiating down from a TLS connection, even though they are meaningless.
• Enhanced the parsing of the Key Usage certificate extension.

• Assure file reads into memory are NULL terminated. This was an issue flagged by Valgrind that doesn't present a problem in practice.
• 2008 copyright update.

• MatrixSSL 1.8.4 was not a public release.

MatrixSSL 1.8.3

API changes

• ‘const’ qualifiers added to literal string parameters for matrixRsaReadPrivKey, matrixRsaReadKeys, matrixRsaReadKeysEx and matrixX509ReadPubKey.

• Additional error reporting in RSA public decryption routine.

• Improved the enforcement of maximum certificate chain length.
• Added the –fPIC compile option to default POSIX builds.
• Fixed one time memory leak on error conditional during certificate parsing.
• 2007 copyright update.

MatrixSSL 1.8.2

API additions

• None

• New "leaky bucket" algorithm for empty message denial-of-service countermeasure. Previously, the count of empty messages was continually being incremented by the MatrixSSL library regardless of any interleaving valid messages. This could potentially cause the connection to be closed if a peer was sending many blank SSL messages. The count will now decrement on valid messages. This change is most relevant to use-cases that involve an OpenSSL client communicating with a MatrixSSL server, as these clients tend to periodically send a blank record.

• None

MatrixSSL 1.8.1

API additions

• None

• Cleaner POSIX cross platform compiles for newer versions of Linux.
• Build support for Intel Macs (tested on OS X 10.4 CoreDuo).

• Minor compile warnings fixed.
• Graceful handling when MAX_CHAIN_LEN limit is exceeded in certificate parsing.
• Added ASN.1 BMPSTRING format support to certificate parsing.
• Fixed matrixSslReadKeysMem so that private key parameter is optional.
• Fixed one time memory leak for client initialization issues that include non-parsable certificates.

MatrixSSL 1.8

API additions

• Addition of two new server APIs that allow the user to add a custom flag value to client sessions. Servers may now assign persistant custom data to connected sessions that can be later retrieved from a session that was established with a session resumption handshake. See the API documentation for matrixSslSetResumptionFlag and matrixSslGetResumptionFlag for more details.

• Ability to put multiple certificates in a single PEM file.
• The handshake will now fail on an un-authenticated cert if no user validation callback has been defined with matrixSslSetCertValidator. It is still encouraged that a callback be registered.
• Users can now reply to a closure alert with a closure alert of their own using matrixSslEncodeClosureAlert. Previously, the SSL_CLOSED flag prevented this. Now only error cases will prevent the closure alert from being created.

• Numerous compile warnings fixed. Especially in the area of unsigned char / char type mismatches.
• Added explicit ‘void’ types to empty parameter functions.
• Fixed a bad shift operation in cipherSuite.c (no functional change).
• Fixed possible memory leak of pre-master secret if deleteSession called on some corner failure cases.
• Fixed compile and link issues when USE_FILE_SYSTEM was turned off in matrixConfig.h.
• Fix for unknown X.509 certificate extension parsing in which the extensions did not provide explicit data lengths in the encoding.
• Fixed parse issue with an empty AuthorityKeyIdentifier certificate extension.
• Created new sample certificates with updated dates.

MatrixSSL 1.7.3

Bug fixes and optimizations

• Fixed issue with certificate extension parsing causing a cert with some unrecognized extensions to fail validation.
• Fixed requirement when USE_CLIENT_SIDE is enabled with ReadKeysMem - CA is no longer required.

MatrixSSL 1.7.1b

Bug fixes and optimizations

• Fixed packaging issue causing a build error on Windows and Linux. No functional change from 1.7.1

MatrixSSL 1.7.1

Bug fixes and optimizations

• Fixed certificate chain parsing bug where a valid certificate chain was marked as invalid under certain circumstances. The result of the fix is that more cert chain configurations are supported.
• Added support for cert validation when the server sends the Root CA cert in addition to the lower levels of the chain. Typically the Root CA cert is loaded into the client, and not sent by the server. We have encountered some deployments where the server does send the root CA as well, and now successfully validate this chain.
• Relaxed parsing of the CertificateSerialNumber field within AuthorityKeyIdentifier. Although officially defined as an ASN.1 INTEGER type, some certificate generators use a non-integer value. Parser now supports these technically incorrect datatypes.

MatrixSSL 1.7

Overall changes

• Explicit support for anonymous RSA handshaking
• New APIs to support anonymous handshaking and re-handshaking over existing connections with new key material

• Version updated from 1.2.5 to 1.7 to mirror commercial MatrixSSL versioning
• Directory and file reorganization

• Significantly accelerated RSA handshake speeds
• Additional parsing of X.509 certificate extensions

MatrixSSL 1.2.5

Overall changes

• No API changes from 1.2.4 release

• Updated expiration date in sample certificates

• Remove unnecessary link to -lcrypto on Linux
• Fix prevTicks compatibility on non-i386 Linux platforms

MatrixSSL 1.2.4

Overall changes

• No API changes from 1.2.2 release
• There was no public 1.2.3 release

• Client will reply with NULL cert message if client authentication is requested.

• Generate static libraries in addition to shared objects on Linux
• AMD64/Nacona x64 compile support on Linux
• Changed all instances of int types to int32 to be more explicit and to allow easy global redefinitions for porting
• Corrected the maximum message size limit to match the SSL specification
• Cert parse can handle duplicate distinguished name entries.
• ASN.1 parse fix for AlgorithmIdentifier missing the trailing NULL
• Checking certificate version before doing checking the 'ca' member of the basic constraint entry during certificate validation.
• Developers may notice some internal routines using a psPool_t parameter. These parameters allow deterministic memory support in the commercial version of MatrixSSL. They are unused in the GNU version of MatrixSSL.

MatrixSSL 1.2.2

Functional changes

• Added legacy certificate support

- for certificates without basic constraints
- MD2 support for older certificates (Because it is a less secure algorithm, it must be explicitly enabled).

• Sanity check against invalid key lengths from certificate (potential DOS fix)
• Fixed 64 bit issue with mpi.c
• Fix potential leak in certificates with duplicate fields
• Allow application data parsing within re-handshake state