[strongSwan] Problem using asymmetric keys against Cisco IOS

John Serink john_serink at trimble.com
Tue Dec 8 15:33:32 CET 2020

ok, got it.
@# is the ticket.

Sent from my BlackBerry — the most secure mobile device

	  Original Message  	

From: tobias at strongswan.org
Sent: 8 December 2020 10:28 PM
To: john_serink at trimble.com; users at lists.strongswan.org
Subject: Re: [strongSwan] Problem using asymmetric keys against Cisco IOS

Hi John,

> It identified my strongswan client CORS89 but it thinks its an FQDN rather than and ID.
> In the ipsec.conf for leftid I used '@CORS89' and in the ipsec.secrets I also used @CORS89 so
> why would the Cisco think its a FQDN rather than just a key-id?

Of course it's a FQDN, why would you think prefixing it with an @
changes that?  Please see [1].


[1] https://wiki.strongswan.org/projects/strongswan/wiki/IdentityParsing

More information about the Users mailing list