| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The original name is returned in the new "name" attribute.
This fixes an issue with bindings that map VICI messages to
dictionaries. For instance, in roadwarrior scenarios where every
CHILD_SA has the same name only the information of the last CHILD_SA
would end up in the dictionary for that name.
|
|
|
|
| |
sections
|
|
|
|
| |
Probably not that useful via swanctl.conf but could be when used via VICI.
|
| |
|
|
|
|
|
|
|
| |
PINs are stored in a "hidden" credential set, so that its shared
secrets are not exposed via VICI. Since they are not explicitly loaded as
shared secrets via VICI a client might consider them as removed secrets and
remove them.
|
|
|
|
| |
The two names are also transmitted in separate keys.
|
|
|
|
| |
Also adds an `ike` parameter to the `uninstall` command.
|
|
|
|
|
| |
The same goes for the start-action-job. When unrouting, we search for
the first policy with a matching child-cfg.
|
|
|
|
|
| |
This will allow us to reuse the names of child configs e.g. when they
are defined in different connections.
|
|
|
|
| |
Fixes #1002.
|
| |
|
| |
|
|
|
|
| |
Fixes #2170.
|
|
|
|
|
| |
This identifier can be set when adding/replacing a secret. The unique
identifiers of all secrets may be enumerated.
|
|
|
|
| |
They are identified by their SHA-1 key identifier.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
After an interface disappeared we can't remove the policies correctly as
the name doesn't resolve to the previous index anymore.
And making the policies so specific might not provide that much benefit.
To handle the interfaces on the policies correctly would require some
changes to the child-cfg, kernel-interface etc. so they'd take interface
indices directly so we could target the policies correctly even if an
interface disappeared (or reappeared and got a new index).
|
|
|
|
|
|
|
| |
For table dumps the kernel accepts RTA_PREFSRC to filter the routes, which is
what we do when doing userspace route calculations. For kernel-based route
lookups, however, the RTA_PREFSRC attribute is ignored and we must specify
RTA_SRC for policy based route lookups.
|
|
|
|
|
|
|
|
|
|
|
|
| |
For gateways with many connections, installing routes is often disabled,
as we can use a static route configuration to achieve proper routing with
a single rule. If this is the case, there is no need to dump all routes and
do userspace route lookups, as there is no need to exclude routes we installed
ourself.
Doing kernel-based route lookups is not only faster with may routes, but also
can use the full power of Linux policy based routing; something we can hardly
rebuild in userspace when calculating routes.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When using vici over RPyC and its (awesome) splitbrain, encoding and decoding
strings fails in vici, most likely because of the Monkey-Patch magic splitbrain
uses.
When specifying the implicit UTF-8 as encoding scheme explicitly, Python uses
the correct method to encode/decode the string, making vici useable in
splitbrain contexts.
|
| |
|
|
|
|
| |
The config can also be reloaded by sending a SIGHUP to charon.
|
|
|
|
|
| |
Currently, only the kernel-netlink plugin supports this, the others will
just ignore it.
|
| |
|
| |
|
|
|
|
| |
subnets
|
| |
|
|
|
|
| |
Same as the change in the kernel-netlink plugin.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While trap and regular policies now often look the same (mainly because
reqids are kept constant) trap policies still need to have a lower priority
than regular policies to handle unroute/route correctly if e.g. IPComp
is used or the mode changes. But if we use a completely different
priority range that's lower than that of regular policies it is not possible
to install overlapping trap policies. By differentiating trap from
regular policies via the priority's LSB this issue is avoided while
still maintaining the proper ordering of trap and regular policies.
Fixes #1243.
|
| |
|
|
|
|
| |
Closes strongswan/strongswan#62.
|
|
|
|
| |
Fixes #2238.
|
|
|
|
|
|
|
| |
The Optimistic Duplicate Address Detection (DAD) seems to fail in some
cases (`dadfailed` in `ip addr`) rendering the virtual IP address unusable.
Fixes #2183.
|
|
|
|
|
|
|
|
| |
This implements rule 6 of RFC 6724 using the default priority table,
so that e.g. global addresses are preferred over ULAs (which also have
global scope) when the destination is a global address.
Fixes #2138.
|
|
|
|
|
|
|
|
| |
By default, the kernel incorrectly uses an 8 byte alignment, which is
mandatory for IPv6 but prohibited for IPv4. For many algorithms this
doesn't matter but that's not the case for HMAC_SHA2_256_128.
Since 2.6.39 the kernel can be explicitly configured to use a 4 byte
alignment.
|
|
|
|
| |
Signed-off-by: Thomas Egerer <thomas.egerer@secunet.com>
|
|
|
|
|
|
|
| |
Picky kernels might otherwise reject our messages as RFC 2367 explicitly
mandates this.
Fixes #2212.
|
|
|
|
| |
than the destination
|
|
|
|
|
|
|
| |
Otherwise, we'd end up with an empty TS list, which is not valid.
Because end->tohost is set to !end->subnets in starter the removed branch was
never used.
|
| |
|
|
|
|
| |
Fixes #2146.
|
|
|
|
| |
Fixes #1192.
|
|
|
|
| |
Signed-off-by: Thomas Egerer <thomas.egerer@secunet.com>
|
| |
|
|
|
|
|
|
|
| |
The Python VICI library does not check if the socket is closed.
If the daemon closes the connection, _recvall() spins forever.
Closes strongswan/strongswan#56.
|
|
|
|
| |
The kernel apparently supports this since 3.10.
|