telnet vs ssh on Core equipment , looking for reasons why ?

Tue Jul 31 19:01:49 UTC 2001

Here's an alternative that might work. Authenticate via Radius which in turn
proxies the authentication request to a SecurId server. With one time
passwords, who cares if they get sniffed? You also get the benefit of having
your Radius server being able to do accounting/access control on the
sessions as well.

-----Original Message-----
From: Dave Israel [mailto:davei at biohazard.demon.digex.net]
Sent: Tuesday, July 31, 2001 2:43 PM
To: alex at yuriev.com
Cc: nanog at merit.edu
Subject: RE: telnet vs ssh on Core equipment , looking for reasons why ?

[Yeah, I know, we've wandered off topic.  But security is fun to 
talk about.]

On 7/31/2001 at 12:41:23 -0400, alex at yuriev.com said:
> 
> > 
> > 2) Your vendor's ssh authentication creates a secure connection, and
> >    transfers the password securely, only to then send the password,
> >    unencrypted, to an authentication server for verification, making
> >    ssh moot.
> 
> Establish reasonable path for trust propagation and you have solved the
> problem.

Except, of course, if I had a reasonable path for trust propigation,
I would have a trusted path for telnet logins. ;-)

Any compromise on a clear-text telnet password is going to be viable
against any other clear-text password transmission.  Even restricting
logins to certain host ranges only pushes security to those networks.
If you're going to sniff my backbone passwords, the networks that are
wrapped in are presumably compromised already.

Network security is a beast.  There's no sure method.  Of course,
the compromises get progressively more unlikely as time goes on
(including keyboard sniffing and signal analysis.)  So the question
becomes, what is secure enough?  If you're only using telnet, with
clear passwords, restricted to a certain range (which, by the way,
despite a recent post to nanog, we are doing; I'd like to say we
left that router open so folks could read my poetry, but the truth
is, we were morons and missed it) you're secure as long as your
backbone links and backend aren't being sniffed.  Physically tapping
fiber isn't terribly easy for the average hacker, and careful routing 
protocol selection and implementation should keep you from external
intrusion.  So really, your back-end that's the most likely way
in.

So... does anybody know how long it takes to hack an ssh key given
identity and identity.pub?  Because, if I have your machine, I have
these... it's just a matter of unlocking your passphrase.  (And not
even that, if you're running ssh-agent and I can get to that...)

-- 
Dave Israel
Senior Manager, IP Backbone
Intermedia Business Internet
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20010731/f40263c9/attachment.html>
-------------- next part --------------
Get to know us
http://www.thestar.com - Canada's largest daily newspaper online
http://www.toronto.com - All you need to know about T.O.
http://www.workopolis.com - Canada's biggest job site
http://www.torontostartv.com - Webcasting & Production
http://www.newinhomes.com - Ontario's Largest New Home & Condo Website
http://www.waymoresports.com - Canada's most comprehensive sports site