Dieter Klünterdieter@dkluenter.de schrieb am 27.11.2013 um 11:15 in
Nachricht 20131127111527.0e561508@pink.avci.de:
Am Wed, 27 Nov 2013 09:09:35 +0100 schrieb "Ulrich Windl" Ulrich.Windl@rz.uni-regensburg.de:
Hi!
I found out why I never was successful with cn=monitor: By default '*' attributes show almost nothing; you'll have to use '+' attributes (in my version at least). I'm not very happy with the decision, because you'll get the truely operational attributes also. If the whole subtree cn=Monitor is invisible in naming contexts, I see little reason to hide the "normal" attributes as operational in the whole subtree.
The other thing is that I'm not too happy with are spaces in RDNs, like " cn=Connection 2111,cn=Connections,cn=Monitor", or "cn=Database 2,cn=Databases,cn=Monitor". I'd prefer are more common pattern for IDs like "Connection-2111" or "Connection_2111".
In fact spaces in a commonName attribute value are in accordance with X.520 practice.
Hi!
I believe that, but when printed two spaces look very similar to one space, and as I guess every space is significant, you can probably have "Joe OneSpace" and "Joe TwoSpaces" as RDN. I guess you cannot enter Joue Twospaces with just one space, opening a can of worms...
Regards, Ulrich
-Dieter
-- Dieter Klünter | Systemberatung http://dkluenter.de GPG Key ID:DA147B05 53°37'09,95"N 10°08'02,42"E