| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Newer NDKs fail otherwise as there is no actual module anymore.
|
| |
| |
| |
| |
| |
| | |
This bunches several log messages together before posting Runnables.
Fixes #2148.
|
| |
| |
| |
| |
| | |
When the bound state service finally connects we might not actually be
attached to an Activity.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
registered once
We register when the service connects but also in onStart() (as we
unregister in onStop() to avoid updates when not shown). So this could
theoretically cause the listener to get registered twice if the service
is connected before onStart() is called (it seems it usually isn't).
|
| |
| |
| |
| |
| | |
This is useful in case the proper MIME type was not set for a downloaded
profile.
|
| |
| |
| |
| | |
Courtesy of Chris Chiang.
|
| | |
|
|/ |
|
|
|
|
| |
Fixes #2370.
|
|
|
|
|
|
|
|
|
| |
If we find a redundant CHILD_SA (the peer probably rekeyed the SA before
us) we might not want to delete the old SA because the peer might still
use it (same applies to old CHILD_SAs after rekeyings). So only delete
them if configured to do so.
Fixes #2358.
|
| |
|
|
|
|
|
|
| |
`start` is basically the same thing.
Fixes #2362.
|
| |
|
|
|
|
|
| |
When an expire is triggered while rekeying, the CHILD_SA might be deleted
while the returned host is still used to queue a rekey job for the CHILD_SA.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Fixes: CVE-2017-9023
|
| |
|
|
|
|
| |
Fixes: CVE-2017-9023
|
|
|
|
|
|
|
|
|
| |
Unlike mpz_powm() its secure replacement mpz_powm_sec() has the additional
requirement that the exponent must be > 0 and the modulus has to be odd.
Otherwise, it will crash with a floating-point exception.
Fixes: CVE-2017-9022
Fixes: 3e35a6e7a1b0 ("Use side-channel secured mpz_powm_sec of libgmp 5, if available")
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
traffic_selector_t::to_subnet() always sets the net/host (unless the
address family was invalid).
Fixes: 3070697f9f7c ("ike: support multiple addresses, ranges and subnets in IKE address config")
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Interestingly, this doesn't show up in the regression tests because the
compiler removes the first assignment (and thus the allocation) due to
-O2 that's included in our default CFLAGS.
|
|
|
|
|
|
|
|
| |
When charon is started via service command LEAK_DETECTIVE_LOG is not set
because the command strips the environment. Since we only want the
variable to be set during the automated test runs we can't just set it
in /etc/default/charon. Instead, we do so in this wrapper when charon is
started and remove the variable again when it is stopped.
|
| |
|
|
|
|
|
| |
Also reorders the input files so the READMEs are listed first in the
navigation menu on the left.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds several changes to enumerator_t and linked_list_t to improve
portability. In particular to Apple's ARM64 iOS platform, whose calling
convention for variadic and regular functions are different. This means
that assigning a non-variadic function to a variadic function pointer,
as we did with our enumerator_t::enumerate() implementations and several
callbacks, will result in crashes as the called function will access the
arguments differently than the caller provided them.
To avoid this issue the enumerator_t interface is now fully variadic.
A new mandatory method is added, venumerate(), that takes a va_list with
the arguments provided while enumerating. enumerate() is replaced with
a generic implementation that prepares a va_list and calls the
enumerator's venumerate() implementation. As this allows passing the
arguments of one enumerator to another it avoids the five pointer hack
used by enumerator_create_nested() and enumerator_create_cleaner().
To simplify the implementation of venumerate() a helper macro is provided
that assigns values from a given va_list to local variables.
The signature of the callback passed to enumerator_create_filter() has
also changed significantly. It's now required to enumerate over the
original enumerator in the callback as this avoids the previous in/out
pointer hack. The arguments to the outer enumerator are provided in a
va_list.
Similar changes to avoid such five pointer hacks affect the signatures
of the callbacks for linked_list_t's invoke_function() and find_first()
methods. For the latter the return type also changed from status_t to
bool, which is important as SUCCESS is defined as 0, so checks for ==
SUCCESS will now fail.
|
| |
| |
| |
| | |
This avoids the unportable five pointer hack.
|
| |
| |
| |
| | |
This avoids the unportable five pointer hack.
|
| | |
|
| |
| |
| |
| |
| | |
This avoids the unportable 5 pointer hack, but requires enumerating in
the callback.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will allow us to implement e.g. enumerator_cleaner without having to
use that unportable 5 pointer forwarding or having to define a callback for
each instance.
A generic implementation for enumerate() is provided so only venumerate()
has to be implemented, which may be simplified by using the VA_ARGS_VGET()
macro.
|
|/ |
|
|
|
|
|
|
|
| |
Since 6a8a44be88b0 the certificate received by the client is verified
first, before checking the cached certificates for any with matching
identities. So we usually don't have to attempt to verify the signature
with wrong certificates first and can avoid this message.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Adds an option to locally configure 96-bit truncation for HMAC-SHA256
when negotiated using the official algorithm identifier. This is for
compatibility with peers that incorrectly use this shorter truncation
(like Linux does by default).
Fixes #1353.
|