Subject: www

From: Jessica Bray LLE <[email-masked]>
Date: Fri, 19 Aug 1994 14:49:02 -0500 (CDT)

Has anyone interfaced WWW and Pine mail?
jbray
Jessica Bray
GNO Free-Net
[email-masked]

---

From: "J. Kelly Cunningham" <[email-masked]>
Date: Fri, 19 Aug 1994 18:17:06 -0600 (GMT-0600)

What's the status of encryption?  I'm building a script that provides pgp 
encryption to Pine.  Send your public key, with a solemn promise not to 
laugh at the code, to [email-masked] if you want it.

-- kc

Here's the blurb:

(1) Extract and install mkpgp.

At your Unix prompt, run the command:

   uudecode NameOfTheFileYouArePresentlyReading

An executable script, mkpgp, will be extracted.  Move the
the script into a directory on your path.  One such dir is
usually "bin" in your home directory.  Examine the leading
names of your path variable if you are unsure.  In the unlikely 
event that you don't have access to a dir for executables, see * below.

Run the Unix command

  rehash

*or* logout and login.  Either of these will make your system
"aware" of the new command "mkpgp."

(2) Configure Pine for mkpgp.
Edit .pinerc.  

Set the alternate editor to mkpgp:

# Editor to use in place of Pine's internal composer, Pico
editor=mkpgp

	* Or use an absolute path. E.g., editor=/yourHomeDir/mkpgp

Force Pine to put your signature at the bottom:

# Use old style forward/reply with new text and signature below included text
# Old-style-reply is obsolete, use signature-at-bottom in feature-list
old-style-reply=yes
[...]
# The feature-list that is in effect when you are running Pine
[...]
# of the features is no-, that is, off.
feature-list=old-growth,
        signature-at-bottom

(3) Configure mkpgp

At present, there are only two configuration options in mkpgp.
Edit mkpgp and change lines 3 or 5 if appropriate.

#!/bin/csh -f
# Set the real alternate editor on the next line.
set MKPGPEDITOR=pico
# Determine if sender can read encrypted messages.
set ENCRYPTTOSELF=on

(4) Usage.

My first axiom: I detest pecking on keyboards...

==========
Encryption
==========

Compose a message.
	(a) If you don't use pico, invoke the alternate editor then compose.
	(b) If you do use pico, compose then invoke the alternate editor.
When you (a) exit your editor or (b) invoke the alternate editor,
mkpgp will ask:

	Include encrypted attachment(s)? [n]
	
At every prompt, simply hit the <return> key if you want what's in [].  
(This can be important; don't give mkpgp needless input. Remember my first
axiom.)

Enter y and hit <return> if you want to include attachments in the message
text (thereby encrypting them).  A primitive browser will let you navigate
the file system and attach files and dirs.  You select attachments by 
number.  Hit <return> on a blank line to move up one directory.  Selecting a
single directory is ambiguous (since you are navigating the directories
with the same browser), so you are further prompted to 
"Enter or Attach? [e]" it.  Hit <return> to enter, enter a and hit 
<return> to attach it. If a directory is a member of a list, mkpgp assumes 
it is an attachment.  After collecting all the attachments, enter f and
hit <return>.  $PGPPATH/tmp/mkpgpAttach is listed and you are  a given a
chance edit it.  If you elect to do so, mkpgp will cd to 
$PGPPATH/tmp/mkpgpAttach and start a /bin/csh. Do what you will, and use 
the csh command "exit" to return to mkpgp.

mkpgp copies attachments into $PGPPATH/tmp/mkpgpAttach.  When you exit the 
browser, $PGPPATH/tmp/mkpgpAttach is tar'ed, compress, uuencoded and 
appended to the message text as ascii. $PGPPATH/tmp/mkpgpAttach is then 
removed.

Next, pgp will show your pubkey ring and mkpgp will ask:

	Enter recipient key id(s) [none].

List the recipient key id(s) separated by blanks, or hit <return> if you 
don't want to encrypt the message.

pgp will show your seckey ring and mkpgp will ask:

	Sign the message with a secret key? [n]

y <return> selects the key defined by MyName in $PGPPATH/config.txt. You
can select an alternate by giving a keyid (If you enter n, mkpgp will look
for a key with n in it. Bad news...  Remember the first axiom.  Also, 
beware of the ENCRYPTTOSELF option if you select an alternate key.)

If you elect to sign the message, pgp will request a pass phrase. pgp goes
to work on the message. There is a 5 second delay when pgp is finished so
you can see what happened.  After that you should be looking at the message
in the Pine compose window.  Send it.  If ENCRYPTTOSELF=on, you can decrypt
the copy of the message in sent-mail.  If ENCRYPTTOSELF=off and you didn't
include yourself as a recipient, you might as well delete it.

The actual pgp commands/options used by mkpgp are:

pgp -sew +encrypttoself=$ENCRYPTTOSELF +armor=on +keepbinary=off \
+armorlines=0 +tmp=$PGPPATH/tmp $1 $keys $sign

pgp -satw +clearsig=on +encrypttoself=$ENCRYPTTOSELF +keepbinary=off \
+tmp=$PGPPATH/tmp $1 $sign

or

pgp -ew +encrypttoself=$ENCRYPTTOSELF +armor=on +keepbinary=off \
+armorlines=0 +tmp=$PGPPATH/tmp $1 $keys

$1 is /tmp/pico.xxxx, $keys is the list of keys, $sign is the key id used 
to sign the message.  There are several other calls to pgp to wipe and 
delete temporary files.

==========
Decryption
==========

The only way to decrypt in pine is in a reply or forward since that is your
only access to the alternate editor.  Decryption seems to work ok in a 
forward; replies are still flakey because of the variety of quote 
characters people use (I'll fix this when I have time). 

If mkpgp finds "BEGIN PGP MESSAGE" or "BEGIN PGP SIGNED MESSAGE" in the
message, it will run the command:

	pgp +force +interactive=on +keepbinary=off 

and attempt to mimic the forward/reply behavior of Pine.  

If, along the way, 

	begin 600 mkpgpAttach.tar.Z

is found in the message text, mkpgp will unpack the attachments and move 
the mkpgpAttach directory into $PGPPATH (renaming it if needed). The 
mkpgpAttach.tar.Z file is wiped & deleted. You are given a chance to
examine/delete the attachments (exiting the c-shell as before).

If mkpgp finds "BEGIN PGP PUBLIC KEY BLOCK" mkpgp runs

	pgp +force +interactive=on +keepbinary=off

to add keys.  This only works in a forward and attachments aren't unpacked.

  (It's easy to fix, I just haven't done it yet. It was an afterthought).

Let me know how it goes.  I'm open to input, but I want to keep it simple.
Contact me again if you want the updates.

---

From: David L Miller <[email-masked]>
Date: Fri, 19 Aug 1994 21:20:13 -0700 (PDT)

What kind of interface are you looking for?

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: [email-masked] (Lance K. Chun)
Date: Sat, 20 Aug 1994 10:56:51 GMT

> Has anyone interfaced WWW and Pine mail?

Jessica,

Why would you want to do that? It doesn't make any sense.

Lance

---

From: [email-masked] (Christian X Nielsen)
Date: 20 Aug 1994 11:26:03 -0600

That is true, pine would not work or should not work with getting WWW 
docs.

If you have pine, and are on a UNIX machine, you can probally already get 
and look up inforamtion using the WWW.

Just type  lynx http://....... and see if it works.

cxn

-- 
Christian X Nielsen					[email-masked]

	http://xmission.com/~cxn     For information on Travel
	(Updated everyday with new information)

---

From: [email-masked] (Scott Gifford)
Date: 21 Aug 1994 06:45:34 GMT

Lance K. Chun ([email-masked]) wrote:
: In article <[email-masked]>,
: [email-masked] (Jessica Bray   LLE) wrote:

: > Has anyone interfaced WWW and Pine mail?
: > jbray
: > Jessica Bray
: > GNO Free-Net
: > [email-masked]

: Jessica,

: Why would you want to do that? It doesn't make any sense.

: Lance

  It makes sense if you send hypertext (HTML) mail...if I'm writing somebody
about WWW, I find it easier to put an HTML command (like 
<a href="gopher://ais.org"> this </a>) right inside the message, and if you 
view it as HTML, you can just "click" on the link to see what I'm talking
about...I use elm and just pipe my message in; Pine might be able to handle 
it as part of a MIME message.  Or by just exporting it to a file and typing 
"lynx filename".

------Scott.

---

From: [email-masked] (Joshua Bell)
Date: Sun, 21 Aug 1994 08:51:39 GMT

>: Why would you want to do that? It doesn't make any sense.

Yeah, you want to do it the other way; have your WWW browser
behave as a MIME-compliant mail reader as well. I'm not sure that
any do that yet, however.

>it as part of a MIME message.  Or by just exporting it to a file and typing 

I have a utility that you (and others) might like. It is still
"beta" (and I think it'll stay beta forever, and be superceded by
browser functions like the above, but I digress), but it works.

Take a peek at: http://www.ucalgary.ca/~jsbell/tools/fwebp.html

Or, if you're not using a utility like that, and want it as an anchor:

<html>
<a href="http://www.ucalgary.ca/~jsbell/tools/fwebp.html">
This will take you to the documentation</a>
</html>

(It requires Perl and runs under Unix, for the record.)

I use it for doing exactly what the above poster suggests
(although you can't pipe things to Lynx on my system) using
macros in my newsreader and mailer programs. Suggestions and
comments greatly appreciated (as would be an offer to help make
it handle MIME documents, but again I digress).

Joshua
--
__  __  __  __  __  __  __  __Joshua_Sean_Bell__([email-masked])__
\ \/  \/ /\/  \/ /\/  \/ / |"There's far too much to take in here, more to|
 \__/\__/\__/\__/\__/\__/  |__find than can ever be found..." - Tim Rice__|
              http://www.ucalgary.ca/~jsbell/home.html