Hi Stefan and Chris,

that is an embarrassing bug, fixed by the following:

--- src/main.c.~1.18.~  2004-03-28 23:59:38.000000000 -0500
+++ src/main.c  2005-03-09 14:38:48.611616672 -0500
@@ -160,7 +160,7 @@
   {"mismatch",     0, 0, 'm'},
   {"envvar",       1, 0, 'E'},
   {"key",          1, 0, 'K'},
-  {"keyfile",      0, 0, 'k'},
+  {"keyfile",      1, 0, 'k'},
   {"prompt",       1, 0, 'P'},
   {"suffix",       1, 0, 'S'},
   {"strictsuffix", 0, 0, 's'},

What surprises me is that nobody seems to have noticed this before!  I
can trace this bug all the way back to the first release of ccrypt in
October 2001.

I have fixed it now, but I won't be in a rush to make a bugfix
release, considering that it took over 3 years for this to bother
anyone. :)

-- Peter

Chris Vanden Berghe wrote:
> 
> Hi Stefan,
> 
> Thanks for your bug report.  I quickly verified the issue described and 
> you seem to be quite right.
> 
> Peter is very responsive when it comes to ccrypt, so I expect a fix soon.
> 
> Thanks,
> Chris.
> 
> ---
> Stefan Alfredsson wrote:
> > Package: ccrypt
> > Version: 1.7-5
> > Severity: normal
> > 
> > According to the man-page,
> > 
> >       -k file, --keyfile file
> >                  Read the keyword as the first line from the named file.
> > 
> >       -K key, --key key
> >                  Specify the keyword on the command line. 
> > 
> > 
> > However, --keyfile seem to be interpreted as --key, as shown below
> > 
> > $ echo secret > mykey
> > $ echo "Hello World" | ccencrypt --keyfile mykey > msg.cpt
> > Enter encryption key:
> > Enter encryption key: (repeat) 
> > $ echo "Hello World" | ccencrypt -k mykey > msg.cpt
> > ccencrypt: could not read key from mykey: No such file or directory
> > $ ls -l mykey*
> > -rw-r--r--    1 alfs     alfs           39 2005-03-09 09:49 mykey.cpt
> > 
> > [this means it encrypted the keyfile!]
> > 
> > $ echo secret > mykey
> > $ echo "Hello World" | ccencrypt -k mykey > msg.cpt
> > $ 
> > 
> > [ok, -k worked as it should]
> > 
> > This is probably a bug in the options handling, not directly related to
> > the debian packaging, so I also CC the upstream on this one.
> > 
> > Regards,
> >  Stefan
> > 
> > 
> > -- System Information:
> > Debian Release: testing/unstable
> > Architecture: i386
> > Kernel: Linux sa-pc 2.6.7-1-686 #1 Thu Jul 8 05:36:53 EDT 2004 i686
> > Locale: LANG=en_US, LC_CTYPE=en_US (ignored: LC_ALL set to sv_SE)
> > 
> > Versions of packages ccrypt depends on:
> > ii  libc6                       2.3.2.ds1-17 GNU C Library: Shared 
> > libraries an
> > 
> > -- no debconf information
> > 
> > 
> > 
> 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to