Jeff Bailey <[EMAIL PROTECTED]> writes:
> A force flag would probably be the best thing to do, with an error that
> says:
Noted.
> [jbailey@cr499794-a jbailey]$ ls -al .lsh
> total 10
> drwxr-xr-x 2 jbailey jbailey 1024 Jul 27 08:28 .
> drwx------ 78 jbailey jbailey 9216 Jul 27 08:16 ..
> [jbailey@cr499794-a jbailey]$ lsh_keygen | lsh_writekey
> lsh_writekey: File exists
> Broken pipe
This is strange. One thing you could do (besides finding and fixing
the bug ;-) is to write a test case that detects it. Use
src/testsuite/keygen-test as a start. To test the no-argument case of
lsh_writekey, one would probably have to do something like
rm -rf testhome
mkdir testhome
HOME="`pwd`/testhome" ../lsh_writekey < $srcdir/key-1.private
> I don't know if it's the version number, or if you just installed it
> better than me. =) I'll try and look a touch later, but it's been very
> busy at work.
Probably a bug introduced after 0.9.4.
I'll look closer at this later next week.
/Niels
