I am also not a C programmer. I've not even looked at patch at this point.
I agree best practice says hostname are limited to specific ASCII characters.
And underscore are indeed not included.
However DNS name in general only have very few restriction (RFC2181) (2).
I did some tests using the
andrew.lawre...@siemens.com wrote:
> --_004_4CF710229787A0419BF92C9304DC6446E7927ADEFTHW99EI5MSXww9_
> Content-Type: multipart/alternative;
> boundary="_000_4CF710229787A0419BF92C9304DC6446E7927ADEFTHW99EI5MSXww9_"
>
> --_000_4CF710229787A0419BF92C9304DC6446E7927ADEFTHW99EI5MSXww9_
>
SGkgTWljaGFlbCwNCg0KTXkgZ29hbCB3YXMgdG8gb25seSBhbGxvdyB2YWxpZCBob3N0bmFtZXMg
d2hlbiB1c2luZyB0aGUgLWggb3B0aW9uLiBBICBiaXByb2R1Y3Qgb2YgdGhpcyBpcyB0aGF0IGxk
YXAgdXJpcyBhcmUgYWxzbyByZWplY3RlZC4NCg0KVGhlIHBhdGNoIHJlamVjdHMgaG9zdG5hbWVz
andrew.lawre...@siemens.com wrote:
> I believe the following patch addresses this problem. I am still a
> bit conf used about what constitutes a DNS name. Alex has suggested
> they should contain an underscore. My colleague who reviewed the code
> had a different opinion.
Disclaimer: Since I'm not
--_004_4CF710229787A0419BF92C9304DC6446E7927ADEFTHW99EI5MSXww9_
Content-Type: multipart/alternative;
boundary="_000_4CF710229787A0419BF92C9304DC6446E7927ADEFTHW99EI5MSXww9_"
--_000_4CF710229787A0419BF92C9304DC6446E7927ADEFTHW99EI5MSXww9_
Content-Type: text/plain; charset="iso-8859-1"
Full_Name: Muthamma
Version: 2.4 and 2.3
OS:
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (2620:160:e708:6::a)
Hi team,
Could you confirm if the product OpenLDAP is a stand-alone product or embedded?
