From: "Edward J. Sabol" <sabol@thuban.gsfc.nasa.gov>
Subject: Re: Burrowing
Date: Fri, 5 Jul 1996 14:34:05 -0400 [thread overview]
Message-ID: <199607051834.OAA09318@thuban.gsfc.nasa.gov> (raw)
In-Reply-To: <w8sn31f8phd.fsf@ylfing.ifi.uio.no> (message from Lars Magne Ingebrigtsen on 05 Jul 1996 03:21:02 +0200)
Excerpts from mail: (05-Jul-96) Re: Burrowing by Lars Magne Ingebrigtsen
> Mark Eichin <eichin@cygnus.com> writes:
>> I'm likely to try these using Kerberos telnet/rlogin, neither of which ask
>> for passwords... so It Would Be Nice If the password prompt checking code
>> was optional (or maybe just only triggered if it *saw* a password
>> prompt...)
>
> For `nntp-open-telnet' the password thing is required. If you're using
> Kerberos, you should be able to use `nntp-open-rlogin', which uses rsh.
> (And should be called `nntp-open-rsh', I guess.)
I don't know about other environments, but in the Kerberos/AFS environments
I'm familiar with, rsh doesn't work, rlogin is frowned upon (especially since
the release of the encrypted, auto-authenticated version of telnet), and the
use of a ~/.rhosts files is completely disabled. And even if that weren't the
case, encrypted, auto-authenticated telnet streams are a *lot* sexier than
rlogin/rsh on any day of the week. If it wouldn't be too difficult, please
add a no-password-necessary option to `nntp-open-telnet' (or make a separate
function `nntp-open-telnet-no-password'?).
Thanks,
Ed
next prev parent reply other threads:[~1996-07-05 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-03 6:04 Burrowing Lars Magne Ingebrigtsen
1996-07-03 9:13 ` Burrowing Thor Kristoffersen
1996-07-04 2:44 ` Burrowing Lars Magne Ingebrigtsen
1996-07-04 20:15 ` Burrowing Mark Eichin
1996-07-05 1:21 ` Burrowing Lars Magne Ingebrigtsen
1996-07-05 18:34 ` Edward J. Sabol [this message]
1996-07-07 10:46 ` Burrowing Lars Magne Ingebrigtsen
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=199607051834.OAA09318@thuban.gsfc.nasa.gov \
--to=sabol@thuban.gsfc.nasa.gov \
/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).