From: Brandon Black photon@nol.net
Subject: pop3
Date: Thu, 30 Jan 1997 00:14:23 -0600 [thread overview]
Message-ID: <19970130061423.dTdPohSMU3XThNtyMipOLxSooJgzOocJL-NYFnHL0jw@z> (raw)
On Wed, 29 Jan 1997, Russ Cox wrote:
> >of secure authentication. if the client side had a useful operating
> >system, you might interpose a `secure' connection between client and
> >server, to prevent the password being seen.
>
> for that matter, if the client side had a useful operating
> system, you could interpose a secure, authenticated connection
> and not require a password.
>
> p.s. is apop somehow encrypted or disguised? i've only seen it
> as an option in eudora.
>
Check out the rfc's I referred to (1731 and 1734 I _think_...)... They
said something about "apop"... it had something to do with the server
initially giving an identification message like:
+OK Pop3 Server ready <123.45678@xxx.com>
where xxx.com was the host, and 123 and 45678 were the pid of the server
and some other number..
Then the user did a (md4 maybe?) hash of a string consisting of that
server id string plus his/her password, and returned the hash to the
server to authenticate...
Or something like that...
brandon
................................. ..............
: Brandon Lee Black : [Office] :.............: [Personal] :....
:....................: brandon.black@wcom.com : photon@nol.net :.......
: "Sanity is the : +1.281.362.6466 .......: photon@gnu.ai.mit.edu :
: trademark of a :.................:..../\: vis_blb@unx1.shsu.edu :
: weak mind. . ." : LDDS WorldCom, Inc. :\/: +1.281.397.3490 ......:
:....................:.....................:..:.................:
next reply other threads:[~1997-01-30 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-30 6:14 Brandon [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-01-30 9:55 pop3 forsyth
1997-01-30 9:13 pop3 Boyd
1997-01-30 6:28 pop3 Lucio
1997-01-30 2:15 pop3 Russ
1997-01-30 1:15 pop3 forsyth
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=19970130061423.dTdPohSMU3XThNtyMipOLxSooJgzOocJL-NYFnHL0jw@z \
--to=9fans@9fans.net \
/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).