Mailing List Archive

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Werner Koch, at 10:02 +0200 on Wed, 2 Aug 2000, wrote:

> On Tue, 1 Aug 2000, L. Sassaman wrote:
>
> Afaik, pgpenvelope supports rfc2015 and it can be used to teach pine
> pgp.

Unfortunately, AFAIK, pgpenvelope does not do this :P

But I hope to get it in sometime. Honest :)

- --
Frank Tobin http://www.uiuc.edu/~ftobin/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (FreeBSD)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjmIMcYACgkQVv/RCiYMT6NWagCfRmdPicTI5LHN1hCHoEGmDJw2
dyMAn2qJkrVHQDft4koWM1vPw0yn8Pn6
=e32k
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 2 Aug 2000, Frank Tobin wrote:
> Werner Koch, at 10:02 +0200 on Wed, 2 Aug 2000, wrote:
> >
> > On Tue, 1 Aug 2000, L. Sassaman wrote:
> >
> > Afaik, pgpenvelope supports rfc2015 and it can be used to teach pine pgp.
>
> Unfortunately, AFAIK, pgpenvelope does not do this :P
> But I hope to get it in sometime. Honest :)

Pine would have to let you get at the MIME parts of incoming messages.
Which it unfortunately doesn't. How can you get around this Pine
limitation?

I know pgpenvelope's procmail filter wouldn't be limited this way,
but you can't decrypt with procmail.

- --
"The Funk, the whole Funk, and nothing but the Funk."
Billy Donahue <mailto:billy@dadadada.net>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE5iEJi+2VvpwIZdF0RAh2XAJ9oOjOS4ETqJ9g71adY0OwTI0MLQQCaAzRF
6GirQCaEk52uqAmWks996Fg=
=Q2bj
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Billy Donahue, at 11:46 -0400 on Wed, 2 Aug 2000, wrote:

> Pine would have to let you get at the MIME parts of incoming messages.
> Which it unfortunately doesn't. How can you get around this Pine
> limitation?

Glad you asked. Look into the piping (| command) of Pine. It can let me
process a message directly. Things are looking up.

> I know pgpenvelope's procmail filter wouldn't be limited this way,
> but you can't decrypt with procmail.

Eh, but some people might trust their system enough, have a key dedicated
to encrypted email, and keep the key stored on the filesystem. I know I
wouldn't, but I'm not everyone (yet) :)

- --
Frank Tobin http://www.uiuc.edu/~ftobin/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (FreeBSD)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjmISFMACgkQVv/RCiYMT6PIkgCgl5Rx/YU7a5HXbBxz8NmWiLWr
1kkAn3+YRrrWjBT8HJG2TjJ7WAper2K1
=0j4p
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

L. Sassaman, at 14:55 -0700 on Thu, 3 Aug 2000, wrote:

> Sadly, that's not the case. I've been using pgpenvelope over a year now,
> and love it... but there isn't any way to handle PGP/MIME with pine. It's
> pine's fault, not pgpenvelope's... and due to the licensing on pine's
> source, I am probably not going to bother fixing it.

Erm, well, that's not entirely correct; eventually pgpenvelope is going to
handle PGP/MIME by using the Pipe command to process the raw message. We
just have to get out of the rut of simply using the display-filter option
:)

- --
Frank Tobin http://www.uiuc.edu/~ftobin/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (FreeBSD)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjmJ82EACgkQVv/RCiYMT6N1PQCgi31DnDEdZu2LjiP94ka1n1u4
4pUAnjAGI13VHhTcO8HR0y/kyHBlZpIX
=6+V4
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 3 Aug 2000, Frank Tobin wrote:

> Erm, well, that's not entirely correct; eventually pgpenvelope is going to
> handle PGP/MIME by using the Pipe command to process the raw message. We
> just have to get out of the rut of simply using the display-filter option
> :)

I just tried piping to pgpenvelope_decrypt and was dropped into
the viewer as advertised. THe problem is that there is no way to reply to
a decrypted message while in the viewer.

- --
John Perry perry@jpunix.com PGP-encrypted e-mail welcome!
PGP/GPG key 164BDBAE
ICQ# 64823745
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE5ig3y7YSEAxZL264RAgUuAJ9+gXV2hXAVJYndHmmJvn9gb0gW1ACZAWdF
xfzAd6/pZ/XJ1EI7Swk//yc=
=37ny
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 3 Aug 2000, L. Sassaman wrote:

> Oh, cool! Show us how!

I did it this way. While in the reader type "|pgpenvelope_decrypt"
and it will pipe the message to pgpenvelope.

- --
John Perry perry@jpunix.com PGP-encrypted e-mail welcome!
PGP/GPG key 164BDBAE
ICQ# 64823745
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (GNU/Linux)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iD8DBQE5ig567YSEAxZL264RAkK0AJ9nQqwu3VtlxC0PbdmMnL6B/qAR7wCgpHmw
uiOkjuVWytv8aXGjUSk79tA=
=hbUz
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John A. Perry, at 19:27 -0500 on Thu, 3 Aug 2000, wrote:

> I just tried piping to pgpenvelope_decrypt and was dropped into
> the viewer as advertised. THe problem is that there is no way to reply to
> a decrypted message while in the viewer.

Ah, yes, this will pose a problem for encrypted messages. I don't know a
solution for this yet.

- --
Frank Tobin http://www.uiuc.edu/~ftobin/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.2 (FreeBSD)
Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/

iEYEARECAAYFAjmKMKcACgkQVv/RCiYMT6PF2ACfS5wL+elnZF6JDxtFEcF1Sazu
k8EAoJ0PBIUP3ekClwbt3FUcgoppfwwl
=vBwn
-----END PGP SIGNATURE-----

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org

On Thu, 3 Aug 2000, L. Sassaman wrote:

> Sadly, that's not the case. I've been using pgpenvelope over a year now,
> and love it... but there isn't any way to handle PGP/MIME with pine. It's
> pine's fault, not pgpenvelope's... and due to the licensing on pine's
> source, I am probably not going to bother fixing it.

Anyway, Mutt is better ;-)

It should also be possible to compile Mutt under Cygwin32 to have a
nice text MUA for Windows.

Werner



--
Werner Koch GnuPG key: 621CC013
OpenIT GmbH http://www.OpenIT.de

--
Archive is at http://lists.gnupg.org - Unsubscribe by sending mail
with a subject of "unsubscribe" to gnupg-users-request@gnupg.org