[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Hostname does not match common name problem

To: Sascha <SaschaGL@gmx.de>
Subject: Re: Hostname does not match common name problem
From: Michael Ströder <michael@stroeder.com>
Date: Sat, 14 Mar 2009 21:38:03 +0100
Cc: openldap-technical@openldap.org
In-reply-to: <1642BBE8-8C60-4ECF-9C3E-1E56D9A88F01@gmx.de>
References: <20090313103013.128730@gmx.net> <49BB933C.6070201@stroeder.com> <2F9032CE0C434CCB5B7237FF@[192.168.1.199]> <1642BBE8-8C60-4ECF-9C3E-1E56D9A88F01@gmx.de>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.21) Gecko/20090303 SeaMonkey/1.1.15

Sascha wrote:
> 
> It is an old-ish version of OpenLDAP (2.0.x I think) that we are using.

You really should update this setup for various reasons. Most notably
because auf possible data loss in this version. Note that this might
require sanitizing the current data since recent OpenLDAP versions are
more strict regarding schema checking than 2.0. And in 2.4 you can't
turn off schema checking anymore.

Ciao, Michael.

References:
- Hostname does not match common name problem
  - From: "Sascha" <SaschaGL@gmx.de>
- Re: Hostname does not match common name problem
  - From: Michael Ströder <michael@stroeder.com>
- Re: Hostname does not match common name problem
  - From: Quanah Gibson-Mount <quanah@zimbra.com>
- Re: Hostname does not match common name problem
  - From: Sascha <SaschaGL@gmx.de>

Prev by Date: Re: Hostname does not match common name problem
Next by Date: smbk5pwd - slapd stops responding
Index(es):
- Chronological
- Thread