Jun Hu

03:50 strongSwan Issue #3259: Question: RFC7427 hashalg speccified in ipsec.conf also mandatates the hash alg used in peer's certificate?: sorry, pls ignore this, Just realize I need to add "ike:" prefix
03:45 strongSwan Issue #3259 (Closed): Question: RFC7427 hashalg speccified in ipsec.conf also mandatates the hash alg used in peer's certificate?: Strongswan 5.8.1, using RFC72472, as tunnel responder, using following config, peer includes only sha256 in Hash Algo...

21:01 strongSwan Issue #3200: ECP384 Diffie-Hellman fail in 5.8.1: Tobias Brunner wrote:
> You don't have a plugin loaded that provides that DH algorithm. See [[IKEv2CipherSuites#Diff...

23:50 strongSwan Issue #3200 (Closed): ECP384 Diffie-Hellman fail in 5.8.1: OS: linux
with 5.8.1, when using ecp384 as DH group, the strongswan rejects proposal despite its config has ecp384...

06:15 strongSwan Feature #2189 (Assigned): Support RFC 8229: TCP Encapsulation of IKE and IPsec Packets: There is new IETF ipsecme group draft draft-ietf-ipsecme-tcp-encaps, which defines a standard way to encapsulate IKE/...

20:09 strongSwan Issue #2186: Windows 7 client can't connect to strongswan 5.5.0, windows error 13801: OK, I found the cause; the problem is fixed after I added the intermediate CA certificate in ipsec.d/cacerts/ and str...
19:43 strongSwan Issue #2186: Windows 7 client can't connect to strongswan 5.5.0, windows error 13801: Tobias Brunner wrote:
> [...]
>
> Make sure you have the _eap-identity_ plugin loaded.
I recompiled strongswan...
06:06 strongSwan Issue #2186: Windows 7 client can't connect to strongswan 5.5.0, windows error 13801: I changed the strongswan certificate to a lets encrypt issued cert, same problem
(sorry for the mess of original pos...
05:25 strongSwan Issue #2186 (Closed): Windows 7 client can't connect to strongswan 5.5.0, windows error 13801: Hi,
I followed offical Wiki page: https://wiki.strongswan.org/projects/1/wiki/Windows7 to setup the windows 7 client...

Also available in: Atom

strongSwan