General

Profile

Andreas Weigel

  • Registered on: 09.01.2017
  • Last connection: 21.12.2017

Issues

Activity

21.12.2017

15:37 strongSwan Feature #2497: Slightly improve IKEv1 PSK lookup with rightid=%any (e.g. connection1: leftid=left=<IP1> rightid=right=%any connection2: leftid=left=<IP1> rightid=right=<IP2>)
Hi Tobias,
I've tested your changes as a backport against 5.3.5 and against the current master and successfully go...

14.12.2017

11:00 strongSwan Feature #2497: Slightly improve IKEv1 PSK lookup with rightid=%any (e.g. connection1: leftid=left=<IP1> rightid=right=%any connection2: leftid=left=<IP1> rightid=right=<IP2>)
Thanks for the quick reply, Tobias.
> So if you'd just list only the remote IP/ID for secrets with specific IP/IDs...

13.12.2017

13:47 strongSwan Feature #2497 (Closed): Slightly improve IKEv1 PSK lookup with rightid=%any (e.g. connection1: leftid=left=<IP1> rightid=right=%any connection2: leftid=left=<IP1> rightid=right=<IP2>)
Hello everyone,
Again I'm messing with the lookup of PSKs (see #2223).
Affected Versions:...

15.03.2017

10:28 strongSwan Feature #2223: Change PSK lookup order for IKEv1 (first configs/identities, then IPs)
Thanks for the clarification.
09:31 strongSwan Feature #2223: Change PSK lookup order for IKEv1 (first configs/identities, then IPs)

> but if FQDNs are used as local/remote addresses these are resolved when peer configs are looked up. But that look...

14.03.2017

09:08 strongSwan Feature #2223: Change PSK lookup order for IKEv1 (first configs/identities, then IPs)
Thanks for your reply, and thanks for fixing the initiator part (which I have yet to understand, it's been some time ...

16.01.2017

15:12 strongSwan Feature #2223 (Closed): Change PSK lookup order for IKEv1 (first configs/identities, then IPs)
I posted this one on the [strongSwan-dev] mailing list, but unfortunately haven't received any reaction, yet.
Plea...

Also available in: Atom