From: Alan Shutko <ats@acm.org>
Cc: ding@gnus.org
Subject: Re: ssh rulez
Date: 29 Mar 1998 15:36:59 -0600 [thread overview]
Message-ID: <m33eg1uqkk.fsf@hubert.wuh.wustl.edu> (raw)
In-Reply-To: Bud Rogers's message of 29 Mar 1998 14:12:13 -0600
>>>>> "B" == Bud Rogers <budr@tanet.net> writes:
B> Felix Lee <flee@teleport.com> writes:
>> note that unless you're firewalled or something, anyone can connect
>> to that port on your machine and get to iglou.com, pretending that
>> they're coming from you.
B> Is that true? I thought the whole point of ssh/sshd was allow
B> secure remote access through encryption, and host/user verification
B> by encrypted keys.
It is, but when you start redirecting ports like that, you are
subverting such protections for the sake of convenience. It allows
you to point apps at your machine and have them automatically take
advantage of the secure ssh pipe, but it also allows other people to
point their apps at your machine....
--
Alan Shutko <ats@acm.org> - By consent of the corrupted
Put your best foot forward. Or just call in and say you're sick.
next prev parent reply other threads:[~1998-03-29 21:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-28 8:16 Lars Magne Ingebrigtsen
1998-03-28 16:43 ` Harry Putnam
1998-03-28 17:14 ` Bud Rogers
1998-03-28 19:17 ` Richard Hoskins
1998-03-29 8:04 ` Lars Magne Ingebrigtsen
1998-03-29 19:39 ` Felix Lee
1998-03-29 20:12 ` Bud Rogers
1998-03-29 20:38 ` Felix Lee
1998-03-30 20:05 ` Richard Hoskins
1998-03-29 21:36 ` Alan Shutko [this message]
1998-03-30 13:01 ` Robert Bihlmeyer
1998-03-31 16:37 ` Francois Felix Ingrand
1998-04-01 14:06 ` Lars Magne Ingebrigtsen
1998-03-31 21:46 ` Manoj Srivastava
1998-04-15 3:50 ` Eze Ogwuma
1998-04-22 18:27 ` Eric Hendrickson
1998-04-26 11:44 ` Eze Ogwuma
1998-07-12 19:07 ` Eric D. Hendrickson
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=m33eg1uqkk.fsf@hubert.wuh.wustl.edu \
--to=ats@acm.org \
--cc=ding@gnus.org \
/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).