Forgot your password?
typodupeerror
Encryption Security

Attacks Against SSH 1 And SSL 170

Posted by michael
from the only-a-matter-of-time dept.
AndyR writes: "SecurityPortal has a very interesting article by Kurt Seifried in which he writes "dsniff 2.3 allows you to exploit several fundamental flaws in two extremely popular encryption protocols, SSL and SSH." He makes many very strong arguments about key validity and the problem with not having a trusted third party signing keys." Don't throw away SSH just yet, it's still a lot better than nothing.
This discussion has been archived. No new comments can be posted.

Attacks Against SSH 1 and SSL

Comments Filter:
  • If the patents really are an issue, then perhaps I can help. I designed a strong password authentication scheme around the same time that SRP was introduced. There were a couple of techniques in common with SRP but I think the overall structure should probably be different enough to avoid the patents. So, if anyone is really interested in moving this stuff forward then I'd be more than happy to provide you with a detailed explaination. Just e-mail orasis@acm.org
  • Credit card companies have fairly sophisticated fraud detection, as these things go, but never underestimate the ingenuity of criminals. It can be easy, but it usually isn't.

    Real organized crime can sell the credit card numbers to trusted parties, who won't get caught spending, and they can get numbers from trusted sources. Put the two in a blender and you've got several apparently unconnected spates of fraud - with some common victims. Everything has been delivered to mail drops, it's pretty hard to chase, and much easier for the credit card companies to pass the "savings" along to you, the customer.

    I've heard of many many people becoming the victims of card fraud. I've heard of relatively few - even scanning police blotters - who got caught for the same crimes. In between is a full percentage point above prime rate.

    The number of people willing and able to exploit - and profit from - man-in-the-middle attacks is considerably fewer.

    Boss of nothin. Big deal.
    Son, go get daddy's hard plastic eyes.

  • Lacking of security mind cam be a major invulnerability indeed.

    A lot of people has installed sshd to enable security telnet-replacement. It surprises me when I found that a lot of people enable BOTH Password authentication and RSA authentication.

    Their rationale is that they want to have higher security in RSA, and convenience in password authentication. Say they setup RSA authenication between their client at home and server at work, but the same user can also login from some other machine with password in case the machine hasn't been setup for RSA connection.

    In fact password authentication effectively breaks the RSA in this case. Why would the hacker bother to temper with the RSA while the system can be intruded by tempering with the weaker password authentication?

    Say you've implmented a very secured physical key-lock on a door, but you also allow people open the door by entering keycode on the keypad in case people forgot to bring key to open the lock(it happens). Enable both password and RSA authentication in sshd is more or less the same thing.

    Of course, it's a way to restrict a group of people using RSA and another group using password authen., but it makes no sense enable both of them for a user.

    More worse, many people still enable both authen, regardless what what I recommended....Is that concept so hard to understand?

  • There WERE known exploits (read: script-kiddies friendly) for SSH1 protocol against its RSA-based encryption (if you compiled ssh1 with it). SSH2 doesn't use it.

    Beside, as the other guys said, they just haven't
    spoof for ssh2 is just not available, YET.
  • yawn. I have seen windows machines that have no open ports run arbitary code. There is something wrong with their TCP/IP stack. It's sad but true. Unfortunately you have to take my word for it and you never would so you will continue to run a toy operating system.
  • Fine, someone go fetch me a two year old child.

    I tried the local two year olds, but they didn't seem to have attention span enough to wait for me to finish the problem, or they didn't understand the words I was using.

    Tough luck. Next time, he should probably go for some better exaggerations. :)
  • Dsniff can be used by u17r4 37337 h4X0r5 to make scr1pts that the k1dd135 can use to do simple local attacks. Once they 0wn3d a router they can download said 5cr1pt and 0wn all the un1x b0x35 on the subnet that have users stupid enough to accept the new keys.

  • by chicago greg (264786) on Monday December 18, 2000 @08:00AM (#552473)
    I consider myself somewhat knowledgable about cryptography in general and SSL in particular. I read the articles by Kurt Seifried, especially the "foundation" articles dates Sep 30, 1999 and Oct 7, 1999. He is very cagey about actually demonstrating an attack, but I think his points are either technically wrong or technically useless.
    First, the technically useless. Every security product/protocol I am aware of is vulnerable to so-called social engineering attacks. That's their whole point! They go around the security perimeter and get "behind" the protection to get humans to give away information. It is certianly fair to analyze the ease to which some products/protocols facilitate this, but I didn't see much of that. Instead, the articles discuss a company called DigitalBond with a solution that perhaps is also vulnerable to social engineering attacks.
    Now lets look at the technical attacks and claims, which are contained in the Sep 30th article. I'll only comment on the weaknesses he alleges are in SSL. His first claim is that you should not order from a store that uses the http GET method. He doesn't say why, and I cannot think of any reason. If the form is submitted with an SSL-secured action (action="https:...") then both are equally secure.
    His next claim is that the user must inspect the certificate of the server every for every SSL connection. He does not say what attack he can mount if the user doesn't do this. I am guessing that he believes the man-in-the-middle can substitute his own certificates and appear to be legitimate. This is firstly not an attack on the SSL protocol, only perhaps on implementations, and secondly it does not work with the implentations I have tested, IE 5+ and Netscape 4.7+. These implementations verify that the hostname you asked the browser to connect to matches the hostname specified in the CN field of the certificate. Of course, you must trust that the CA will do some checking to make sure hostnames actualy belong to the entity getting the certificate, but that is way outside the scope of the SSL protocol. These "flaws" cannot be the basis for later claims of insecurities. These implementations do not rely entirely on having savvy users carefully inspect every certificate.
    I'd like to check up on earlier broswer versions to see if they also behave similarly. I'd be particularly interested in browsers that were in play at the time the article was written, say fall of 1999.
    --greg
  • I always do electrical work with the power on. Of course, I turn the power off first. And then I work as if I still had the power on. Cuz ya never know, it might be on.
    -russ
  • Getting on the phone to call a (potentially unreliable or corrupt) representitive of amazon.com to verify their server id is not likely to measurably improve the security of the transaction, and is almost certain not prevent me from losing anything of value (since my credit card numbers aren't worth that much to me anyhow -- I'd lose some time, but not money, if they were stolen, but I'd probably lose more time if I called every e-commerce site to verify the server id before placing an order). As long as people understand what the CA's are capable of doing, and what they're not capable of doing, I have no problem with them. It does seem that many people are confused about their capabilities, though.

    Printed means of distributing fingerprints should not be overlooked; you could include the fingerprint in small print in printed advertisements. Or perhaps a printed publication listing current correct fingerprints for major e-commerce sites; a "yellow pages" of the internet. It seems "backwards" but it solves a lot of problems. No, wait - I claim copyright on that idea!

    Alternatively, a government-run key signing authority, that only signs keys requested by companies and requires signatures of the company owners/CEOs would be another way of dealing with this. Or perhaps a government "tree of trust" - with Governments able to issue signing keys to certificate authorities, with the proviso that if they are abused the company will be shut down, and the abusers hung, drawn and quartered.

    Then you can be assured the signing authority is as good as the Government. Personally, in a world so corrupt that alcohol is legal and marijuana illegal, I still wouldn't trust it :-)

    How about it, politics?

  • ssh is always a good idea but what is wrong with having an opie install for when you are on the road and can't install ssh on the term that you are using.
  • It is amazing how insecure most real life (for lack of a better term) things are.

    Last time I was at Bank of America they asked me to change my PIN# to one with 4 digits, instead of the usual max of 6 numbers. In the network world, you find administrators that configure systems to require more characters in a password than before, *never* less.

    Take a look at Credit Cards. That's like: "I'm lazy, here's my login and password. Take only what you're supposed to." You try to tell a sysadmin that and he would flip out.

    So yes, "real life" is a lot riskier. Why do we babble over our SSH bits-per-key, when in the real world we give our passwords away to the waitress?

    -Justin
  • Yeah, or hack the firewall at your house.
  • by Anonymous Coward
    I am really getting tired of Kurt. He sends out false alarms and really stupid and sometimes incorrect information. Kind of reminds me of another person (anti-online).

    "For example -- this is oversimplified but essentially correct -- user Alice wants to
    talk to server Bob, and Charlie wants to snoop in on her session so he can read her
    mail. Alice initiates a connection with Bob, Charlie sees this and intercepts it.
    Charlie talks to Bob and pretends to be Alice; on the other side he talks to Alice
    and pretends to be Bob. Alice sends her public key out, which Charlie intercepts;
    Charlie then sends his own public key to Bob. Bob then sends his public key to
    Alice, which is again intercepted by Charlie; Charlie sends his own public key on to
    Alice. "

    Yeah no kidding. Everyone has known this from the beginning. Can you please tell us something we DON'T know?

    You have to check with the person who's site it is or the owner of the SSH server.

    Get the fingerprint directly from them, then you won't have this problem. His little stupid analogy only works when you don't know the person's fingerprint.

    So learn their fingerprint...duh.
  • by Frac (27516) on Monday December 18, 2000 @02:59AM (#552481)
    some guys at MIT developed a file system called SFS - Secure File System. Knowing how untrustworthy DNS really is, they used a novel authentication scheme by embedding the public key and hostname into a string called the HOSTID that's required to connect. Their implementation is based on NFS3, but the key-certifying scheme is applicable to everything.

    http://www.fs.net [fs.net]

  • Well even using ssh in 'secure' network can still introduce the issue of someone snagging passwords along the wire via other methods such as someone using ssh and then using ftp instead of scp or sftp so I would guesstimate that 80% of the times it is always going to be users that are the weak link and not the protocols.

    So as of now I will wait for the next security based document pimping IPSec, Secure Tunneling, Diameter [diameter.org], SSH over SSL over Biometric based authentication, then point out the clueless (l)user who just did something stupid like use a protocol which doesn't provide any encyption down the strech.
  • Read again carefully. Nothing is the difference. It's just that he hasn't coded up an attack for ssh2 yet. But it could be done in a similar way, just a few more details (I am guessing).

    Smthng
  • His first claim is that you should not order from a store that uses the http GET method. He doesn't say why, and I cannot think of any reason. If the form is submitted with an SSL-secured action (action="https:...") then both are equally secure.

    Well, if the store has ads served by a third party, when your browser gets the ad images it will send the third party the refering URL, which is the GET with all your info in it. I don't think this scenario is changed just because the refering page is https. This is a known privacy issue.
  • telnet over ssl (with certs :) ).

    Get stunnel from stunnel.org, and you can SSLize lots of stuff.

    ssh has too much stuff thrown into it, so it's harder to get right.

    Link
  • Of course you can use S/Key for one-time passwords when using SSH and PAM.
  • this is not a problem in ssh.
    this is not a problem in ssl.

    It is a very old, very well known attack approach, which both already guard against (that's what the 'host key changed' message is all about in ssh). If you see that message and haven't been notified (and sent a new key fingerprint to veryfy against by the admins), you *MUST* assume that a man-in-the-middle attack is being employed - it's what the message means!

    Someone in the middle of your connection pretends to be the server to you, and pretends to be the client to your server. Poof, two valid connections, he forwards your data (he has it in plaintext, as he is your server), and you notice only one thing to tell you that something is amiss - that he *did't* know the right server key (ssh has caches it from previous connections to that server's IP, ssl can check the CA's notes about whose key it is) and had to send you a different one.

    So your client warns you that the key has been changed. You need to get the key fingerprint from the server admin (out-of-band, not over the same potentially compromised network) and compare it to the one you recieved (you did do that when you first connected to the machine too, right? it should have come along with your account credentials, if not you needed to ask for it if you cared a bit about security) and make sure it matches the new print the server is offering.

    to get a fingerprint for a host, use ssh-keygen -l -f /etc/ssh/ssh_host_key

    SSL is in a similar situation - the key bears the DNS name if the site it is for, and your browser will warn you if it recieves a key for the wrong site, or not signed by a recognized CA. You didn't turn those off did you? If not, then one or the other will come up when confronted with a man-in-the-middle attack (either he'll send a properly signed key, but not for the right site, or he'll have a forged and unsigned key for the site you were really going to) and you'll know what you're facing.

    for ssl, if in doubt, click the little padlock in your browser, and read the key - see that it's for the site you think it is, and signed by a recognized CA.

    If you don't use these tools correctly, you may as well not use them at all. Everything is in place to detect these attacks (which are not new), but if people simply ignore warning messages that indicate the presence of known attacks, there's not much else that can be done
  • of course it has to run as root - how else could it give your your own account perms when you connect to it (instead of whatever menail ones it would otherwise have)?
  • by Anonymous Coward
    I guess this has consequences for VPN systems using SSH1/SSL technology as well?
  • by Dr. Evil (3501) on Monday December 18, 2000 @08:42AM (#552490)

    Locks are to keep honest people honest

    I disagree, the strength of your locks reflect your assessment of risk. If sufficiently valuable in the real world, locks are replaced with security guards and automatic rifles. Most people don't have anything that valuable, and find it more cost effective to place limits on their credit cards, check up on protection from their credit card companies and take up insurance policies.

    If there were no banks and no insurance policies, would you, with your life savings under your mattress, still say that your locks are to keep honest people honest?

    Besides, this SSH and SSL attack is very well documented, known and understood for a long time to be a limitation of the system. If your life savings are on the line, use callback, challenge response, or don't use remote logins at all.

  • their browsers do... and warn them... unless they click OK and continue anyway.

    In which case they deserve whatever they get.
  • Tough luck. Next time, he should probably go for some better exaggerations. :)

    My point exactly :-).

    "A child of five would understand this. Send someone to fetch a child of five."

    - Groucho Marx
  • These vunrubilities have always existed. It comes from the fact that SSH is not signed by a certificate authority, and as such you cannot trust the server on the other end. If someone cracks DNS etc to direct you to another server, you won't know about it, except for a warning that the key is different from last time.

    SSL is similar, but it is signed on the server side, usually not on the client.

    This isn't anything new, it's just not there are publically available tools to exploit this.
  • by bellings (137948) on Monday December 18, 2000 @08:44AM (#552494)
    It comes from the fact that SSH is not signed by a certificate authority, and as such you cannot trust the server on the other end.

    You most certainly do not need a certificate authority to trust the server on the other end. And for this article to imply that somehow SSH v2 is a solution is downright wrong.

    If you're using SSH (either v1 or v2) to communicate with a server, and you want to avoid the man-in-the-middle attact described by the article, then you must be certain you're talking to to the server, and not to the man in the middle. The only way to do this is to be certain that the public key that you have for the server you want to talk to really is the public key for the server you want to talk to.

    There are several ways to do this:
    • You can copy the public key from the server using some secure method, such as copying it onto a floppy and transfering it to your machine using sneaker net, or transfering it through encrypted email
    • You can copy the public key across the (possibly insecure) network, and verify that the key was not replaced in transit by verifying the key signature by some secure means (perhaps by getting on the telephone with an administrator of the other machine)
    • Although I don't believe SSH directly supports it (someone will hopefully correct me if I'm wrong), the public key can be signed by some trusted third party. If you trust the thrid party, you can trust the key.
    • or, you can simply allow SSH to transfer the public key across the insecure network, and when it asks "should I trust this key", you can simply answer "yes".
    This last method, of course, is the only method that is vulnerable to the man in the middle attack described in the article. Unfortunatly, its also the default method used by most SSH users. Obviously, there are several ways to reliably transfer the public keys without using a signature by a certificate authority.

    It also can not be emphasised enough that a generic "certificate authority" by itself should not be considered a guarantee that you're talking to who you think you're talking to. Getting a signed certificate from a company like Verisign is not an insurmountable problem. Verisign is certainly reliable enough to trust with something like your credit card numbers -- credit card numbers are relatively inexpensive to replace if they're stolen, and stealing credit card numbers is painfully simple through many means much simpler than attacking Verisign. But I certainly wouldn't trust it for anything really important, unless I had absolutely no choice.

    If you're using SSH (v1 or v2), or setting up a vpn, and you want to be reasonably certain you're not talking to a man in the middle, then nothing can replace coping the public key from machine in a known secure and reliable method. And if your client ever says "the signature of the server has changed. connect anyway (y/n)?" be very, very, very certain you know exactly what you're doing before you hit "y".
  • Actually I'll wager OpenSSH is able to require client certificates, since it is built on OpenSSL.

    Well then, you'd lose your wager. OpenSSL has cert handling OK, but the SSH protocol can't use certificates directly

    I did patch OpenSSH (version 1) a while ago so that it can use certificates if they are available via local files or an LDAP server, and am currently trying to get OpenSSH2 similarly able.

    So there's hope yet

  • In the end nothing is 100% secure...
  • Well, on my school's network many of the computers have some kind of load-sharing, where any given name might send a person to more than one computer. Since this is the case, the key "changes" quite a bit. There is, of course an easy solution to this, but if someone wants to go to the least-busy computer, they might expect to see a key change quite frequently.
  • by moz25 (262020)
    Not the best news to start the day with... considering I use SSH on all of my machines. You can bet quite a few people will be following these developments *grumble*

    Moz.
  • well, to simplify matters quite a bit (though allowing a miniscule chance that a malicous key could generate the same fingerprint, this would be *really* hard to do), just send them the key fingerprint and let them compare the fingerprint shown by their client during that first connection with what you told them to expect.
  • Only the ssh.com implementation.

    OpenSSH [openssh.com] supports SSH2 for free (beer and speech).
  • The program ssh2 is non-free. The protocol is not and is already implemented in openssh. Just use the command "ssh -2" if you are using openssh.
  • *nod* However, if yon waiter uses your credit card illegally, it's usually pretty easy to track down when it started and who the guilty party is. Most credit card 'thefts' like this are done by people with a minimum of the daily recommended intake of intelligence.

    However, with online security, all too frequently, the people who are intercepting transmissions or forging them are quite intelligent (or have read the user docs for their script kiddie toy). Therefore it takes a little more then the standard protocols to insure a minimum level of safety.

    No protocol is 100% safe. We accept that. Well, most of us /.'ers do. It's the clueless masses that get all of their tech news from Headline News that panic over this.

    Oh well. Wonder how long it will be before the next "X isn't secure" story on /.?

    Kierthos
  • OpenSSH supports the SSH2 protocol, it has for a while now.
    --
  • SSL2 doesn't have client certificates; that's SSL3. The article says

    While SSL requires that the server authenticate to the user, it is usually an option for the user to authenticate to the server. And since so very few users own personal certificates, it is exceedingly rare for a user to be able to prove their identity to the server in question -- leaving the connection open to attack.

    To which the obvious answer is: pull your finger out and issue client certs to your users. If it's that important that you know who they are, then the effort must be worth it. This article is basically just an enormous troll.

  • Well, SSH1 goes up to 1 right? Whereas SSH2 goes up to 2. That means it's one more secure.
  • Hmm, interesting point.. I'll have to think about this one...
  • You usually use the phone for that.
  • And what if Charlie listens to the traffic on a router

    And how is he going to hack the router? The same way as he's hacking Bobs machine?

  • It should only change when you install a new key. Installation of new sshd shouldn't be sufficient.

    Most of our systems have the same ssh keys they had when we were running Debian 1.3, for example. The upgrade to OpenSSH which was in Debian 2.1 didn't change the keys. Motherboard and disk upgrades have not changed the keys.

    Only YOU should be changing the keys.

  • Oh yeah, Windows boxes are inherently more insecure, Because Dogma Says So. Way to confuse a good point (about the lack of testing of SSH Clients on Win32) with some stupid /bot rage, "G".

    Anyway, I've 'secured' this Windows box the same way you Linux boys always recommend doing it -- shutting off all services, no NBT (==no RPC), and no IIS. And I didn't need to read your sig to know not to run trojans, and lock down IE and not run as Administrator.

    Meanwhile, RedHat keeps finding nice root holes in basic good ol' standbys such as LPD and BIND. I mean, Fucking A, look at the RedHat advisory list: modutils, pine, bash, nfs-util, ed(!)/vim/emacs/joe, PAM, 'usermode', traceroute, openldap, gpm, and so on. All bread-n-butter stuff in the Unix world, and still br0ken. (I won't even comment on the fact that the standard EDitor has a security hole.)

    Oh yeah, but you know the Linux drill -- firewall, kill all the network services, don't allow interactive access. Sounds exactly as secure as Windows!
  • it might be changed by the time the cracker broke it, or at least the cracker would be locked out eventually.

    This is incredably stupid logic. What hacker who broke in wouldn't install a backdoor? And to brute force a SSH key would take literally three google (2^1024, or about 10^309) attempts at login for 1024 bit key. Any admin who didn't notice that deserves the death penalty for stupidity.

    -David T. C.

  • What many people may not realize in this discussion is that the problem of MITM attacks against SSH1/SSH2 is the direct result of the host-based security model that SSH tries to impose on users. UserAuthentication is the worst because it discloses the password to anyone who convinces a client to accept his host key. Strong password protocols like SRP are able to resist these MITM attacks because they are zero-knowledge, i.e. they don't reveal any information about the password while they prove their knowledge of it to the server. There have been a number of postings that elaborately describe schemes to ensure that you have the right host key, be it by writing down the key fingerprint or FTP'ing around of file of known host keys. But this complexity makes it easier to screw things up, and is made unnecessary by strong password protocols. srp-1.7.1 is now available at http://srp.stanford.edu/. It implements secure Telnet-over-TLS with SRP support as well as Kerberos V5 and X11-session-forwarding.
  • SSL is in a similar situation - the key bears the DNS name if the site it is for, and your browser will warn you if it recieves a key for the wrong site, or not signed by a recognized CA. You didn't turn those off did you? If not, then one or the other will come up when confronted with a man-in-the-middle attack (either he'll send a properly signed key, but not for the right site, or he'll have a forged and unsigned key for the site you were really going to) and you'll know what you're facing.

    I didn't think the article was very groundbreaking or anything either but a good one to pass around the office to the technically challenged :)

    But I did get a few things from the article. The above quote could result in a man in the middle attack if the "man" were able to get one of the known CA's to sign a cert for him with that hostname. As goofy as most CA's are, I don't see how difficult this could be.

    It comes back to the eternal question of "who do you trust?". Do you know the registration policies of every CA in your netscape or IE database, or why those CA's are even in the database at all (eg, how were they picked)?

    In a nutshell, I thought that this article was OK because I do believe in client and server certs which are issued by a common CA. If I were to buy something online and I at least knew who the CA was before I went to the secure side of the site, and had already been issued a client cert from the same CA and the browser asked me to pick one of one certs that match that environment, then I would feel as though that connection was much more secure than with only a server cert that I would more likely blindly trust because the url says https:// and the little lock icon is "locked".

  • Some notes to slashdotters:

    The article is long, why? Because I had to explain what SSL and SSH are, most people do not know how public key crypto/etc works. If I do not explain this trying to explain the security problems and why it's an issue would be pointless.

    Before it was hard to attack SSL/SSH connections and do man in the middle. You'd have to write your own software or find some, which as a rule wasn't publically available (you could see it demo'ed at security conferences/etc but I don't remember anyone ever putting it up for anon ftp or on the web). Well now it is trivally easy to find, and the entry level for attacks just got a lot lower. Users should be aware of this.

    Unfortunately I can't offer any really good solutions (go get software package foo and everything will be better). For now dsniff only does SSH1 attacks, so going to SSH2 should help (until somone modifies dsniff, as I point out in the article). How can you verify SSH keys, print out lists of key signatures and tape them to every workstation and teach users to verify them? Not likely. Ditto for SSL, how many of you actually look at the certs servers hand to you, and how many of you have clicked on OK or Continue when the cert is out of date or issued by a non trusted entity (i.e. a self signed cert).

  • SRP is free worldwide for both commercial and non-commercial use. And, AFAIK, now that people are becoming increasingly aware of the security advantages they offer when used with memorized passwords, they are starting to see increasingly widespread use in a variety of settings (not just secure Telnet/FTP).
  • Melissa/ILOVEYOU are fundamentally due to problems in Outlook, not Windows. Yes, they run under the Windows Scripting Host (WSH). Y'know what WSH basically is? It's Microsoft's take on Perl. If Pine or Mutt were designed to automatically run attached shell or perl scripts, at least as much harm could be done by those scripts as by those Windows worms.
  • Installation of a new sshd shouldn't change it. The host key is stored in it's own file [generally in /etc/ssh_host_key*]. Upgrading, changing, rebooting... Unless the backup of /etc is changed, or the system is compromised [thus necessitating a new key], then there is no reason for it to ever be changed!


    ---
    man sig
  • The problem with the warnings are:
    1. They don't show up the first time you connect to a new site
    2. When the warning appears, the user doesn't have any way of knowing whether or not the key change is legitimate, and most will simply ignore it, rendering it useless.
    You can always write down host key fingerprints, but a system that depends on this kind of user vigilance for user security will never scale.
    1. Installation of new sshd

      Been there, done that (this week). All the systems where I've changed out the sshd still have the same key. The key itself is stored in a separate file and isn't going to be affected by changing the binaries.

    2. Upgrade of OS

      I just got through a few of those this week as well, and the systems still have the same key. Again, the key file is not part of the OS, and as such it isn't affected.

    3. Serious mucking with hardware configuration

      Okay, I haven't seen this one for a while, but I've still gone through it and had the key come through intact. IIRC, the most extreme case was switching a system from running on a sun4c machine to running on a macppc box. I moved the harddrive over, booted from CD, and installed the new binaries from there. When I rebooted from the harddrive, the machine came up with the same key.

    The only case I've seen where the key changed was when a machine that wasn't important enough to back-up went down and was replaced with an entirely new machine. The only thing the new box had in common with the old one was the hostname.

    Basically, you should only see key changes in extreme circumstances like that, and in the less extreme case of a CNAME changing to point to a different box, you would hope for some warning, too.


    T. M. Pederson
    "...and so the moral of the story is: Always Make Backups."
  • The point is that these MITM attacks can be prevented without inconveniencing the user or forcing him to get a copy of the host key fingerprint in advance. Strong password protocols resist MITM attacks by using a zero-knowledge password proof combined with the key exchange, instead of trusting a host key and sending the cleartext password encrypted with a key of dubious origin. Some versions of SSH (like LSH) have already incorporated strong password technology into their code - others should take their lead.
  • I generally change a key only when a system (root) is compromised.

    Some people like to change keys periodically (every 2 years or so) on the pretext that doing so limits the vunerability of having a host key brute-forced. (ie, it might be changed by the time the cracker broke it, or at least the cracker would be locked out eventually.) I don't like this, as it increases the complexity of using the software, and trains users to ignore key changes.

    As other posters mentioned, ssh doesn't nicely deal with multiple meanchines all being referenced by the same DNS name. (It looks like the key changes, when you're really just getting a different machine.)

  • For SSL, why would anyone with the ability to perform such an attack bother with a single session? With the amount of time you would take getting all aspects of the attack coordinated, why not just take on the server directly? The only way I would see this pay off is if you where going after SSH, but the shear number of SSL connections that you would have to filter through would make this an excercise in futility.
  • it is never the users. It is the policies of the network. If you don't run an ftp server, and a telnet server then you can't have people using unencrypted protocols. But people insist on running these protocols. Ok, so maybe it is the users now and then, like postit notes on the computer.
  • by dmiller (581) <djm@@@mindrot...org> on Monday December 18, 2000 @03:14AM (#552525) Homepage
    With OpenSSH [openssh.com] you have a chance to thwart these attacks - not only does it support SSH protocol 2, it also displays "fingerprints" for each unknown key it receives from over the network. You can use this fingerprint to do out-of-band checking of key authenticity (eg. by phone, in person, PGP signatures on a web page, etc).

    There is also a project underway to allow OpenSSH to use keys distributed by DNSSEC.

    This attack then comes back to user apathy (i.e not bothering to verify key fingerprints). An alternative (not yet implemented) is some form of PKI, which has its own problems (complexity, centralised trust, revocation issues).

  • by veg (76076) on Monday December 18, 2000 @03:17AM (#552527) Homepage Journal
    For administering a private network, SSH and SSL
    are perfectly secure. You can surely trust keys certificates that you generate yourself. As most of the dsniff tools rely on being on the same segment of ethernet, with careful key management they're not really a threat. Ever tried changing a ssh host key and then sshing into it ? You get the largest, scariest warning that makes you feel totally paranoid.

    Also, if you are connecting to a server for the first time - fingerprints allow you to check the validity of the keys.

    The problem is with connections to machines you can't personally validate, where DNS spoofing could be used, for example with e-commerce sites. But this is what CAs are for. So where's the problem (until a CA gets cracked that is :-).

  • by Idaho (12907) on Monday December 18, 2000 @03:20AM (#552528)
    Well, it may be a little more serious than it looks.

    Okay, these vulnerabilities have always existed and you could live with them because it was quite hard to exploit them.

    However, as the author of the article points out, there is now a very convenient, easy to compile/install, almost 'off-the-shelf shrinkwrapped' set of applications that can do these kinds of things, which means the l33t 5(r1pt k1dd135 are probably going to find it a lot easier to use then before.

    So that's why he writes the article, and I think he certainly has a point here.
  • because windoze boxen are inheritently insecure. Just read my tag line, I bet you get at least three "cute" flash games and the like every month. Even if you don't, I'm sure you don't have the Outlook security patch installed (the one that makes it impossible to open exe's and vbs scripts and the other 100 - yes there's a list - file formats that are infectable). Patching binaries on windoze is trivial. Intercepting keypresses on windoze is trivial.
  • by mugwumpjism (200010) on Monday December 18, 2000 @03:41AM (#552532) Homepage

    This is definitely FUD. The SSH documentation deals specifically with this issue. This is a good thing and SSH's handling of the situation is more secure than a central signing authority.

    What he's basically advocating is removing the need for people to have secure methods for exchanging keys. Instead of having the chance of a "man-in-the-middle" attack during the first connection (which, if you've exchanged the fingerprint of the server with the admin of the server involved, is eliminated), he'd rather that we trust some other person with our security.

    What if:

    1. Someone actually manages to break the key authority's signing key
    2. Someone replaces the key authority's signing key in your browser/software
    3. Somebody working for the key authority secretly leaks the key (a "purchase-key" attack)

    If any of these happen then your security is FUBAR. Bear in mind that the key could potentially be used to attack e-commerce sites, and is therefore pretty valuable. If the secret of the key being leaked is kept well enough, it is quite possible that no-one will ever find out - except for the odd sum of money missing from random credit cards worldwide.

    Compare that to SSH, where upon connecting to the server, you are notified that you are connecting to an unknown host key, and it gives you its fingerprint to check against what you have recorded it should be. If the key ever changes, you are presented with a huge warning message saying that the host key has changed, and that a man in the middle attack may be in progress.

    If you were using this commercially, you generally would be using SSH between two machines that you admin yourself, or between one that you admin and one that your peer's company admins, and you can verify the keys, set them up in each systems ssh_known_hosts file, and rest secure that you are not vulnerable to man-in-the-middle attacks.

    Personally, I think he's trying to promote the idea that "security needs trusted arbitraries" to the corporate IT world - I wonder if Kurt Seifried has received any "donations" from any large key authorities recently?

    Let's face it - if people use security that doesn't need key authorities, then they'll go away.

    Every security system that uses a trusted authority is vulnerable to a purchase-key attack, and don't let anyone convince you otherwise!

  • The simple answer is that the host key changes whenever /etc/ssh/ssh_host_key is changed or replaced.

    This usually happens when a new version of the OS is installed on a given server, and the sysadmin is careless about not moving the contents of the SSH host key to the new server.

    There are some protections against this attack. When the host key is changed, ssh for Unix gives you a warning that you would have to be blind to miss. If you want better protection than that, the best solution is to hack OpenSSH or what not to only accept a key with a given key fingerprint for a given IP. In other words, if the host key is changed, the hacked client will not connect to the host in question.

    - Sam

  • I thought that ssh gave you a warning if someones public key changed. So a simple solution would be to be careful about these warnings. ssh checks public keys, so in the example he gives, ssh would give a warning because Charlies public key is different from Bobs. They important thing is to be careful about how you obtain someones public key.

  • Interesting thought. I was just thinking whether we should be more secure if we used public keys as 'net addresses, so that the address and the authentication are coupled together (I know, I know, this is puuure fiction). Sending data to one address then ensures no-one is tapping that line.

    In your scheme, the following might occur:
    - client: hey router, pass this package on to the server, will ya?
    - evil router: OK (looks inside the package, finds a key request. Starts producing a fake key) Hey client, I just got this package from server. Any idea what's in it? Open it, quick!
    - client: none of your biz! (turns side to router and opens package) Aah, finally, the keys from server! (encodes a package o'data) Hey router, pass this package on to the server, will'ya?
    - evil router: Well, OK.

    This would for instance mean that your ISP can still check out on you if you use SSH and if they desperately want to do so (government!).

    It's... It's...
  • "And there comes a point where too much security slows down the system. Hey, yeah, we could go to 4096-bit encryption, but what's the point? "

    Go? I'm already there for the more secure stuff... ;)

    It all boils down to the concept of an `identity'. There is the identity that pays my enormous phone bills, one that writes this here and now, one that drives the car, another one that exists on my driving license, and a few GPG/PGP identities as well. Tying them all together into one is possible, but legally necessary. I think that's where the problem lies.
    ~Tim
    --
    .|` Clouds cross the black moonlight,
  • by Lion-O (81320) on Monday December 18, 2000 @04:26AM (#552552)
    Thus Alice thinks she is talking directly to Bob in a secure manner, when in fact Charlie is in the middle intercepting the communications, able to monitor them and also to modify the content.

    Bob : 245.345.0.20
    Alice : 245.345.0.40
    Charlie: 245.345.0.50

    Now Alice wants on Bob's machine so he (Bob) opens up the firewall to allow Alice to access his server (don't forget; SSH isn't about encrypting and decrypting email, its a real time connection. And hey; if you need security and therefor use SSH but no firewall I think you're missing the point). Their keys get intercepted by Charlie. Charlie tries to access Bobs machine but is rejected by his firewall. Now what?

  • by bellings (137948) on Monday December 18, 2000 @04:33AM (#552553)
    This is a good thing and SSH's handling of the situation is more secure than a central signing authority.

    black is white. stop is go. SSH's handling of the situation is most certainly not more secure than a central signing authority.

    he'd rather that we trust some other person with our security.

    Look, the article was a tripey piece of crap, but it certainly never said that. The simple, basic fact that the article gave was this -- if you don't verify who you're talking to, then you haven't verified who you're talking to. Somehow, this dumbass managed to make an entire article out of that. And I read it, and got the ad impressions, and everything. I feel dirty.

    For anyone who hasn't taken the time to read the article yet, or ever learn basic security stuff, let me boil it down: In every single system known to man or mathematics, to identify an entity X, you must trust something to say "method Y is an accurate method to identify X". Unfortunately, the default way to get get that identification method in SSH and SSL is fundementally flawed. If entity W has no way to identify X, but wants to talk to X for the very first time, W simply asks X "what is a question that only you can answer correctly, and by answering proves that you are X?" That leads to a false sense of security at best, because entity Z can step in front of X, and provide a false answer to the "how can I identify you?" question. Voila! Now, W is talking to Z, and since Z was presumably smart enough to supply a question it can answer, W will never know that its speaking to Z instead of X.

    Most two year olds could come up with a half dozen solutions for this problem. Certificate Authorities (where, essentially, someone pays a third party to certify that the identification question is a valid one) are certainly one partial solution. Manually transmitting the identification question (usually in the form of public keys) on secure medium is another. Ignoring the problem, because its inconvenient to deal with, is another solution.

    As many people have pointed out already, ignoring the problem is often the "good enough" thing to do anyhow, since intercepting SSH or SSL communications is still several orders of magnitude more difficult than other attack vectors. But saying a Certificate Authority is bad because you can be lulled into a false sense of security is kind of like saying "you should only do electrical work on your house with the power switched on, since switching the power off lulls you into a false sense of security." You're certainly still vulnerable to attacks to the Certificate Authority, in exactly the same way you can still be electrocuted even if you think the fuse box is off. But there are certainly many situations where the CA's are the least inexpensive and effective method to mitigate the most risk.
  • One of the main things that secure protocols are designed to stop is that man-in-the-middle attack.

    The basic idea is to exchange session keys and verification data before a random public key. That way, the attacker can't substitute other public keys, because the attacker would have to be able to generate data based on information which has not yet been sent.

    The article isn't actually talking about the described attack at all, but about spoofing servers. Identification of servers is a substantially different problem, and is a human-engineering one rather than a protocol one: what makes a server the one you are trying to connect to?

    The attack is where the attacker wants to convince you that you're talking to the server you think you are by having you actually talk to that server, except that you are not talking directly. Most encrypted protocols do a good job of insuring that you are connected directly, over an encrypted channel to whatever it is you seem to be talking to. Whether the server you're talking directly to is the one you want to talk to is up to the user and other parts of the system.

  • SSH is as secure as you make it. If you validate server keys rigorously, MIM attacks are impossible. If you regenerate your keys frequently, it's even less likely that you will be compromised. Until quantum-based encryption becomes reality, the 'perfect' security system is just theory. Until then, SSH is certainly good enough for me.

    TCP/IP and UDP provide no built-in encryption or authentication, and it will be a very long time before there is widespread use of IPSec.

    IPSec isn't a solution either. Well, Bruce Schneier certainly doesn't think so, anyway. Check out this [counterpane.com] at Counterpane.

    Sample quote:
    We strongly discourage the use of IPsec in its current form for protection of any kind of valuable information, and hope that future iterations of the design will be improved. However, we even more strongly discourage any current alternatives, and recommend IPsec when the alternative is an insecure network. Such are the realities of the world.
  • If you want better protection than that, the best solution is to hack OpenSSH or what not to only accept a key with a given key fingerprint for a given IP. In other words, if the host key is changed, the hacked client will not connect to the host in question. In OpenSSH the directive StrictHostKeyChecking does exactly this, provided the IP in question is in your known_hosts file.
  • by oolon (43347) on Monday December 18, 2000 @04:50AM (#552568)
    I find the quest for the holy grail of perfect encryption/perfect protocol rather odd.

    Why do we put locks on doors? To stop people walking in an stealing our stuff, So lets lock the windows, fair enough better security, people are less likely to break in that good. Fit an alarm?

    So why not fit better locks? etc etc every upgrade costs money, and as it gets more expensive I get less return on my money. However this is completely ignoring one factor, insurance!

    My SSL connection to buy a porn flick via my credit card... Hmm, how much do I care about it being broken.. well a thief just wants my number, my gf might be interested in my buying porn.

    My GF does not have the skills to break the encryption, so SSL is secure. A thief, well so long as the Credit Card company pays up if someone else uses it I really don't care.

    A tool should be fit for the job, SSL with real world insurance is seccure for credit cards, the day they don;t pay out, SSL falls!

    James
  • Since neither SSH or SSL use signed certificates on both ends they are potentially open to attack.

    I'll put my hand up in the air and admit I don't know much about SSH -- but SSL most certainly supports signed certificates on both ends: it's up to the server whether it requires a valid client certificate, up to the client whether it requires a valid server certificate. Try adding 'SSLVerifyClient require' to your Apache/Mod_SSL directory stanzas sometime.

    Just because many deployed SSL applications choose not to use client certification (presumably because of the hassle for users of obtaining a client certificate) does not mean the protocol doesn't support it.

    Actually I'll wager OpenSSH is able to require client certificates, since it is built on OpenSSL.
    --
  • by linuxelf (123067) on Monday December 18, 2000 @05:16AM (#552573) Homepage
    Well, this isn't actuall as bad as you might think. The attacker has to be in a pretty specific point, somewhere between you and your target. Some script kiddie sitting at home with his road runner account will still need to hack into an ISP that's routing your packets in order to intercept. And, that warning that SSH gives saying that they key changed should never be ignored. If you get that, drop the connection.
  • What this guy needs is a "freshman shooters course". Every FAQ, HOWTO, Guide for Lamers states that the most dangerous process is the key exchange. If you don't trust the channel don't exchange keys. JUST DON'T DO IT!!! Grab a disquette, write the key, pick an envelope and send it to Alice's Aunt in the name of your dog. That's if you and Alice are thousands of kilometers apart and you are damn paranoid. On smaller distances it is much simpler. On local networks it should not be a great problem. Depends on the sysadmin and your colleagues but hey, Alice is a desk away... If you are a sysadmin it SHOULDN'T be a problem. If this doesn't happen then what are you administering?

    That's the main problem. Key trnasfer. And this is the same problem as transferring and storing cypher books, passwords and many other things. In the rest SSH has shown that problems drop several orders of magnitude.

    Now a problem. Why do I need a third party here? I need thrid parties only for a very specific set of problems. I can come to Alice and drop the key in her computer. Now in cases of extreme paranoidism I may ask a third party to do that job for me. For example, I know that Alice's Uncle is really angered for kicking his car. And I still remember what he said about me and Alice with that old rifle in my nose. But I do trust that Alice's Aunt will deliver her my diskette...

    Other case is chenging info with a party I do know too much. For example a commercial transaction with some e-shop. We may use a third party we trust to process our transactions.

    However, in these two cases we have a problem. We should trust the third parties. And the level of trust depends on how good I know them, if the channel between me and them is secure and what do I need them for. Interknowledge is something quite relative. We see many third parties in e-commerce and even don't know a thing about them. It does not matter too much if we just wanna buy a computer and we don't want our credit/debit card numbers being stollen. The problem of the channel gets up to the same level as Alice's problem. What if someone intercepts this "certificates" and keys? In the end, the need. Do I need them for e-commerce? Sure. For my local network. No thanks! Wanna come? Cool, where's the AK-47? It's our private property and no one has a damn to do here. I can myself run over the workstations and exchange the keys...

    Besides there is a problem of centralization. Certifications are a form of centralization. What may happen when huge corps, states, mobs, large and small nets, individuals and computers will be tighten to such a thing? Forcing certifications over everything is the biggest error possible. That will break exactly the fundament of public key encryption, that each individual has the possibility to set its own key for private exchange of information. Such move will be the revival of such things like CLIPPER...

  • I would rather get fired than have management dictate security issues to me. Thankfully I've never run into that kind of pigheadedness. If the geek says it aint safe, it aint safe.
  • by dasunt (249686) on Monday December 18, 2000 @02:22AM (#552582)
    I don't think twice about giving my credit card to a waiter at a restraunt, although its rather easy for the waiter to use the information to charge false expenses to my account (and it has happened to other people before). Its nice to have security holes pointed out, but really, locks are to keep honest people honest, any transaction is potentially insecure, and it pays to double check any financial records you receive to find any false charges or transactions. I don't fear this hole, statistically speaking, I suspect real life is a lot riskier.
  • by PigleT (28894) on Monday December 18, 2000 @02:22AM (#552583) Homepage
    "In the end nothing is 100% secure... "

    Of course. I knew that.

    But the article doesn't say anything new at all. I've long-since known about the possibility of interception, and when it comes to signed documents, the presence of a digital signature on a document, even one that matches someone else's signature, does not mean that that person wrote that document. (It means there exists at least one person out there who knows the private key password for that identity and/or chose to apply it to the document; if you go around signing things you didn't even write yourself willy-nilly, the whole concept loses any strength it had.)

    Again, this is a luser-space problem. There is no security vulnerability in ssh that's been discovered, this is an "if you abuse it you'll lose it" article. Well woopie-doo.
    ~Tim
    --
    .|` Clouds cross the black moonlight,
  • And I forgot to carry on ranting... ;)

    You should always double-check identity for yourself instead of taking someone's word for it. Anyone can ask Thawte or Verisign for a certificate; the money does not by security of identity for later transactions, unless you're a very gullible PHB, basically.
    Oops, there goes "e-commerce", oh well.

    This applies even more so to SSH, where you really must check the server's fingerprint before connecting. If that means phoning up the sysadmin remotely to confirm it, go ahead.
    ~Tim
    --
    .|` Clouds cross the black moonlight,
  • If you don't run an ftp server, and a telnet server then you can't have people using unencrypted protocols. But people insist on running these protocols.

    Sometimes it is the users, particularly those users with authority over you (like the ones who sign your paycheck). If they demand a service despite your protestations that the service in question compromises security, you are left with little choice but to provide the service knowing full well that it creates a security hole in your network, or look for a new job. In this case it is the user's fault, not the administrator's whose advice is being ignored or overridden.

    That being said, you make an excellent point. The first thing anyone should do when building a new system is install ssh (including sshd) and disable telnet and ftp (on Linux/Unix: comment out the two entries in /etc/inetd.conf, then either reboot or kill -1 [pid] where [pid] is the process id of the inetd daemon).

    As we've seen in this article, running ssh isn't a panacea, but it is a hell of a lot better than using no encryption at all
  • by FreeUser (11483) on Monday December 18, 2000 @05:31AM (#552601)
    If each administrative domain could maintain its own key-signing/authentication service, then at least enterprises, ISPs, and the like could provide solid security between their own systems. Contact between such entities could be preceeded by "out-of-band" authentication or exchange of keys (e.g. something like a PGP key signing party, a phone call, or an exchange of keys signed by a trusted third party).

    The flexibility of the current approach could be maintained, with added levels of trust ranging from completely secure to completely open to "man-in-the-middle" attack.

    There is still the possibility of abuse, however, as the "trusted third party" (particularly in the case of ISPs) could easilly be subverted by a law enforcement or spook agency into signing counterfeit keys. Indeed, they could legally be required to do so with legislation akin to the wiretapping laws requiring phone companies to provide technical facilities that facilitate evesdropping by law enforcement on demand.
  • by QuMa (19440) on Monday December 18, 2000 @06:35AM (#552603)
    It's just a man in the middle attack, hardly worth the electrons it's published with. Anyways, it claims man in the middle is fundamentel to public key is not true. The interlock protocol by rivest and shamir is quite effective against this sort of thing... The following description is quoted from Applied Cryptography by Bruce Schneier, second edition (page 49):

    The interlock protocol, invented by ron rivest and adi shamir, has a good chance of foiling the man-in-the-middle attack. Here's how it works:
    1. Alice sends bob her public key.
    2. Bob sends alice his public key.
    3. Alice encryptions her message using bob's public key. She sends half of the encrypted message to bob.
    4. Bob encrypts his message using alice's public key. He sends half of the encrypted message to alice.
    5. Alice sends the other half of her encrypted message to bob.
    6. Bob puts the two halves of alice's message together and decrypts it with his private key. Bob sends the other half of his encrypted message to alice.
    7. Alice puts the two halves of bob's message together and decrypts it with her private key.
    The improtant point is that half of the message is useless without the other half; it can't be decrypted. Bob cannot read any part of alice's message until step 6; Alice cannot read any part of bob's message until step 7. There are a number of ways to do this:
    • If the encryption algorithm is a block algorithm, half of each block (e.g., every other bit) could be sent in each half message.
    • Decryption of the message could be dependent on an initialisation vector, which could be sent with the second half of the message.
    • The first half of the message could be a one-way hash function of the encrypted message and the encrypted message itself could be the second half.
    To see how this causes a problem for Mallory, let's review his attempt to subvert the protocol. He can still substitute his own public keys for alice's and bob's in steps 1 and 2. But now, when he intercepts half of alice's message in step 3, he cannot decrypt it with his private key and re-encrypt it with bob's public key. he must invent a totally new message and send half of it to bob. When he intercepts half of bob's message to alice in step 4, he has the same problem.
  • I apologize for my tone. And I also apologize for my conclusion... I'm reading a lot of posts on here saying "SSL is secure because it uses a CA, and SSH is not secure because it does not use a CA." Apparently, the exact function of a CA isn't generally well known; if the attitude of posters on slashdot is any indication, there are quite a few people who believe CA's provide some type of "magic" security.

    I agree that the way CA's are generally used today, where often the only existing CA (VeriSign) is alone used in some kind of binary "trust/not trust" is almost insane. And for most of the traffic SSH is used for, methods of exchange are usually possible that are orders of magnitude more secure than trusting Verisign.

    But for one of the most common types of encrypted traffic -- transmitting mostly non-sensitive information to e-commerce sites -- I think CA's are a fairly reasonable solution. If someone decides to steal my credit card numbers, Verisign is not the weak link. Getting on the phone to call a (potentially unreliable or corrupt) representitive of amazon.com to verify their server id is not likely to measurably improve the security of the transaction, and is almost certain not prevent me from losing anything of value (since my credit card numbers aren't worth that much to me anyhow -- I'd lose some time, but not money, if they were stolen, but I'd probably lose more time if I called every e-commerce site to verify the server id before placing an order). As long as people understand what the CA's are capable of doing, and what they're not capable of doing, I have no problem with them. It does seem that many people are confused about their capabilities, though.
  • Has anyone tested dsniff 2.3 against the Stanford SRP? SRP has several different aspects from SSH, and is advocated by many as a more secure alternative to SSH. It wraps legacy applications like telnet and ftp around an encrypted package. Also, I would be curious from anyone who uses SRP to see if dsniff can be modified to exploit SRP. Thanks!
  • wow, an on topic FP.

    Basically as long as you are 100% sure who you are talking to on the other end your connection will be secure.

    The problem comes from there being no way to be 100% sure who is on the other end without signed certificates on both ends. Since neither SSH or SSL use signed certificates on both ends they are potentially open to attack.
  • True.

    "On the Internet, no one knows you're a dog."

    Just because I say I'm someone doesn't mean I am really that person. Just because I am using the PGP or SSH key of Joe Smith doesn't mean I am Joe Smith. Now, it's pretty likely that I am, but the possibility still exists that some 733t h4xx0r or script kiddie got them from Joe.

    And there comes a point where too much security slows down the system. Hey, yeah, we could go to 4096-bit encryption, but what's the point?

    Basically, it boils down to a couple points:

    1) If you absolutely, positively don't want anyone else but the intended reader to see some private communication, hand it to them. No transmission media is 100% secure.

    2) There comes a point where security paranoia limits efficiency. We're damn close to the paranoia limit.

    Just my 2 shekels.

    Kierthos
  • Information on burnable credit-card sizeed CD-ROMs is available at:
    http://www.fadden.com/cdrfaq/faq07.html#[7-15] [fadden.com]

  • by phaze3000 (204500) on Monday December 18, 2000 @02:38AM (#552611) Homepage
    For those that want to check out dsniff itself, the URL is:

    http://www.monkey.org/~dugsong/dsniff/ [monkey.org]

    Clever stuff...


    --
  • But even if you have certificates signed by a third party, that's not the end of the story.

    For instance, what are the certification policies for your CA? How does he check that you really are who you say you are? How does he know that you manage the server you are requesting a certificate for? How does anyone else know that?

    A VPN doesn't really help. Whenever you get authentication material from certificates there still remains the problem of identifying what entity is bound to that key, and what level of trust you should give to it.

    The article doesn't really establish weaknesses in either SSL or SSH. It simply explores the problem of how to trust public keys -- which has been going on ever since PK systems were developed (think PGP, X.509, etc)

  • by Alik (81811) on Monday December 18, 2000 @02:39AM (#552613)
    As pointed out in the article, you can't really defeat stuff like this through user education, because Users Are Dumb. Seems to me that you *can* do the sort of risk-reduction that Schneier's always talking about. Therefore, o wise Slashdot users (I'm pretty sure there's one of you somewhere...), when is it reasonable to see a host key change? I can think of:
    1. Installation of new sshd
    2. Upgrade of OS (new software installed)
    3. Serious mucking with hardware configuration (not sure why --- I guess the keygen code uses some parameters as a seed)

    I'm also pretty sure that rebooting the system isn't supposed to change the key. So what else is there that can legitimately change a key?

    (And yes, I *did* try to RTFM. Checked the SSH specification, but that just says that hosts MUST have keys and MAY have multiple keys. STFW didn't help either; bunch of tech support announcements that some host somewhere was changing its key.)
  • by Paul Crowley (837) on Monday December 18, 2000 @02:29PM (#552617) Homepage Journal
    I don't think you can plausibly apply the interlock protocol to SSH. When I log into a server, I expect a conversation in which each side reads the message from the other before generating their own messages. If that's the fundamental top-level conversation, any attempt to impose an interlock underneath that, unbeknownst to the communicating parties, can be spoofed.

    Interlock only works if the actual communicating parties know they're interlocking. No attempt at automated interlock is going to work, because the MITM can separately spoof two separate interlocked conversations.

    No, the correct answer is strong password protocols like SRP [stanford.edu] and B-SPEKE, as another poster has already observed ("Encrypted Key Exchange").
    --
  • Strong password protocols are the Correct Answer to this problem. If one party (the client) can't carry around the keys needed for strong authentication of both parties, if all you can carry is a password in your head, then strong password protocols like SRP [stanford.edu], B-SPEKE, and some others on their way (AMP) are the correct route to strong security. The most effective attack known on these protocols is

    1. Decide which end you want to spoof - client or server
    2. Choose a guess at the password
    3. Do a protocol run.
    3a. If you're pretending to be the client, try and log on using the password you've guessed.
    3b. If you're pretending to be the server, somehow persuade the client to try and log onto you thinking you're the real server.
    4a. If you guessed the password correctly, congratulations! You've successfully spoofed your way in.
    4b. If you did not guess the password correctly, you lose! And you have learned *nothing* except that your guess was wrong.
    5. If you want to have another guess, you'll have to return to step 1 and persuade the other end to play with you again. They may tire of this game before you do.

    (Caveat. Password files have to be kept secret for this: compromise that and you can spoof the client into thinking your the server, while running a dictionary search against them on your supercomputers. Guard password files)

    Strong password protocols are Right and Good and should be used everywhere that stronger authentication is not available. Remember to use key stretching on your passwords too.
    --
  • I meant to say: explanation of key stretching [cluefactory.org.uk], and the paper about it [counterpane.com].
    --
  • hear, hear.

    If you use Open SSH and always check your key fingerprints, this is not an issue. Whenever I set up SSH on a new machine I copy the key fingerprint into my Handspring Visor. Then I can check it when I connect remotely. That eliminates the man-in-the-middle attack. This is not that hard to do, the SSH documentation talks about these things.

    I prefer this to trusting a certificate authority (and probably having to PAY a certificate authority. Ugh.)

    I do occasionally worry about using Putty SSH to connect from windows machines - somebody who broke into the Windows box could grab my password like that, but hey, you have to draw the line of paranoia somewhere. And CA's don't help at all for that problem anyway.


    Torrey Hoffman (Azog)
  • by XNormal (8617) on Monday December 18, 2000 @07:24AM (#552626) Homepage
    Encrypted key exchange algorithms such as SRP and SPEKE provide strong password authentication which is resistant to all known passive and man-in-the-middle attacks. An added benefit is that they authenticate the server to the client as well as the other way around. And all this is done without PKI and without even requiring particularly strong passwords.

    Why are they not in widespread use? It might have something to do with the fact that (AFAIK) all these algorithms are patented. SRP is patented by Stanford but apparently they allow it to be used without licensing fees in free software.

    Another problem is that these algorithms cannot be used with the existing password databases. Replacing critical components such as /etc/shadow, passwd and requiring all users to change their password to move to the new system is never going to be very popular with system administrators.

    ----
  • Now, W is talking to Z, and since Z was presumably smart enough to supply a question it can answer, W will never know that its speaking to Z instead of X.

    Not entirely true.

    If you are using SSH to connect to a machine, the automated key exchange and authentication may be 'impossible' to do without being vulnerable to man-in-the-middle attacks. However, once you've logged in, compare the /etc/ssh_host_key.pub to the ~/.ssh/known_hosts key you just got; if they're different, watch out! It would have to be a very smart sniffer program to realize 'cat /etc/ssh_host_key.pub' and all other variations should get the 'fake' key substituted in.
  • by QuantumG (50515) <qg@biodome.org> on Monday December 18, 2000 @02:44AM (#552631) Homepage Journal
    bah. I have seen a few people intercept SSH before but only at demonstrations. I knew all of these guys and they said they have never wanted for accounts - there's enough unencrypted traffic to not bother going after the encrypted traffic. If there is one box that no-one connects to without using ssh, it is almost always connected to from an insecure box and, at present, there is nothing to stop tty sniffing. I wont even bother mentioning people who use windoze ssh clients. On most "secure" networks, ssh is the strong link in the weak chain. As for SSL, I have never seen an intercept of SSL by anyone who didn't have the SSL certificate.
  • First it was firewalls, then intrusion detection systems, then VPNs, and now certification authorities (CAs) and public-key infrastructure (PKI). "If you only buy X," the sales pitch goes, "then you will be secure." But reality is never that simple, and that is especially true with PKI.

    Certificates provide an attractive business model. They cost almost nothing to make, and if you can convince someone to buy a certificate each year for $5, that times the population of the Internet is a big yearly income. If you can convince someone to purchase a private CA and pay you afee for every certificate he issues, you're also in good shape. It's no wonder so many companies are trying to cash in on this potential market.With that much money at stake, it is also no wonder that almost all the literature and lobbying on the subject is produced by PKI vendors. And this literature leaves some pretty basic questions unanswered: What good are certificates anyway? Are they secure? For what?


    Taken from a prior document written by Bruce Schneier which can be found here [securify.com].

    Man in the middle attacks have been rampant for some time now so I don't know why anyone would use an article such as this for 'clarity's' sake where security is concerned. Sure it assists in dealing with issues and bringing them to light but when you need that much of a level of trust the easiest way to circumvent ANY man in the middle attack or any other form of an authentication issue can be achieved simpler via way of verifying a PGP key id over the phone before any trusted information is encrypted and sent down the wire using any key.

    Would've made a nice longer post but Monday morning hangovers leave me feeling pissy

    My Slashdot Spoof [antioffline.com]

UNIX was half a billion (500000000) seconds old on Tue Nov 5 00:53:20 1985 GMT (measuring since the time(2) epoch). -- Andy Tannenbaum

Working...