1993-07-11 - PINE

Header Data

From: me <root@Cloud.Cuckoo.Land>
To: cypherpunks@toad.com
Message Hash: bf992cd7df27bb04f9e91ed573580b505984414da5725082bb48582c7ae7282e
Message ID: <Pine.3.05.9307111733.A26652-a100000@eris.cs.umb.edu>
Reply To: N/A
UTC Datetime: 1993-07-11 21:26:18 UTC
Raw Date: Sun, 11 Jul 93 14:26:18 PDT

Raw message

From: me <root@Cloud.Cuckoo.Land>
Date: Sun, 11 Jul 93 14:26:18 PDT
To: cypherpunks@toad.com
Subject: PINE
Message-ID: <Pine.3.05.9307111733.A26652-a100000@eris.cs.umb.edu>
MIME-Version: 1.0
Content-Type: text/plain




  One of the many neat features of PINE is that it allows one to talk
to the SMTP server _directly_, bypassing sendmail (and its security checks).
What this means is that instead of doing a  "telnet xxxx smtp", you can
build and configure a PINE client to do it for you, and retain all the
nice features. PINE source code is freely available, and does not require
root privs to run (any more than it requires root privs to "telnet xxx smtp").
The pine executable does take up a Meg and a half though, which could be a
problem for folks without a lot of space to play with.
 Coming down the pike though, I see SMTP, maybe even NNTP protocols being
secured (check out the magazine someone mentioned earlier: INFO-SECURITY.
You just have to fill out a bingo card to get it, Write:INFO-SECURITY NEWS
498 Concord St, Framingham MA 01701-2357). If that happens, the days of EZ
phreaking are over.....



			






Thread