jef@unisoft.uucp (Jef Poskanzer) (06/25/87)
I unpacked it and compiled it on a VAX running 4.3BSD. No problems.
I ran through the testing procedure, and it works pretty well. (And
is a lot of fun, too!) But:
-- When I try to complete a decryption by running the ciphertext through
zeecode, it gets through a few lines and then exits. No core, it just
exits.
-- The pwords tool does not seem to work very well. To test it, I made
a words file for Usenet headers by taking an actual Usenet article,
deleting everything but the headers, and inserting linebreaks at the
wordbreaks. Then I encrypted that same article, and tried pwords on it.
It should have decrypted the whole block, but it only found one or two
words.
Any clues? Has anyone else run across these problems?
---
Jef
Jef Poskanzer unisoft!jef@ucbvax.Berkeley.Edu ...ucbvax!unisoft!jef
"What we've got here is a failure to communicate."mta@tut.fi (Markku J{rvinen) (06/30/87)
in article <428@unisoft.UUCP>, jef@unisoft.uucp (Jef Poskanzer) says: > > I unpacked it and compiled it on a VAX running 4.3BSD. No problems. > I ran through the testing procedure, and it works pretty well. (And > is a lot of fun, too!) But: > > -- When I try to complete a decryption by running the ciphertext through > zeecode, it gets through a few lines and then exits. No core, it just > exits. > There is one little bug in zeecode.c which makes it act like you described. In the function doblock(p) there is described a variable 'char c;' which should be 'int c;', that's because the value which 'getchar' returns is placed in it (getchar returns int, EOF ((int)-1) when _End_Of_File_ is reached), thus when there is a char which decimal value is 255 (read it to char and voila, it's -1==EOF) zeecode stops reading. I've tried CBW using files supplied and had no other problems. It really does the work for me. Markku Jarvinen, last `a' with two dots over it mta@tut.fi (internet) tut!mta (UUCP)