On Sun, Aug 22, 1999 at 05:28:31PM -0400, Fairlight wrote:
>
> Based on the symptoms and the process listing, I'd say your problem is the
> `yes` command. Try `yes 1` once from the commandline and see why I say
> that.
>
> Where the `yes` is coming from unless you configured it that way, I have
> no idea...my pgp 2.6.3 worked out of the box with 0.95.[6|7]i...didn't even
> have to specify my keyring locations. That's one of the things I've
> wondered about...I see all this talk about PGP configuration, yet mine just
> "works" ...flawlessly and with no configuration.
>
I tried running yes from the command line. It just spits out
endless lines with "y\n" (y followed by newline). Running yes 1
has the same effect. This is no surprise. According to the yes
man-page yes doesn't accept any parameters except --help and
--version.
I took a closer look at the files generated in /tmp. I got 3
files.
First is /tmp/mutt-nexus-29263-0 which is the message itself
without the headers.
Second is /tmp/mutt-nexus-29263-2 which consists onyl of the
following lines:
+language=en +pubring=/home/fastjack/.pgp/pubring.pgp
+secring=/home/fastjack/.p gp/secring.pgp +verbose=0
+encrypttoself +batchmode -aefts -u 0x757AA05D 0xB82BCB829FBCC2DD
This file grows until I kill the signing process or my /tmp is
full
The last file is /tmp/mutt-nexus-29263-4 which is again my
message with some extra headers.
The second file contains obviously a part of the command line of
the singing process. Is this a configuration error?
Regards
Martin
--
The bugs you have to avoid are the ones that give the user not only
the inclination to get on a plane, but also the time.
-- Kay Bostic
