| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
PolicyConstraints, too
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
supported algorithms
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
encoding
|
| |
|
| |
|
|
|
|
|
| |
That is, enable compilation if OpenSSL was configured with
OPENSSL_NO_ENGINE.
|
|
|
|
|
| |
That is, enable compilation if OpenSSL was configured with
OPENSSL_NO_EC.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
settings in libstrongswan.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
not have to replicate them in every plugin that implements the DH interface.
The main reason for this change is that Android's libcrypto does not
include the get_rfcX_prime_Y functions by default. Therefore we would
have had to replicate the primes a third time.
|