Control: tags -1 + upstream confirmed Control: forwarded -1 http://projects.martini.nu/shelldap/ticket/10
Hi Dominik
On Sat, Oct 06, 2012 at 11:53:58PM +0200, Dominik George wrote:
> Package: shelldap
> Version: 0.5-2
> Severity: normal
>
> Having RDNs like "cn=Foo Bar" causes unexpected behaviour for some commands.
>
> - edit cn=Foo Bar - works
> - cat cn=Foo Bar - expects ""
> - cd cn=Foo Bar - works
> - rm cn=Foo Bar - expects ""
>
> All commands should expect "" for RDNs with spaces to not produce unexpected
> behaviour.
Many thanks for your report. I agree here that it's inconsistent. It
is due how many arguments such a call can expect. For example on cat
you can use:
=item B< cat>
Display an LDIF dump of an entry. Globbing is supported. Specify
either the full dn, or an rdn. For most commands, rdns are local to the
current search base. ('cwd', as translated to shell speak.) You may
additionally
add a list of attributes to display. Use '+' for server side attributes.
cat uid=mahlon
cat ou=*
cat uid=mahlon,ou=People,dc=example,o=company
cat uid=mahlon + userPassword
i.e. you can have as first argument either a full dn or an rdn,
followed with attributes to list, or/and + for server side attributes.
The manpage should at least document that if there are RDNs with
spaces, then they need to be quoted. I do not see an easy way (right
now) on how the code could be changed to parse the arguments to cat
and rm in better way.
In any case I have also forwarded this to upstram.
Regards,
Salvatore
signature.asc
Description: Digital signature
