| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
Fixes: 4af02c6c61cf ("bus: Fix maximum log level for different groups
after removal of a logger")
|
|
|
|
|
| |
Fixes: 622c2b2c3386 ("peer-cfg: Add method to atomically replace child
configs")
|
|
|
|
|
|
|
| |
The log level was incorrectly set to the same value for all groups.
Fixes: dac15e03c828 ("bus: Fix maximum log levels when mixing log/vlog
implementing loggers")
|
|
|
|
| |
Jump to BPF_STMT(BPF_RET+BPF_K, 0) if protocol_size != 4
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Fix for "Permission denied (you must be root)" error when calling
iptc_init(), which opens a RAW socket to communicate with the kernel,
when built with "--with-capabilities=libcap".
Closes strongswan/strongswan#53.
Fixes #2157.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
A wrong variable is used (route instead of best), so much that the
returned interface belongs to the last seen route instead of the best
choice route.
get_route() may therefore return mismatching interface and gateway.
Fixes: 66e9165bc686 ("kernel-netlink: Return outbound interface in get_nexthop()")
Signed-off-by: Christophe Gouault <christophe.gouault@6wind.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far every "newer" CRL (higher serial or by date) replaced an existing
"older" CRL. This meant that delta CRLs replaced an existing base CRL
and that base CRLs weren't added if a delta CRL was already stored. So
the base had to be re-fetched every time after a delta CRL was added.
With this change one delta CRL to the latest base may be stored. A newer
delta CRL will replace an existing delta CRL (but not its base, older
base CRLs are removed, though). And a newer base will replace the existing
base and optional delta CRL.
|
| |
|
|
|
|
|
|
| |
This was added a few years ago because pki --signcrl once encoded serials
incorrectly as eight byte blobs. But still ensure we have can handle
overflows in case the serial is encoded incorrectly without zero-prefix.
|
|
|
|
|
| |
According to RFC 5280 delta CRLs and complete CRLs MUST share one
numbering sequence.
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
| |
Fixes: 40f2589abfc8 ("gmp: Support of SHA-3 RSA signatures")
|
|
|
|
| |
Fixes: 188b190a70c9 ("mgf1: Refactored MGF1 as an XOF")
|
|
|
|
|
|
|
|
|
| |
In case of an empty LDAP result during a CRL fetch (for example, due to
a wrong filter attribute in the LDAP URI, or invalid LDAP configuration),
the call to ldap_result2error() with NULL value for "entry" lead to
a crash.
Closes strongswan/strongswan#52.
|
| |
|
|
|
|
|
|
|
|
| |
one retransmit
The counter is already increased when sending the original message.
Fixes: bd71ba0ffb03 ("task-manager: Add retransmit cleared alert")
|
| |
|
| |
|
|
|
|
|
|
| |
We parse aes*gmac as encryption algorithm, which we have to map to an
integrity algorithm. We also make sure we remove all other encryption
algorithms and ensure there is an integrity algorithm.
|
| |
|
|
|
|
| |
But filter PRFs from ESP proposals.
|
|
|
|
| |
References #2051.
|
|
|
|
| |
Fixes #2051.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We try to detect the type of key by parsing the basic structure of the
passed ASN.1 blob.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If a responder is natted it will usually be a static NAT (unless it's a
mediated connection) in which case adding these notifies makes not much
sense (if the initiator's NAT mapping had changed the responder wouldn't
be able to reach it anyway). It's also problematic as some clients refuse
to respond to DPDs if they contain such notifies.
Fixes #2126.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
charon-nm fails to find the private key when its CKA_ID doesn't match the
subjectKeyIdentifier of the X.509 certificate. In such cases, the private
key builder now falls back to enumerating all the certificates, looking for
one that matches the supplied subjectKeyIdentifier. It then uses the CKA_ID
of that certificate to find the corresponding private key.
It effectively means that PKCS#11 tokens where the only identifier to relate
the certificate, the public key, and the private key is the CKA_ID are now
supported by charon-nm.
Fixes #490.
|
| |
|
|
|
|
| |
It does not have any CHILD_SAs attached at that point.
|
|
|
|
|
| |
After the ISAKMP_DELETE task has been executed the IKE_SA is destroyed
so we wouldn't be able to send deletes for the Quick Mode SAs.
|
|
|
|
|
|
| |
If we silently delete the IKE_SA the other peer might still use it even
if only to send DPDs. If we don't answer to DPDs that might result in the
deletion of the new IKE_SA too.
|
| |
|
| |
|