Re: TLS: hostname does not match CN in peer certificate

2012-06-18 Thread Ivan De Masi
stname does not match CN in peer certificate" That message does not exist in the default configuration. Someone added it to the local configuration. Complete output: Sending Access-Request of id 137 to 127.0.0.1 port 1812 User-Name = "user" User-Passwor

Re: TLS: hostname does not match CN in peer certificate

2012-06-18 Thread Ivan De Masi
Am 16.06.2012 00:04, schrieb Frank Ranner: Set the hostname in the ldap conf to match what is in the certificate. You may need to create an entry in /etc/hosts to match. You may be able to get around the mismatch by creating an ldaprc file and setting the parameter that controls the hostname chec

Re: TLS: hostname does not match CN in peer certificate

2012-06-15 Thread Frank Ranner
try > > # radtest user "mypassword" localhost 1 testing123 > > I get the following message: > > Reply-Message = "TLS: hostname does not match CN in peer certificate" > > Complete output: > > Sending Access-Request of id 137 to 127.0.0.1 port 1812 >

Re: TLS: hostname does not match CN in peer certificate

2012-06-15 Thread Alan DeKok
Ivan De Masi wrote: > The access to the ldap server is secured with ssl (not TLS!), so > openladp is listening on port 636. > > When I try > > # radtest user "mypassword" localhost 1 testing123 > > I get the following message: > > Reply-Message =

TLS: hostname does not match CN in peer certificate

2012-06-15 Thread Ivan De Masi
123 I get the following message: Reply-Message = "TLS: hostname does not match CN in peer certificate" Complete output: Sending Access-Request of id 137 to 127.0.0.1 port 1812 User-Name = "user" User-Password = "password" NAS-IP-Address = 1