| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | openssl: Fix AES-GCM with BoringSSL | Tobias Brunner | 2016-10-11 | 1 | -3/+3 |
| | | | | | | | | | BoringSSL only supports a limited list of (hard-coded) algorithms via EVP_get_cipherbyname(), which does not include AES-GCM. While BoringSSL deprecated these functions they are also supported by OpenSSL (in BoringSSL a completely new interface for AEADs was added, which OpenSSL currently does not support). | ||||
| * | openssl: Update GCM/crypter API to OpenSSL 1.1.0 | Tobias Brunner | 2016-06-29 | 1 | -13/+13 |
| | | |||||
| * | aead: Support custom AEAD salt sizes | Martin Willi | 2014-03-31 | 1 | -1/+9 |
| | | | | | | | | | | The salt, or often called implicit nonce, varies between AEAD algorithms and their use in protocols. For IKE and ESP, GCM uses 4 bytes, while CCM uses 3 bytes. With TLS, however, AEAD mode uses 4 bytes for both GCM and CCM. Our GCM backends currently support 4 bytes and CCM 3 bytes only. This is fine until we go for CCM mode support in TLS, which requires 4 byte nonces. | ||||
| * | iv_gen: aead_t implementations provide an IV generator | Tobias Brunner | 2013-10-11 | 1 | -0/+15 |
| | | |||||
| * | openssl: The EVP GCM interface requires at least OpenSSL 1.0.1 | Tobias Brunner | 2013-03-01 | 1 | -0/+6 |
| | | |||||
| * | openssl: Provide AES-GCM implementation | Tobias Brunner | 2013-02-28 | 1 | -0/+259 |
 |
index : tteras/strongswan | |
| tteras' strongSwan tree | gitolite |
| aboutsummaryrefslogtreecommitdiffstats |