[ldap] Re: Entering a 'NULL' character
Well, that's the kind of detail we need to help. Good luck. :) -Original Message- From: [email protected] [mailto:[email protected]] On Behalf Of Jerry Sent: Wednesday, June 24, 2009 4:32 AM To: General LDAP discussion list Subject: [ldap] Re: Entering a 'NULL' character On Tue, 23 Jun 2009 22:29:07 -0500 "Dustin Puryear" wrote: > I agree with Jerry and others. You'll need to put something, and > something unmistakable like "-" would do the trick. Putting in control > characters may actually break scripts (even though, technically, the > script writer should write better code). > > Why are you using inetOrgPerson if you don't need that field? If you > are forcing data fields to behave in odd ways, then perhaps you're > using the wrong object class. > > In other words, there may be a better way to solve this problem > entirely. I am using the "mozillaOrgPerson" schema which has a dependency on "inetOrgPerson". -- Jerry [email protected] Journalism will kill you, but it will keep you alive while you're at it.
[ldap] Re: Entering a 'NULL' character
On Tue, 23 Jun 2009 22:29:07 -0500 "Dustin Puryear" wrote: > I agree with Jerry and others. You'll need to put something, and > something unmistakable like "-" would do the trick. Putting in control > characters may actually break scripts (even though, technically, the > script writer should write better code). > > Why are you using inetOrgPerson if you don't need that field? If you > are forcing data fields to behave in odd ways, then perhaps you're > using the wrong object class. > > In other words, there may be a better way to solve this problem > entirely. I am using the "mozillaOrgPerson" schema which has a dependency on "inetOrgPerson". -- Jerry [email protected] Journalism will kill you, but it will keep you alive while you're at it.
[ldap] RE: Entering a 'NULL' character
I agree with Jerry and others. You'll need to put something, and something unmistakable like "-" would do the trick. Putting in control characters may actually break scripts (even though, technically, the script writer should write better code). Why are you using inetOrgPerson if you don't need that field? If you are forcing data fields to behave in odd ways, then perhaps you're using the wrong object class. In other words, there may be a better way to solve this problem entirely. -Original Message- From: [email protected] [mailto:[email protected]] On Behalf Of Gerard Seibert Sent: Tuesday, June 23, 2009 1:21 PM To: [email protected] Subject: [ldap] Entering a 'NULL' character Is it possible to enter a 'NULL' character into a LDIF field? In some cases, I do not have a legitimate surname to enter in the sn: field. The inetorgperson.schema requires it. I tried this: sn:: IA== I thought I could enter the base64 representation of a space; however, that does not work. i receive an error message. I would like to enter a true NULL but that doesn't seem possible.
[ldap] Re: Entering a 'NULL' character
Jerry wrote: > On Tue, 23 Jun 2009 15:26:59 -0400 > Terry Gardner wrote: > >> The 'sn' attribute is required to be present and populated in >> entries that have the 'inetOrgPerson' objectClass, that is, >> 'inetOrgPerson' should be used where a fully populated entry is >> available - it is a "MUST" attribute, not a "MAY" attribute. > > I realize that. Unfortunately, I cannot leave it blank, not can I > simply enter a character in a normal fashion. I had thought > that I could use base64 encoding to enter a character; i.e., > IA== however, that does not seem to be working even when I use the > double :: colon marks and I am not sure why. > > In order to get around this, I am being forced to manually enter a N/A > entry into the field. I've successfully used "sn:: IA==" in LDIF before. What's the entry you're trying to enter look like, and what's the error message? -- James Andrewartha
[ldap] Re: Entering a 'NULL' character
Jerry writes: > I realize that. Unfortunately, I cannot leave it blank, not can I > simply enter a character in a normal fashion. I had thought > that I could use base64 encoding to enter a character; i.e., > IA== however, that does not seem to be working even when I use the > double :: colon marks and I am not sure why. The problem is easier to guess if you say what the error message is and which implementation. I think it should be allowed, but I'm not surprised if some servers reject such an attribute. Which is my guess so far. BTW, it'd work - wrongly - without the '::' since that just stores a plain "IA==" string in the directory:-) Base64 here is only releated to the LDIF file format, the client decodes it before sending to the server. Also note that your original question about a NULL character does not make sense, chr(0) - a control character - is not what you'd want. Even if the C langauge happens to treat it as empty if it is treated as a C string and not a binary value. > In order to get around this, I am being forced to manually enter a N/A > entry into the field. Yup. Might use something like "sn: -" instead - then e.g. a substring search for (sn=N*) won't return it. -- Hallvard
[ldap] Re: Entering a 'NULL' character
On Tue, 23 Jun 2009 15:26:59 -0400 Terry Gardner wrote: > The 'sn' attribute is required to be present and populated in > entries that have the 'inetOrgPerson' objectClass, that is, > 'inetOrgPerson' should be used where a fully populated entry is > available - it is a "MUST" attribute, not a "MAY" attribute. I realize that. Unfortunately, I cannot leave it blank, not can I simply enter a character in a normal fashion. I had thought that I could use base64 encoding to enter a character; i.e., IA== however, that does not seem to be working even when I use the double :: colon marks and I am not sure why. In order to get around this, I am being forced to manually enter a N/A entry into the field. By the way Terry, please do not CC: or send me directly. I am a member of the list and will receive the reply normally. -- Jerry [email protected] A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? TOPIC: Posting Etiquette
[ldap] Re: Entering a 'NULL' character
The 'sn' attribute is required to be present and populated in entries that have the 'inetOrgPerson' objectClass, that is, 'inetOrgPerson' should be used where a fully populated entry is available - it is a "MUST" attribute, not a "MAY" attribute. On Jun 23, 2009, at 2:21 PM, Gerard Seibert wrote: Is it possible to enter a 'NULL' character into a LDIF field? In some cases, I do not have a legitimate surname to enter in the sn: field. The inetorgperson.schema requires it. I tried this: sn:: IA== I thought I could enter the base64 representation of a space; however, that does not work. i receive an error message. I would like to enter a true NULL but that doesn't seem possible. smime.p7s Description: S/MIME cryptographic signature
