From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Re: authentication in gnus technically not perfect
Date: 24 Nov 1997 22:40:57 -0800 [thread overview]
Message-ID: <x74t51qxvq.fsf@des.castles.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "24 Nov 1997 22:37:36 -0500"
>>>>> On 24 Nov 1997 22:37:36 -0500, Stainless Steel Rat <ratinox@peorth.gweep.net> said:
Rat> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> "WH" == Wes Hardaker <wjhardaker@ucdavis.edu> writes:
Rat> For the other, by not sending a password in the clear when it is
Rat> not necessary, it is an instance of not sending a cleartext
Rat> password across the network.
Don't get me wrong, I agree :-) I just don't classify it as a 'bug'
because it doesn't violate protocols nor does it cause problems (aside
from security).
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
prev parent reply other threads:[~1997-11-25 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-20 18:32 Wes Hardaker
1997-11-23 6:16 ` Lars Magne Ingebrigtsen
1997-11-24 21:33 ` Wes Hardaker
[not found] ` <x7zpmtc0l5.fsf@peorth.gweep.net>
1997-11-25 2:04 ` Wes Hardaker
[not found] ` <x7d8jpod8f.fsf@peorth.gweep.net>
1997-11-25 6:40 ` Wes Hardaker [this message]
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=x74t51qxvq.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
/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).