Jonas Norling 277598e34a Use same sequence number calculation in tls.c and internal.c ...

The DTLS sequence number used when decrypting CCM/GCM was taken from
the internal state, instead of from the actual message record.

If any DTLS messages were dropped, the expectation of the next
sequence number was wrong. This lead to a failed MAC check on the next
message to arrive, and an alert was generated.

2014-07-28 15:10:17 -07:00

..

crl.c

crl: refactoring LoadCRL to reduce stack usage:

2014-07-21 22:52:06 -03:00

include.am

uses most recent version of cyassl

2014-07-10 11:18:49 -06:00

internal.c

Use same sequence number calculation in tls.c and internal.c

2014-07-28 15:10:17 -07:00

io.c

io: refactoring EmbedOcspLookup:

2014-07-23 13:20:23 -03:00

keys.c

added ECDSA and DHE_RSA support for chacha-poly

2014-07-10 16:35:56 -06:00

ocsp.c

ocsp: refactoring CheckCertOCSP to reduce stack usage:

2014-07-21 22:52:05 -03:00

sniffer.c

uses most recent version of cyassl

2014-07-10 11:18:49 -06:00

ssl.c

refactoring

2014-07-17 15:00:40 -06:00

tls.c

uses most recent version of cyassl

2014-07-10 11:18:49 -06:00