Re: [strongSwan] eap-md5: constraint requires public key authentication, but EAP was used

2015-02-11 Thread Tobias Brunner
Hi Michael, > no. the problem was that in the destict TNC documentation > > https://wiki.strongswan.org/projects/strongswan/wiki/TrustedNetworkConnect > and > the links in this site there is no mentioning switching off > multiple_authentication in charon.conf: > > multiple_authentication = no

Re: [strongSwan] eap-md5: constraint requires public key authentication, but EAP was used

2015-01-16 Thread Michael Schwartzkopff
Am Freitag, 16. Januar 2015, 11:32:36 schrieb Martin Willi: > Hi, > > > constraint requires public key authentication, but EAP was used > > selected peer config 'test' inacceptable: constraint checking failed > > > > On the server side I have: > > leftauth=eap-ttls > > rightauth=e

Re: [strongSwan] eap-md5: constraint requires public key authentication, but EAP was used

2015-01-16 Thread Martin Willi
Hi, > constraint requires public key authentication, but EAP was used > selected peer config 'test' inacceptable: constraint checking failed > > On the server side I have: > leftauth=eap-ttls > rightauth=eap-ttls > and on the client side I have: > leftauth=eap If you wan

[strongSwan] eap-md5: constraint requires public key authentication, but EAP was used

2015-01-16 Thread Michael Schwartzkopff
Hi, I want to test a TNC setup according to https://wiki.strongswan.org/projects/strongswan/wiki/TNCS https://wiki.strongswan.org/projects/strongswan/wiki/TNCC The authentication should be EAP-MD5, so the first sample on the web site. I think I did follow the doc quite close, but I am stuck with