On 2 Jun 2000, Niels M�ller wrote:

> "Eric J. Schwertfeger" <[EMAIL PROTECTED]> writes:
> 
> > It seems that the -o option that lsh-authorize passes to sexp_conv has
> > been removed, which causes sexp_conv to fail, which causes lsh-authorize
> > to fail.  For the time being, I'm just removing -o canonical from the
> > sexp_conv arguments in lsh-authorize.
> 
> Ooops. The -o flag has been renamed to -f (as in "format"). This was
> done for consistency reasons, -o is used for specifying an output file
> name for those programs for which that makes sense. I'll fix the
> lsh-authorize script.

Not a bad problem, I'm just embarrassed, because 0.9.10 seemed stable and
useful enough that I finally submitted my lsh port to the FreeBSD ports
collection, but didn't catch this until afterwards.

> > Also, I've noticed that somewhere between 0.9.5 and 0.9.10, some old bugs
> > are back.

...

> Sorry, I can't do much without the actual compilation errors.

Not a problem, it was fixed again, I was just mentioning it because it
seemed odd that several familiar problems cropped up at the same time.

> > Unhandled exception of type 0x4001: Public key userauth failed.
> > Abort trap (core dumped)
> > 
> 
> This (or at least the symptoms) indeed matches an old bug.  Can you run
> the client with --trace and see what it says? That should tell us
> where the exception is raised, and how it is propagated. I've tried to
> reproduce it (the --no-publickey flag to the server is handy for
> that), but I don't see the bug here.

http://gz.geekazoid.com/lsh/client-typescript.txt (at just short of 24K,
I'd rather not post it to the list).

If it helps http://gz.geekazoid.com/lsh/server-typescript.txt is the
corresponding output of lshd, also with --trace set, and no other
connections to lshd during the file capture.

As a side note, while 

        lsh dest "cat >destfile" <sourcefile

is more convenient than using ftp to shift a single file, I'm working on a
perl implementation of what I'm calling lcp (a wrapper around somthing
like the above, though a little more complicated), if anyone is
interested, though it's still in design stage.


Reply via email to