Displaying 4 results from an estimated 4 matches for "aead_aes_256_gcm".
2016 May 30
2
Need stronger SRTP ciphers (256 bit)
Hi folks,
At least several endpoints (soft phone and desk phones) are supporting various 256 bit ciphers for SRTP these days. I *believe* libsrtp has been updated to allow this, and that only the code in Asterisk has not been been updated to allow these stronger ciphers.
Would anyone with the know-how be willing/able to submit a patch ?
Thank you,
Kevin Long
2013 Sep 10
0
[Bug 1647] Implement FIPS 186-3 for DSA keys
...thms you want to allow.
>
> It appears that OpenSSH has added support for SHA-256 and SHA-512 in
> version 5.9p1 (2011-09).
RFC 6668 is good if you want to use something like the Cipher aes128-cbc
with hmac-sha2-256 or hmac-sha2-512 as the MAC instead of implementing
AEAD_AES_128_GCM or AEAD_AES_256_GCM.
The way that RFC 5647 is written makes it hard to do the right thing
when the Cipher and Macs are negotiated separately as both have to agree
and having one of the AEAD_* ciphers with some other MAC just makes no
sense, but has no provision for forcing the two to be sane during
negotiations.
The...
2013 Sep 10
4
[Bug 1647] Implement FIPS 186-3 for DSA keys
https://bugzilla.mindrot.org/show_bug.cgi?id=1647
mackyle at gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mackyle at gmail.com
--- Comment #2 from mackyle at gmail.com ---
RFC 6668 [1] (2012-07) updated RFC 4253 adding the SHA-256 data
2013 Sep 10
4
[Bug 1647] Implement FIPS 186-3 for DSA keys
https://bugzilla.mindrot.org/show_bug.cgi?id=1647
mackyle at gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mackyle at gmail.com
--- Comment #2 from mackyle at gmail.com ---
RFC 6668 [1] (2012-07) updated RFC 4253 adding the SHA-256 data