On Sun, Jun 28, 2015 at 11:53 PM, Martin Willi mar...@strongswan.org
wrote:
tiple auth methods, we'd have to
return all of them (for example using a bit-set), and use these methods
in main/aggressive_mode.c to select the appropriate
Hi Martin,
Thanx for the reply. Yes, I realized from the
Hi,
[...] when the cisco initiates a connection with both the
transforms, the RSA-SIG being first in the list, strongswan replies back
with a proposal that contains RSA-SIG, because it is the first in the list,
even though the connection is defined as PSK.
Is this a bug and is there a way
Hi,
It seems that strongswan does not consider the authentication type in the
configuration when selecting proposals. I have a cisco device which is
configured with two transform proposals, one for rsa-sig and and one for
PSK. Strongswan is configured with a connection definition that uses PSK
