The only problem with this is people who are using these new DH/DSS
keys.
>Have you manually copied:
Yes; I don't have a pgp config file as most of the defaults seem to work
for me.
>PGP5.0i can be called in various ways. I renamed pgp.exe to pgpo.exe.
>This is supposed to allow the pgp2.6.3 calling syntax, but it appears
>to be buggy.
This is definitely an understatement <g>. In particular, this having to
use the -r to specify a recipient always messes me up.
>#encrypt=command.com /c %d\pgpe.bat %o -aest %f
>
>needs to be changed to:
>
>encrypt=command.com /c %d\pgpe.bat %o -aest %f -r
Cool, I had the right idea, but the wrong order. Also, I think it will
be necessary to create two batch files, a pgpe.bat for encrypting and a
pgps.bat for signing, as the -r option is required for encrypting, but is
not required for signing. Am I making this overly complicated?
>
>Personally, I'd use -aet rather than -aest because the "s" (sign) will
>reveal your identity. If you're posting anonymously, that's a BAD
>thing, and it's easy to forget that Yarn's "Encrypt" menu choice
>is really "Encrypt & Sign."
I've often wondered if there was a way to solve that little problem, I
was thinking that it might be possible to write a small menu in the
pgpe.bat file which would prompt the user wether to sign, or not. in
this way, you could select he encrypt option and opt to sign, or not to
sign. Maybe that'll be the next project.
>
>I got tired of messing with it and didn't test the decrypt and view.
>You'll probably need to fiddle with the calls a bit.
Probably, but that shouldn't be that difficult as the syntax hasn't
realy changed from earlier versions.
>
>You can see the %o, %f, et cetera by changing pgpe.bat to:
[SNIP]
That's a great and very useful idea, I'll give it a try.
Again, I really appreciate all your helf/info/suggestions, they are all
very helpful.
Steve
>steve@sawczyn.com (Steven M. Sawczyn) wrote:
>>Hi, Since many people are upgrading to the latest and greatest versions
>>of pgp, I thought I'd do the same. Unfortunately, the only version of
>>pgp which is accessible via the command line and which supports these
>>new non-rsa keys is the international version 5.0. Unfortunately, this
>>version requires the command line to be structured differently than
>>earlier versions, so the yarn pgp hooks no longer werk. Fuss though I
>>did with the pgpe.bat file, I could not get it to work at all. Has
>>anyone on this list done this? If so, please tell me how. If not,
>>could someone tell me specifically what the %o and %f arguments refer to
>>in the pgp section of the yarn config file?
>>
>>As always, any help would be greatly appreciated.
>>
>>Steve
>>
>
>