[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: ssh are you nuts [THE BOTTOM LINE]
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: RE: ssh are you nuts [THE BOTTOM LINE]
- From: shivak <anarkky_(_at_)_cyberwar_(_dot_)_com>
- Date: Sun, 10 Dec 2000 17:54:07 -0500 (EST)
Jesus Christ this spam has gone on for long enough. Jessem, listen well
and listen ONCE:
since you're having a difficult time understanding anything (maybe we
should just give you a 'man ssh' or 'man scp', i doubt you read those),
here are definitions:
security, as it applies to ssh and telnet, is the ability to
transmit data back and forth between two hosts without a third party being
able to intercept or modify your transmission.
evil means bad.
All the below assumes that traffic happens on an insecure network like the
THE SHORTCOMINGS OF TELNET:
1) ability of third party to read transmission. there is no encryption,
what else can i say. people can learn your password, etc.
2) ability of third party to modify transmission. this is even worse, a
telnet session to a production machine could result in a quick "rm -rf
/" via session hijacking.
3) inability to trust second party. if you telnet to your webserver, you
can't know for sure that you're speaking to your webserver.
HOW SSH FIXES THOSE SHORTCOMINGS:
encryption. jesus christ it doesn't get any simpler than this. the first
two shortcomings are fixed immediately.
the third shortcoming cannot be fixed without prior knowledge. this
problem is nipped in the bud 99% of the time. But this can't be recognized
as an 'evil' of ssh for two reasons:
1) the shortcoming is in telnet as well.
2) some security is better than no security at all (this is a
problem related with encryption theory, but the fact is SSH OPERATES ON
THE MOST SECURE ENCRYPTION PRINCIPLES KNOWN TO MAN. TELNET OPERATES ON
SHORTCOMINGS OF SSH
none really. maybe unnoticeable bandwidth problems, but no one cares.
WHY YOU ARE A LAZY, UNQUALIFIED, AND MISLEADING IDIOT
from what we can make out, you are giving a speech to a relatively
inexperienced unix crowd next month. You are consulting the openbsd
mailing lists on a subject that you *should* be an expert on. Throughout
the prolonged life of this spam thread, you have proved to be not only
inadequate in your knowledge and experience, but even your eloquence has
>From this, we can deduce these things about your future speech:
1) it will show your lack of understanding about basic ssh
2) it will mislead hundreds of inexperienced unix users into
believing your delusions
3) it will be poorly written and orated.
have a good life, and get off of our mailing list. go join a linux support
group or something. maybe then you can listen to people who are just as
incoherent and wrong as you.
Visit your host, monkey.org