From: Mark Eichin <eichin@cygnus.com>
Cc: ding@ifi.uio.no
Subject: Re: Burrowing
Date: 04 Jul 1996 16:15:24 -0400 [thread overview]
Message-ID: <xe1raqr6ahv.fsf@maneki-neko.cygnus.com> (raw)
In-Reply-To: Thor Kristoffersen's message of 03 Jul 1996 09:13:58 +0000
> works fine if you can modify the .rhosts file. If you use telnet it
> will always ask for a password, AFAIK.
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...)
I thought "telnet -a" would check .rhosts on some systems as well, not
sure though. It may just save you from typing a password.
next prev parent reply other threads:[~1996-07-04 20:15 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 ` Mark Eichin [this message]
1996-07-05 1:21 ` Burrowing Lars Magne Ingebrigtsen
1996-07-05 18:34 ` Burrowing Edward J. Sabol
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=xe1raqr6ahv.fsf@maneki-neko.cygnus.com \
--to=eichin@cygnus.com \
--cc=ding@ifi.uio.no \
/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).