From: Nathan Williams <nwilliams@primeon.com>
Cc: ding@gnus.org, hoepman@cs.utwente.nl
Subject: Re: gnus-PGP
Date: 24 Sep 1999 14:24:11 -0400 [thread overview]
Message-ID: <wku2okxj5g.fsf@primeon.com> (raw)
In-Reply-To: psadhukhan@hss.hns.com's message of "24 Sep 1999 17:54:51 +0000"
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
psadhukhan@hss.hns.com writes:
> Hi,
> I am using PGPi 6.5.1
> I get from the NEWS file in the /usr/lib/xemacs-20.4/lisp/mailcrypt
> directory that the version is 3.4.
> is there any other way of knowing the mailcrypt version?
I've recently (in the last few days) been trying to make Mailcrypt
3.5.4, and PGP 6.5.1 (command line) talk to each other (with FSF Emacs
20.3.1 and pGnus 0.92, all on a Windows 98 system). Here's what I've
learned:
- 6.5.1 is close enough to 2.6.2 that mods should be based on
mc-pgp.el rather than mc-pgp5.el.
- Signing and encrypting can be made to work either by using the
+COMPATIBLE flag throughout mc-pgp.el or changing key-regexp in
mc-pgp-lookup-key to:
"^\\(\\(DSS\\|RSA\\)\\s +\\S +\\s +0x\\(\\S *\\)\\s +\\S +\\s +\\(.*\\)\\)$"
- The bug that prevents -f and +BATCHMODE from working together
triggers a bug in mc-pgp-decrypt-region such that if one
naievely removes +BATCHMODE, you get wedged asking for a
password. This can be worked around with the following patch
(which is more like what mc-pgp5.el and mc-gpg.el do; I presume
that it isn't fixed here because it doesn't cause problems with
PGP 2.6.2):
[-- Attachment #2: Fix to mailcrypt that avoids -f/+BATCHMODE lossage in 6.5.1 --]
[-- Type: text/plain, Size: 1106 bytes --]
*** src/mailcrypt-3.5.4/mc-pgp.el Tue Jul 20 10:20:56 1999
--- share/elisp/mc-pgp.el Thu Sep 23 15:28:38 1999
***************
*** 255,267 ****
passwd
(if key
(mc-activate-passwd (cdr key)
! (and id
! (format "PGP passphrase for %s (%s): "
! (car key) (cdr key))))
(mc-activate-passwd id "PGP passphrase for conventional decryption: ")))
(if passwd
(setenv "PGPPASSFD" "0"))
! (setq args '("+verbose=1" "+batchmode" "+language=en" "-f"))
(if mc-pgp-alternate-keyring
(setq args (append args (list (format "+pubring=%s"
mc-pgp-alternate-keyring)))))
--- 253,264 ----
passwd
(if key
(mc-activate-passwd (cdr key)
! (format "PGP passphrase for %s (%s): "
! (car key) (cdr key)))
(mc-activate-passwd id "PGP passphrase for conventional decryption: ")))
(if passwd
(setenv "PGPPASSFD" "0"))
! (setq args '("+verbose=1" "+language=en" "-f"))
(if mc-pgp-alternate-keyring
(setq args (append args (list (format "+pubring=%s"
mc-pgp-alternate-keyring)))))
[-- Attachment #3: Type: text/plain, Size: 674 bytes --]
- mc-pgp-decrypt-parser needs a lot of work. As-is, you get no data
because the "Signature good" output (on stderr) from pgp ends
up after the actual message, the opposite of what
mc-pgp-decrypt-parser expects (This might also be a result of
Windows or Emacs on Windows mixing stdout and stderr
differently; <insert flame about start-process not having a way
to handle stderr separately from stdout and depending on
unreliable mixing semantics>).
This might be a place where ripping off from mc-pgp5.el
would be productive. I'm still working on it.
I hope this helps some.
- Nathan
next prev parent reply other threads:[~1999-09-24 18:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <652567F6.00416332.00@sandesh.hss.hns.com>
1999-09-24 17:54 ` gnus-PGP psadhukhan
1999-09-24 15:12 ` gnus-PGP Rupa Schomaker (list)
1999-09-24 18:24 ` Nathan Williams [this message]
1999-09-27 12:03 Gnus-PGP psadhukhan
-- strict thread matches above, loose matches on Subject: below --
1999-09-24 14:57 gnus-PGP psadhukhan
1999-09-24 11:54 ` gnus-PGP Jaap-Henk Hoepman
1999-09-13 18:59 gnus-PGP psadhukhan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=wku2okxj5g.fsf@primeon.com \
--to=nwilliams@primeon.com \
--cc=ding@gnus.org \
--cc=hoepman@cs.utwente.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).