[LDAPsh-devel] Hi

[<po...@li...>]

(Are these mailinglists in use at all?)

Thank you for a slick product.  I had just started to write my own
ldapsh when I found yours, which was far more complete than my 1-day
hack.  The code was generally a pleasure to work with as well.

I will (eventually) be using this in a mixed environment of Solaris
and Linux systems, using openLDAP to manage users, groups and login
rights.  I suspect I'll be writing quite a few local commands to do
the higher level stuff.

An idea for the longer term is to support #!/usr/bin/ldapsh and write
scripts in ldapsh syntax.

I'll be uploading a couple of patches to sourceforge in a moment
(nothing big, just details).

One thing I'm seeing which I'm not quite sure how to fix yet is the
ReadLine::GNU password handling.  My xterm prints funny characters
around the "Password:" prompt, and if I type the wrong password, it's
echoed back at me.  Several times, in fact.  Anyone else seeing this?
I'll be looking at it in more detail later on.

Two questions: Why is the CVS structure as it is?  It's impossible to
check out the project as a module using anonymous pserver, I had to
check out each file explicitly.  Other sf projects I have worked on
have their files under /cvsroot/<projname>/<projname>, so that 'cvs
-d:pserver:anonymous@...sf.net:/cvsroot/<projname> co <projname>'
work.

Next: What does it take to get ssh access to ldapsh cvs?  I'm
currently behind a firewall that does not allow pserver through.  To
do anything useful I have to check out ldapsh to another machine, and
scp files through the firewall, which is kind of a hassle.

-- 
Peder O. Klingenberg   |   Systemkonsulent/Systems Consultant
Linpro AS              |   URL: http://www.linpro.no/
Wdm. Thranes Gt 98b    |   Tlf: +47 22 87 11 80
NO-0175 OSLO           |   Fax: +47 22 87 11 81