Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
W.: Re: Aw: Re: Special characters in distinguished name
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
chris_n...@arcor.de  
View profile  
 More options Jul 31 2012, 4:37 am
Newsgroups: perl.ldap
From: chris_n...@arcor.de
Date: Tue, 31 Jul 2012 10:37:04 +0200 (CEST)
Local: Tues, Jul 31 2012 4:37 am
Subject: W.: Re: Aw: Re: Special characters in distinguished name
 Dear Philip,

thank you for the fix. I'll forward it to Perl's LDAP List and Graham.

@Graham: could you add the attached fix to Net::LDAP::LDIF?

Thank you in advance.

- Chris

----- Original Nachricht ----
Von:     Philip Guenther <guenther+ldapt...@sendmail.com>
An:      chris_n...@arcor.de
Datum:   31.07.2012 07:12
Betreff: Re: Aw: Re: Special characters in distinguished name

On Tue, 31 Jul 2012, chris_n...@arcor.de wrote:
> > > I've accidentally discovered that CPAN's Net::LDAP::Entry module doesn't
> > > support them (in the distinguished name). Other attributes are escaped
> > > correctly.

> > What exactly leads you to this conclusion?

> I setup the DN with $entry->dn($dn); and generated with write_entry an
> LDIF-file. The DN wasn't base 64 encoded. I could encode it myself, but
> then the second colon is still missing. So I probably won't use this
> library.

Or, you could submit the one line fix to have
        Net::LDAP::LDIF->new($file, $mode, { encode => 'canonical' })

pass "{ mbcescape => 1 }" to canonical_dn().

(Some might also consider it a bug that Net::LDAP::LDIF doesn't default to
RFC conforming output but rather requires you to explicitly request it.)

Philip Guenther


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »