Subject: Pine and S/MIME

From: Nicholas Horwood <[email-masked]>
Date: Mon, 24 Jul 2000 16:44:59 +0100 (BST)

Hi there

I'm new to this list...

Can anyone point me to some how-to or info on S/MIME and Pine, assuming
someone has got it working. (boy have i been looking hard everywhere,
found nothing) PGP works fine, no probs, nice, but PGP and
S/MiME aren't compatible.

many thanks

nicholas

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Nicholas Horwood <[email-masked]>
Date: Tue, 25 Jul 2000 15:03:30 +0100 (BST)

Hi there

I've been looking everywhere and still have found nothing.
If anyone on this list knows anything about Pine and s/mime, i would
really appreciate a link or something to get me started.
Maybe Pine and s/mime can't be intergrated and I'm waisting my time
looking, but i don't even know that :(

many thanks

nicholas

---

From: Frank Tobin <[email-masked]>
Date: Tue, 25 Jul 2000 14:55:56 -0500 (CDT)

Nicholas Horwood, at 15:03 +0100 on Tue, 25 Jul 2000, wrote:

> I've been looking everywhere and still have found nothing. If anyone
> on this list knows anything about Pine and s/mime, i would really
> appreciate a link or something to get me started. Maybe Pine and
> s/mime can't be intergrated and I'm waisting my time looking, but i
> don't even know that :(

While I am not an official spokeperson for Pine by any means, I have not
seen any efforts to develope S/MIME functionality into Pine directly or
via a filter (even if that is possible with S/MIME).

All efforts I have seen are to develop OpenPGP functionality into it (and
with good reason, IMO :) ).

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

---

From: Paul Jakma <[email-masked]>
Date: Tue, 25 Jul 2000 23:33:09 +0100 (IST)

> with good reason, IMO :) ).

what are all these different standards btw? S/MIME.. PGP/MIME, (or does
PGP/MIME fall under S/MIME?). How does OpenPGP relate to this?

it's quite a pain for me, cause i have to communicate with mutt users in
work which uses some kind of MIME. The encrypted body of the message is
given:

Content-type: application/octet-stream

which is a pain, cause you can only tell that this is PGP encrypted
because it is preceded by a seperate MIME section of
application/pgp-encrypted.

I wish there was a way for Pine to be handle these types of things. either
via specific S/MIME/standard of the day support or better MIME handling
configurability. (eg ability to use pass MIME to display filters, or
similar). Cause at the moment it is impossible to use PGP with mutt users.

regards,

Paul Jakma.

---

From: Frank Tobin <[email-masked]>
Date: Tue, 25 Jul 2000 17:47:44 -0500 (CDT)

> PGP/MIME fall under S/MIME?). How does OpenPGP relate to this?

PGP/MIME is standard to use the RFC 1991 (original PGP) implementation
together with MIME to allow PGP to work together and take advantage of
what MIME offers.

S/MIME is a MIME implementation that is not related to PGP; it is a
competing standard with OpenPGP and PGP/MIME.  It's security is based on
the same certificate system SSL uses, if I'm not mistaken.

OpenPGP is the current PGP standard, RFC 2440.  It's name is not
PGP-by-NAI specific because there are other (possibly better)
implementations of the standard, most prominently GnuPG,
available at http://www.gnupg.org/

> application/pgp-encrypted.

Yeah, can be annoying; but MIME does provide language/character
extensibility, and PGP/MIME covers that.

> I wish there was a way for Pine to be handle these types of things.
> either via specific S/MIME/standard of the day support or better MIME
> handling configurability. (eg ability to use pass MIME to display
> filters, or similar). Cause at the moment it is impossible to use PGP
> with mutt users.

Tell your mutt users to not use PGP/MIME, but rather clear-signed text,
for the time.  Non-MIME messages can be cleaner to handle at times (they
require less processing), as they are 'blocks' that can be easily grasped.

Pine doesn't support multi-part MIME messages yet, IINM, so PGP/MIME
support won't likely be very well integrated.  But I have a few tricks up
my sleeve try to solve that :)

- --

---

From: Paul Jakma <[email-masked]>
Date: Wed, 26 Jul 2000 13:17:19 +0100 (IST)

On Tue, 25 Jul 2000, Frank Tobin wrote:

> Pine doesn't support multi-part MIME messages yet, IINM,

it seems to work. at least i can see every MIME part when a mutt user
sends me an encrypted message. (or do you mean something else?)

> so PGP/MIME

excellent! can't wait to see it! (forgive my present use of pgp4pine :) )

regards and thanks for the info,

Paul Jakma.

---

From: "Robert Dwyer - Inhealth Record Systems" <[email-masked]>
Date: Thu, 27 Jul 2000 14:17:38 -0400

I'm a new PINE administrator, so I have a basic question to begin with.  I'm
currently using PINE 4.21 under Data General DG/UX 4.11.  We also have begun
using a program called Faceterm, which allows for multiple windowing on our
dummy terminals.

The problem that I'm having is that PINE is going "idle" under Faceterm
within 15-30 seconds of a log-in.  This is very annoying, since you have to
re-activate the window AND log in again to use PINE.  Since PINE is actually
checking for mailboxes on another computer (our mail server), it seems to be
receiving a break signal when no mail is there.  I was wondering whether
keeping the Inboxes on the main server (where PINE resides) would solve this
problem.  I'm not sure how to go about configuring PINE to import the
messages on to the main server.  Would I have to use a "fetch" program or
are there features in PINE that would allow me to do this?  Any suggestions
would be highly appreciated.

Robert Dwyer
Inhealth Record Systems
Atlanta, GA