Slashdot Mirror


Cryptography 'Becoming Less Important,' Adi Shamir Says

Trailrunner7 writes "In the current climate of continuous attacks and intrusions by APT crews, government-sponsored groups and others organizations, cryptography is becoming less and less important, one of the fathers of public-key cryptography said Tuesday. Adi Shamir, who helped design the original RSA algorithm, said that security experts should be preparing for a 'post-cryptography' world. 'I definitely believe that cryptography is becoming less important. In effect, even the most secure computer systems in the most isolated locations have been penetrated over the last couple of years by a series of APTs and other advanced attacks,' Shamir said during the Cryptographers' Panel session at the RSA Conference today. 'We should rethink how we protect ourselves. Traditionally we have thought about two lines of defense. The first was to prevent the insertion of the APT with antivirus and other defenses. The second was to detect the activity of the APT once it's there. But recent history has shown us that the APT can survive both of these defenses and operate for several years.""

250 comments

  1. He put the S in RSA by Anonymous Coward · · Score: 5, Interesting

    Without him, it'd just be RA, which isn't even RAD.

    1. Re:He put the S in RSA by ls671 · · Score: 2, Funny

      He put the S in Rivest-Shamir-Alderman

      --
      Everything I write is lies, read between the lines.
    2. Re:He put the S in RSA by a_hanso · · Score: 4, Informative

      He put the S in Rivest-Shamir-Alderman

      You mean Adleman.

    3. Re:He put the S in RSA by ls671 · · Score: 2

      Holy shit , thanks for that.

      https://en.wikipedia.org/wiki/Leonard_Adleman

      --
      Everything I write is lies, read between the lines.
    4. Re:He put the S in RSA by a_hanso · · Score: 1

      No problem. I used to do the exact same thing!

    5. Re:He put the S in RSA by noh8rz10 · · Score: 1

      Thank you for helping with the acronyms, but what the feck is APT?

    6. Re:He put the S in RSA by schitso · · Score: 4, Informative

      Advanced, persistent threat.

    7. Re:He put the S in RSA by treeves · · Score: 1

      Well, he did say that everything he writes is lies. Had to stay true to form.

      --
      ...the future crusty old bastards are already drinking the Kool-Aid.
    8. Re:He put the S in RSA by EETech1 · · Score: 1

      Looks like he could have quite the neckbeard if he wanted to:)

    9. Re:He put the S in RSA by gmuslera · · Score: 0

      Thats why you should use AES-256. Breaking the encryption in RSA is just transposing one letter..

    10. Re:He put the S in RSA by Culture20 · · Score: 3, Funny

      Did he say that, or did he write it? The difference is important.

    11. Re:He put the S in RSA by crutchy · · Score: 2

      it's the debian package manager :)

    12. Re:He put the S in RSA by RoboJ1M · · Score: 1

      *switches to yum*

    13. Re:He put the S in RSA by bluefoxlucid · · Score: 2

      RSA?? You mean that DIFFIE-HELLMAN RIP-OFF?

      It's more like the postman's kid.

    14. Re:He put the S in RSA by Anonymous Coward · · Score: 0

      Is Adleman from Chicago? If so, he might have been an alderman.

    15. Re:He put the S in RSA by Anonymous Coward · · Score: 1

      Yes he did, but didn't RSA suffer a major breach. I am no expert, but when the police are overwhelmed by the bad guys you need more police or better/different police, not less. Sure any system is susceptible to breach, but you would think RSA would have a recovery plan as should every customer, who claims they protect customer data. I'm sorry RSA has failed twice in my opinion. Number one the rumor mill is that, RSA is no longer updating their own products in this space when it's obvious that encryption and trust are more important today than ever. Number two, having your leader announce to the world that the bad guys have essentially won and there is nothing you can do to stop them is a horrible thing to say. As a leader in the encryption field you should have answers to solve problems. Perhaps this article is not the full story, but if I was a RSA customer, my next call would be to another security provider.

    16. Re:He put the S in RSA by ChatHuant · · Score: 3

      RSA?? You mean that DIFFIE-HELLMAN RIP-OFF?

      Eh? How is RSA a Diffie-Hellman rip off? One is an asymmetric encryption algorithm, the other one a key-exchange protocol. While there are some things where you could use either of them, their capabitilies don't overlap completely. Or is it because they both work on groups of integers modulo n? But then they're both rip-offs of the table of multiplication!

    17. Re:He put the S in RSA by darkonc · · Score: 1

      .....But then they're both rip-offs of the table of multiplication!

      Dunno about you, I only memorized my multiplication tables up to about 2 digits, not 800.

      --
      Sometimes boldness is in fashion. Sometimes only the brave will be bold.
    18. Re:He put the S in RSA by bluefoxlucid · · Score: 1

      Uh. How do you think the RSA key-exchange protocol works? Hint: It's an asymmetric encryption algorithm.

  2. no by masternerdguy · · Score: 5, Insightful

    Encryption is the best anti-tampering mechanism you have in computing. Well placed encryption protects OS data from tampering, user data from theft, and sensitive communications secured. It's only getting more important.

    --
    To offset political mods, replace Flamebait with Insightful.
    1. Re:no by Anonymous Coward · · Score: 0

      what about a root kit that installs itself above the OS?

    2. Re:no by masternerdguy · · Score: 4, Insightful

      Code signing to the rescue but slashdotters seem to hate that idea.

      --
      To offset political mods, replace Flamebait with Insightful.
    3. Re:no by masternerdguy · · Score: 4, Insightful

      Before I get flamed, it is possible to do code signing without using it for evil. It's a tool like anything else.

      --
      To offset political mods, replace Flamebait with Insightful.
    4. Re:no by jonwil · · Score: 5, Insightful

      Slashdotters (including myself) dont hate code signing, they just hate code signing where the owner of the computer does not control what gets signed and what can run.

    5. Re:no by happylight · · Score: 5, Insightful

      I think the point is no encryption is going to protect you from users installing malware, buggy software, or just plain hand over data unknowingly. Next to no attackers would attack the cryptography itself. The weakest link is always somewhere else.

    6. Re:no by masternerdguy · · Score: 4, Insightful

      Crypto is part of a full solution containing (crypto), proper segregation of permissions, proper segregation of user data / accounts, proper firewall configuration, proper software configuration, patching vulnurabilities, malware detection (lots of solutions on Windows, chkrootkit on linux), and user education. If I forgot anything add it to the list.

      --
      To offset political mods, replace Flamebait with Insightful.
    7. Re:no by ls671 · · Score: 1

      Encryption is the best anti-tampering mechanism you have in computing

      Let me disagree; the best anti-tampering mechanism is checksums taken from preferably remote access to the file system from a highly protected host. md5sum and the like are your friend to find 0 day exploit root kits.

      Note that this is line with what Rivest-Shamir-Alderman Adi Shamir is trying to warn us about.

      --
      Everything I write is lies, read between the lines.
    8. Re:no by Anonymous Coward · · Score: 1

      And, in the short term, current cryptographic techniques may be good enough that focus needs to be placed on these other links.

    9. Re:no by Anonymous Coward · · Score: 1

      Most of the attacks came by email from unknown senders. If we started using encrypted e-mail to verify authenticity, wouldn't that drastically lower the chance of being infected? By default you would never open files if they were never signed.

    10. Re:no by Kaenneth · · Score: 1, Insightful

      The problem is most owners have no clue how to do code signing, and would rather their equipment/software vendor take care of it.

      My car door/ignition lock came from the factory; I have no idea how to fix it if something goes wrong, but that's fine by me, since for more than 10 years it has just worked.

      The best encryption is transparent to the user; most people won't notice if a link uses HTTP or HTTPS, a bright red bar might get their attention, but that's about it.

    11. Re:no by Anonymous Coward · · Score: 0

      Encryption is the best anti-tampering mechanism you have in computing. Well placed encryption protects OS data from tampering, user data from theft, and sensitive communications secured. It's only getting more important.

      Do not confuse importance with relevance. I believe that was the point he was trying to make. Seems no matter what crypto we use, it's been rather proven that attacks can live below that level and remain undetected. Thus the logical conclusion is use crypto pointlessly, or don't use it at all.

    12. Re:no by Anonymous Coward · · Score: 3, Insightful

      Its fine for someone else to take care of it. The problem is when you complicate it for those who don't want someone else taking care of it. The reasons it is being done differ from those stated. They are doing it with malicious intent.

    13. Re:no by swilde23 · · Score: 4, Insightful

      user education should be printed in all caps, bold, underlined, comic sans, etc...

      At some point, unless we develop new algorithms that utterly break how current encryption algorithms behave (which I know I know, is a possibility... and of course the NSA has it already)... your weakest point is not going to be the computer. It's going to be the lackey at the front-desk happily letting a "tech" in (physically or electronically)

      --
      There are 10 types of people in the world. Those that understand this sig, and those that beat up people who do.
    14. Re:no by ceoyoyo · · Score: 2

      The weakest link is the encryption if you don't have any.

      Encryption has just become so important, and so good, that attackers are forced to look elsewhere.

    15. Re:no by Clarious · · Score: 1

      MD5 isn't that secure, and AFAIK SHA1 usage is not recommended due to near future threats too. The system you referred to is just the same one as my laptop, with the TPM chip as the 'highly protected host'.

    16. Re:no by the_B0fh · · Score: 2

      bah. 15 years ago, there was a post on BugTraq about this internet mapping that someone was doing. The systems were running redhat, everything was locked down, tripwired, only thing running was ssh, and it required certs to get in.

      The guy felt something was wrong. Compared tripwired hashes to what was on the disk. Everything looked good. lsmod, ps -ef, netstat -an, everything looked kosher.

      A couple of days later, he decided to take the system down anyway, and run an offline tripwire. Found shit.

      Can you figure out how they got in?

    17. Re:no by viperidaenz · · Score: 1

      Unless the subject of the email is "NAKED PICTURES OF " Then Average Joe will dismiss all warnings without reading them.

    18. Re:no by happylight · · Score: 3, Insightful

      What you're referring to is more often called information security. Cryptography usually just refers to the methods, algorithms, and protocols of transferring data.

      But there's little point in arguing the semantics of words. I think we can all agree the human factor plays a large part in almost all intrusions these days.

    19. Re:no by Anonymous Coward · · Score: 0

      No. I honestly hate code signing.

    20. Re:no by Anonymous Coward · · Score: 0, Troll

      Yes. In the same way that a gun is a tool for killing, so code signing is a tool for evil.

    21. Re:no by ls671 · · Score: 3, Insightful

      I don't give a damn about how secure it is, I could even use crc-32 if the snapshot takes too long. The idea is only to be alerted about unexpected file changes, especially system executable like; top, login, w, etc. but you should look wider.

      1) Take periodic checksums
      2) Have differences reported
      3) If they don't match documented updates you have an intruder.

      That's why it is recommended to run the checksum program from a secluded host because the rootkit hopefully won't have had a chance to get at the checksum program on the secluded host. View that host as the ultimate secured host in a good rsync backup strategy, the CA in a good PKI strategy, etc...

      It used to be common practice in the old days to take periodic checksums to detect intrusion into systems. Now, with all the fancy IDS solutions around, it seems to be less used but I do not see anything that really replaces it yet.

      --
      Everything I write is lies, read between the lines.
    22. Re: no by Anonymous Coward · · Score: 0

      I keep clicking on your comment, but the pictures don't appear.

    23. Re:no by Anonymous Coward · · Score: 1

      I think the canonical formulation of what you just said is that people aren't attacking the crypto, they're attacking how it's used. (And it's working.)

    24. Re:no by jythie · · Score: 2

      keyboard?

    25. Re:no by a_hanso · · Score: 1

      Exactly. Securing the data is not much use if the programs accessing that data are compromised. If the encryption program is conning you into thinking that your data has been securely encrypted, you're screwed. I'm not an expert in this area, but I don't know why this approach is not more widespread.

    26. Re:no by Sulphur · · Score: 2

      Unless the subject of the email is "NAKED PICTURES OF " Then Average Joe will dismiss all warnings without reading them.

      Hillary Clinton?

    27. Re:no by ls671 · · Score: 1

      Easy analogy: In spy movies, they put a tiny piece of something between the door frame and the door when leaving. If not there when back, then you have an intruder.

      Same basic principle.

      --
      Everything I write is lies, read between the lines.
    28. Re:no by Anonymous Coward · · Score: 0

      System administrators are severely overestimating themselves if they think they can keep an intelligence agency off their network. These organisations have millions of dollars and thousands of extremely skilled employees. And they're not just masters at the technical aspects. Adversaries might even have access to the source code of windows and who knows what else they might know and have. They are ahead of the curve, because that's what they're all about. They will find a way in no matter what you do, you will always be a sitting duck. There is just too much attack surface, and no possibility of retaliation.

    29. Re:no by Anonymous Coward · · Score: 3, Insightful

      Exactly. When the code signing process can not be initiated by the end user should they chose to sign an unsigned executable. It's just asking the vendors of your hardware and OS to establish a monopoly on your user experience by locking out competition.

      This current system of all-or-nothing needs to go unless they offer an easy but out of the way means of signing an executable. All the current system does is make dumb users choose the nothing route and forgo all of the transparent benefits of the all route.

      Hell stick the signer in a control panel app or similar easy to access location. Restrict it to administrative/root level for usage. That's enough to deter anyone from using it unless it's needed. The process should not be so obscure that you must resort to potentially malicious 3rd party sources just to get started. Especially with all the self-proclaimed experts out there that regularly dish out advice like "disable UAC" instead of pointing out the simple process to give an individual program automatically elevated privileges.

    30. Re:no by Junta · · Score: 1

      The problem is the execution. In my mind SecureBoot both restricts the user power *and* comes up short of a comprehensive solution. I can't imagine a comprehensive solution that wouldn't completely supersede SecureBoot strategy and allow user control.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    31. Re:no by EETech1 · · Score: 1

      Seems they've gotten to Bit-9, and found ways to get around that too.

      OS security needs to have a major makeover, zero days for sale to the highest bidder, state sponsored malware with forged certs, vulnerabilities everywhere.

      It's getting scary on the ol' Interweb...

      She ain't what she used to be

    32. Re:no by Anonymous Coward · · Score: 0, Insightful

      Yes. In the same way that a gun is a tool for killing, so code signing is a tool for evil.

      You are a simple-minded fool.

      Killing is not always bad. And guns are efficient tools when killing needs
      to be done.

      Or maybe you'd rather try to "negotiate" when scum who have invaded your home
      are interested in raping your wife and daughter while they make you watch ?

      Do you actually believe the police are going to save you in the above scenario ?
      That is the sort of fantasy naive children entertain. Adults know better.

    33. Re:no by Kaenneth · · Score: 2

      For code signing, if you could sign everything yourself, what stops malware (or an attacker with temporary physical access) with the same privileges as the user from doing the exact same operations, and signing itself to install a rootkit?

    34. Re:no by demonlapin · · Score: 4, Insightful

      This is true but unfortunately irrelevant. You can do all the user education in the world and it means nothing if the IT staff are idiots.

      I have a handful of fairly secure passwords. They're reasonably long, are incredibly easy for me to memorize, and don't rely on any details of my life (pets, wife, kids, birthday, etc.). But I have to deal with websites that demand a series of ridiculous standards: some require (thank you, AmEx) a number in the username, some require passwords to have number, capital letter, and symbol. I spent a lot of damned time figuring out a password that people can't guess, and I can't use it because I can't remember the rules for any random website - so I have to get a password reset email sent to me in plaintext. And on top of that, I can't use a password I've used before - so every time I log into a website I rarely use, I have to reset the password to something I will forget in a few days. I'd use something like Keepass but I need to be able to log in from non-home computers.

    35. Re:no by SternisheFan · · Score: 1

      When you build a better safe, there will always be a better safecracker. Same applies to encryption.

    36. Re:no by tibman · · Score: 1

      15 Years ago there were bugs in ssh?

      --
      http://soylentnews.org/~tibman
    37. Re:no by Anonymous Coward · · Score: 0

      Exactly - if people were encrypting more of the data they have at rest, these breaches wouldn't be so damaging.

      For example, companies handing payment card information have to comply with various PCI requirements regarding things such as never storing credit card information in clear text. If companies would treat other personal info (such as email addresses, names, snail mail addresses, etc) with the same level of concern and keep them encrypted as well, then these attacks wold be far less profitable to the attackers, and there would be fewer of them.

    38. Re:no by Anonymous Coward · · Score: 0

      How about this: Whenever someone is caught deliberately hacking into a computer system, distributing spy/malware or running a bot net work, we take him/her out and shoot them in the fucking head?

      Really, this is like debating how we are going to protect ourselves from muggers by wearing Kevlar and and helmet. Find the perps and deal with them. If fucking China is hacking into our systems,. cut them off. I mean send a ship and sever the cables to China. God Damn you people are such pussies.

    39. Re:no by dbIII · · Score: 2

      Means nothing if the IT policy is set by idiots.

    40. Re:no by grumbel · · Score: 4, Interesting

      I think the point is no encryption is going to protect you from users installing malware, buggy software, or just plain hand over data unknowingly.

      That's a problem of the current day extremely fragile OS design. Stuff a user installs should simply never have the right to do any damage. Just like a HTML app is strictly sandboxed and can't access your whole HDD, so should a native executable. You don't really have to worry about malware when its locked up in a sandbox and can't even modify itself.

      To make quick Unix example of how things should work:

      Wrong way: sed "s/foo/bar/" file
      Right way: cat file | sed "s/foo/bar/"

      In the first one 'sed' has all the rights the user has and can do whatever it wants behind the users back. In the second case 'sed' needs absolutely no rights at all aside from being able to read stdin and could be completely sandboxed away. It's 'cat' that has the right to access users files and pass the data down the line to other programs. Thus instead of having dozens or hundreds of apps with file access, you have just one. Similar concepts can be adopted to the GUI easily where the file dialog (the GUIs 'cat' equivalent) becomes part of the OS instead of the application.

    41. Re:no by grumbel · · Score: 2

      user education should be printed in all caps, bold, underlined, comic sans, etc...

      If the user can break the OS, then the OS wasn't secure enough. It should be completely impossible to get the OS into a state where it's unrecoverable or unverifiable. If the OS fails at that, blame the OS, not the user, maybe then we get some progress in computer security.

    42. Re:no by InfoJunkie777 · · Score: 2

      user education should be printed in all caps, bold, underlined, comic sans, etc...

      At some point, unless we develop new algorithms that utterly break how current encryption algorithms behave (which I know I know, is a possibility... and of course the NSA has it already)... your weakest point is not going to be the computer. It's going to be the lackey at the front-desk happily letting a "tech" in (physically or electronically)

      I would tend to agree. Many of the stories I have read, like the Iranian nuke plants getting infected with Stuxnet, were due to human engineering. Getting to stupid people inside to get access or keywords or geting them to insert an infected thumb drive into the wrong computer. Hard to work against that. People are lazy much of the time.

      --
      Don't explain computers to laymen. Simpler to explain sex to a virgin. -- Robert A. Heinlein
    43. Re:no by tsotha · · Score: 3, Insightful

      Actually, a safe is a good analogy. Nobody actually "cracks" a safe any more, in the same way criminals don't gain access to your computer by cracking your crypto. Safes are blown open, battered open, cut open, or subjected to some fancy chemical attack. But modern high-quality combination locks are impervious to the guy with nimble fingers and a stethoscope (which is a Hollywood thing anyway).

      Installing a rootkit from an email is roughly analogous to having your safe opened because you put the combination in the top right drawer of the adjacent desk.

    44. Re:no by Anonymous Coward · · Score: 0

      Someone must be an academic, or selling a certification, and 2 tablespoons of salt with that I suppose.

    45. Re:no by Anonymous Coward · · Score: 1, Insightful

      "After they take it from you"

      What sort of fatalist defeatist bullshit is this?

    46. Re:no by Anonymous Coward · · Score: 0

      To clarify, OS data is protected with memory protection while running, not encryption. Encryption and signing is on disk (if even used which is not always).

    47. Re:no by hairyfeet · · Score: 5, Interesting

      Exactly, its like how a friend of mine was nearly fired because he wouldn't let a PHB have his "files" from his "friend" Melissa, yep the moron was threatening to fire him if he didn't let a worm loose on the network. Lucky for Glenn the guy above the PHB wasn't a retard and actually kept up on current events so he just said "Is he talking about the worm that's going around?" and then gave Glenn a free steak dinner while giving the PHB the riot act for trying to compromise security for an imaginary girl.

      At the end of the day you just can't protect from a case of the stupids, you just can't. I was quite proud of having an unbroken record, nothing but happy customers and well running systems,until I finally had to throw a customer out of the shop and threaten to call the cops, why? because this was right after Limewire had been shut down, I told him flat footed "The courts shut Limewire down, it doesn't exist and anything that says its limewire is either worthless or a malware laden fake" so guess what he did? promptly went home, downloaded "the new limewire" and then demanded i fix the machine for free because...shock... it was nothing but a bunch of malware with the limewire logo. When i threw him out the shop he was saying "it says its limewire now you make it work!"

      Sadly there is only so much you can do without turning the system into nothing but a locked down, corporate controlled thin client and as long as the user has the right to install you are at the whims of somebody who may be a moron. I learned you do the best you can but at the end of the day stupid is as stupid does.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    48. Re:no by Anonymous Coward · · Score: 0

      >In the first one 'sed' has all the rights the user has and can do whatever it wants behind the users back.

      Is that statement really true if someone is using SELinux? I'd think that would lock down sed a bit?

    49. Re:no by Anonymous Coward · · Score: 0

      If a gun miraculously appeared in his hand when he was tied up and forced to watch - then yes, you are 100% right. But if he had the gun outright, then the story would be much more likely to end in perpetrators running off with their pants full.
      Although, people like you should have guns. You will fill your pants in a blink of an eye and then submit to anyone who looks threatening. However, even you should be allowed to have one.

    50. Re:no by tlhIngan · · Score: 2, Interesting

      user education should be printed in all caps, bold, underlined, comic sans, etc...

      At some point, unless we develop new algorithms that utterly break how current encryption algorithms behave (which I know I know, is a possibility... and of course the NSA has it already)... your weakest point is not going to be the computer. It's going to be the lackey at the front-desk happily letting a "tech" in (physically or electronically)

      First off, any security system designed should account for Dancing Pigs in which security decisions should not be left up to the user because the user will always choose dancing pigs/rabbits/kittens over security basically 100% of the time. (Replace it with whatever - pr0n, pirated programs/apps, "free money", etc).

      And anyone who says users should learn everything about computing before allowed in front of one - do you know everything about your car? Do you want your mechanic to be able to fix your car, or to compile and install a new Linux kernel? (Especially on your dime).

    51. Re:no by Anonymous Coward · · Score: 0

      DICK CHENEY

    52. Re:no by the_B0fh · · Score: 4, Informative

      no. They finally tracked it down. They watched the guy come in and take over the box again. He got in and owned the box in 8 seconds.

      The hacker found an old samba server in Australia (version 0.5 or some such), took it over. Used that to remotely mount the windows desktop used by the researchers in Japan.

      Found the private cert/key on the windows box. Used that to ssh in to the linux server. Ran a zero day gnome exploit and took it over.

      After taking over the server, installed 2 kernel modules that hid itself and also trapped certain calls like the ones used by tripwire and basically returned true for all the operations for tripwire and removed itself from the modules list and the process list.

      damned cool hack, and that was 15 years ago!

    53. Re:no by PReDiToR · · Score: 3, Interesting

      You're looking for Password Hasher and if you're not on your own computer the demo page will work in (nearly) any browser.

      In case you (or someone else) doesn't click it, if you use your UID as the passphrase and "slashdot" as the site tag you get "i0+v+dXNbzPpvpW177NeV9eYnK" at my default settings of 26 characters, upper, lower, numbers and symbols.
      For remembering just your UID. How simple is that?
      To bump it up and alter the password completely when you change it there is a button that will change "slashdot" to "slashdot:1" - a change that is remembered by your browser, or can be written in a text file as a reminder because that isn't sensitive information.

      This is not perfect security but it would go a long way to making identity theft and account hijacking harder if everyone showed their mother and their kids how to use this simple piece of code. They could go on using that one stupid password that is the only thing they can remember but be secure from rainbow tables and GPUs for a few years.

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    54. Re:no by crutchy · · Score: 5, Insightful

      would you remove all the locks on the doors and windows of your house merely because they couldn't stop aliens from abducting you?

      also, window locks are uselss because burglers can simply smash the window

      any level of personal security (even the fake security cameras, lasers, etc) is better than none at all

      but on the other hand, imposing your ideas of "security" on others is not a good idea (such as the TSA)

      people should be free to decide what level of security they think is appropriate for themselves, as long as it doesn't adversely affect others (don't install a nuclear reactor powered ion cannon in your back yard because your neighbors likely won't be very happy having risks from your ideas of security imposed on them)

    55. Re:no by AK+Marc · · Score: 1, Insightful

      Like I said, cowards and liars take the mythical best case of their preferred opinion, and the absolute worst case of the opposite. Every time. Predictable (stupid), cowards, and liars.

    56. Re:no by crutchy · · Score: 0

      except in the case of use by trained law enforcement, how many instances of guns (in the hands of private citizens) having prevented a crime have you ever heard of?

      maybe a lot, but what about compared to instances of guns being used to perpetrate a crime, or in accidental shootings, etc?

      guns may be good in unlikely scenarios (like someone successfully pulling off a dirty harry move when someone breaks into their house in the middle of the night) but they do relatively far more harm than good

    57. Re:no by Sique · · Score: 2

      The problem with code signing is the idea, that there is always one party doing the coding and another party doing the running of the code, and that they are always different. It turns the operator of a computer strictly in the consumer position without a chance to leave it again, because neither self written code nor modified code will be signed. If we allow selfsigning of code, we are back at the situation of being allowed to run every code, and we are back to the spreadfest of malware. The main problem is that even code for simple tasks is utterly complex and mainly unreadable for most of us - either because we don't even have the ability, not being coders, or not the capability, because we have better things to do than reading each and every byte of code we are running. Open Source has its advantage, because there, the signed part is not only runnable code, but source code. Thus we still have the advantage of signed code (proof of origin), but without the disadvantages (we can run modified or selfwritten code without hassle). And the process of executing non signed code is transparent to us and very in the open, because we do the process of installing, modifying and and executing unsigned code, when we are actually know we are installing, modifying and executing code.

      --
      .sig: Sique *sigh*
    58. Re:no by Threni · · Score: 2

      I think that's what he's saying, though. Use it, but stop pretending it's the solution. It's the solution to a decreasingly important part of the overall picture.

    59. Re:no by ls671 · · Score: 1

      You are the man, You got the full picture which I was trying express.

      --
      Everything I write is lies, read between the lines.
    60. Re:no by ls671 · · Score: 1

      I used to be, I would be tempted to blame IDS fud and hype.

      http://slashdot.org/comments.pl?sid=3497631&cid=43021047

      --
      Everything I write is lies, read between the lines.
    61. Re:no by ls671 · · Score: 1

      Also, same thing here. When something is detected that way, set honey pots to discover how they do it.

      --
      Everything I write is lies, read between the lines.
    62. Re:no by ls671 · · Score: 1

      Damn, I meant to say: IT used to be

      --
      Everything I write is lies, read between the lines.
    63. Re:no by grumbel · · Score: 2

      No, that was just a theoretical example of how a secure 'sed' could be build. I don't think it's actually implemented that way anywhere, not even sure if it's possible with SELinux, but it might. The point I was trying to make is simply that you can build a highly flexible toolset (i.e. the Unix toolbox) in a way that has no direct system access.

    64. Re:no by HuguesT · · Score: 1

      Somehow that sounds unlikely. Why was the samba server useful? Why was the researcher's desktop shared? Over the internet to boot? Why was a cert useful to log onto the RedHat box? What was the motivation for taking over the box in this fashion?

      Do you have a link to the bugtraq discussion?

    65. Re:no by L4t3r4lu5 · · Score: 1

      I have my Keepass database hosted on Dropbox, synching with my computer and Android phone. However, the database contains only 4 characters which satisfy the idiosyncrasies of whatver the site requires, e.g. A$s4 for CAPITAL, $pecial, lower, numb3r. In the notes is a number corresponding the position to insert these characters into my easy to remember and secure password, as you have. If the maximum size is shorter than my password, I clip it to the maximum it can be.

      The database is useless without my secure password (which isn't the password to the database), site access is secure as the full password is not stored in the database, and I never need to worry about forgetting a password regardless of the stupid decisions of others. Further, any site storing the key in plaintext only gets the password for that site; They'd need the Keepass database unlocked to use the key anywhere else.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    66. Re:no by UltraZelda64 · · Score: 1

      Stay away from Windows, obviously... problem minimized. Also distrust any other "mainstream" OS and avoid typing up anything important with them. I don't know why the fuck anyone would be using a phone or tablet computer to type up anything important, but Android would probably be included as mainstream... with the added bonus of being easily stolen, since people take the machines that run it everywhere they go.

    67. Re:no by dnaumov · · Score: 1

      I'd use something like Keepass but I need to be able to log in from non-home computers.

      Do use Keypass and install it on your phone as well.

    68. Re:no by CrashandDie · · Score: 3, Interesting

      The problem is most owners have no clue how to do code signing

      Paraphrased: "The problem is most owners have no clue how to safely store a gun." Or even: "The problem is most owners have no clue how to do proper parallel parking."

      Just because you give everyone access to a tool doesn't mean everyone knows how to use it. That's where education comes into play. The same way we educate individuals how to talk, or behave in society. Education is important, hence, that's why it is mandatory up to a specific level.

      I'm not saying everyone needs to know how to do proper code signing, but then again, not everyone knows how to service their car. But just because some people don't know, or don't want to learn doesn't mean that everyone should be banned from servicing their car.

      And there is the real problem: we use the excuse that knowledge is optional to impose restrictions on others. You may not know how your door lock works now, but if you were so inclined, you could still replace it with one of your choosing. You could learn about the mechanics and even make your own. Or you could remove it altogether. Why couldn't you do the same with the lock on your computer?

    69. Re:no by flyneye · · Score: 1

      In this case, the only hiding place left is the first layer of the OSI model. I can't believe no one thinks of that. When you find the final receiving/originating server go to the physical location and either investigate log ins from there or find the culprit sitting on his ass. Recidivism is a concern, so old fashioned arrest is out of the question, especially if it's a foreign country. 3 letter agencies just eat more tax dollars, which leaves us with hoodlums to disappear,the problem/black hat. Hoodlums drive their business, so hoodlums can close their business. It would just be a "move", "business". How much would a person or group or business entity be willing to pay to delete black hats? There would be overhead costs of course, hiring a "white hat" to do the digital work and travel expenses for the physical business meeting.

      It may not totally eliminate the problem, but I'm betting it could drop activity a good 90% once a few disappear and word starts going around. Leave the hoodlum work to hoodlums and quit relying on some money gobbling geek corporation or government clowns to do the job right and actually get it done. It's a first layer problem.

      --
      *Repent!Quit Your Job!Slack Off!The World Ends Tomorrow and You May Die!
    70. Re:no by Anonymous Coward · · Score: 2

      Why was the samba server useful?

      So the attack would not be traced to the hacker's own machine

      Why was the researcher's desktop shared? Over the internet to boot?

      By "desktop" he likely means C$, which used to be shared by default on any windows box with F/S turned on. He's talking about 1997, remember.

      Why was a cert useful to log onto the RedHat box?

      SSH will let you authenticate using a private/public key pair, where the public key is on the server and the private key held secret on the client. If that private key is a) not encrypted/pw protected and b) shared over C$ to the internet, then any random joe can use it to impersonate the owner.

      What was the motivation for taking over the box in this fashion?

      It works. Steal someone's login credentials (through an obfuscating intermediary), elevate privileges, and hide your trail. In fact, I'm pretty sure that's the classic approach to taking over a box.

    71. Re:no by the_B0fh · · Score: 1

      AC gave the perfect answer, but seriously, give it a bit of thought. I had originally mentioned that the ssh server was locked down and only accepted certs/keys, and you come back and ask why a cert was useful to login to the redhat box?

      As for the link, it was just a one liner mention in one post (never seen him post before) that was really about another bug. It was a throwaway line that pointed to a URL, and for some reason, I was curious that day, and followed that URL, and read it, and went *WOW*

    72. Re:no by GameboyRMH · · Score: 1

      The regression in computer security over the last few years is due to "cyberwarfare." Zero-days are being sold to militaries as "cyber-weapons" and being used in a very targeted manner, instead of being sold to common black hats and being used as widely as possible where security researchers can at least find them soon after the fact, or ideally being reported/disclosed.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    73. Re:no by cryptizard · · Score: 2

      This is what Apple is doing now but people flip out about it. Apps in the app store can only interact with files through the OS file chooser, so they are effectively sandboxed and can only see files explicitly allowed by the user.

    74. Re:no by cryptizard · · Score: 2

      You are missing the point of the checksum. In a situation where random error or corruption might happen, then sure CRC is fine because it will most likely catch the change. In an adversarial setting, if someone changes any of your file maliciously they can EASILY craft it so it matches the old checksum. That is the point of cryptographic hashes, it is very difficult to find two things that hash to the same value. If you realize that, then you have to use at least SHA-1 because it is relatively easy right now to craft collisions with MD5.

    75. Re:no by Hatta · · Score: 1

      Is it possible to do code signing without enabling others to use it for evil? It's a tool like anything else.

      --
      Give me Classic Slashdot or give me death!
    76. Re:no by swilde23 · · Score: 1

      I was unaware of the dancing pigs. I love that analogy.

      --
      There are 10 types of people in the world. Those that understand this sig, and those that beat up people who do.
    77. Re:no by Anonymous Coward · · Score: 0

      Even the most conservative estimates of yearly defensive firearm uses say this is not the case.

    78. Re:no by drinkypoo · · Score: 3, Insightful

      When i threw him out the shop he was saying "it says its limewire now you make it work!"

      These are the people I don't understand. Not because they don't listen to you, that's normal. But what I don't understand is why they would trust you to fix their computer when they don't trust you to tell them what to do with it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    79. Re:no by Anonymous Coward · · Score: 0

      I think the point is no encryption is going to protect you from users installing malware, buggy software, or just plain hand over data unknowingly. Next to no attackers would attack the cryptography itself. The weakest link is always somewhere else.

      Correct, but that does not make cryptography "less important". Try tansferring your banking passwords without encryption, and you bank account will soon enough be "less relevant".

      You need encryption more than ever, but perhaps you don't need to think so much about it. Similiar to how you don't consider whether or not to put up with the extra cost of having locks on your doors. Locks are not obsolete just because information and valuables are lost in so many other ways that to the few who actually break locks.

    80. Re:no by Neil+Boekend · · Score: 1

      They should start with telling the requirements for a password after the first attempt. This knowledge is easily found by a hacker, but not knowing this can be a big obstacle to a legitimate user.

      --
      Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
    81. Re:no by Anonymous Coward · · Score: 0

      Unless the subject of the email is "NAKED PICTURES OF " Then Average Joe will dismiss all warnings without reading them.

      Well, don't run an email system that is vulnerable then. Email clients and web browsers don't need to be vulnerable to malware sites or spam. I can read all the spam I want (usually none, I admit) with no ill effect. I can surf attack porn sites - well, not much point in that for all I get is a failed attack instead of the expected porn. But no ill effects for the computer. No viruses "picked up".

      Just get rid of the vulnerable software, for there are good alternatives to all of it now. You don't need outlook, in particular. You don't need an os that is suceptible to viruses at all, for that matter.

    82. Re:no by blueg3 · · Score: 1

      because it is relatively easy right now to craft collisions with MD5.

      Only if you control the original file as well as the new file. (Or, more simply, it's easy to craft two files with the same MD5 hash provided you're able to modify both files.)

      Crafting a new file that has a chosen MD5 hash (or, equivalently, has the same hash as a preexisting file you cannot modify) is still hard.

    83. Re:no by frinkster · · Score: 2

      This is what Apple is doing now but people flip out about it. Apps in the app store can only interact with files through the OS file chooser, so they are effectively sandboxed and can only see files explicitly allowed by the user.

      Apple is going even further with this, as an App Store "app" - now is encouraged to contain XPC services. Each service runs as its own process (started and stopped by the OS as needed) within its own sandbox and its own reduced set of privileges (and it is explicitly NOT possible for one of these services to get root).

    84. Re:no by Anonymous Coward · · Score: 0

      Not quite. It's like the bank owner inviting you in to the open vault and being oblivious to your presence.

    85. Re:no by steelfood · · Score: 1

      if you use your UID as the passphrase and "slashdot" as the site tag you get "hunter2"

      That's funny... I see hunter2.

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    86. Re:no by Natales · · Score: 1

      1Password will do the trick. It works on almost every platform and you can access your encrypted items remotely via Dropbox with a fairly nice HTML UI.

    87. Re:no by TangoMargarine · · Score: 1

      Except for the part where if the person in question knows you use this service and your username, you're basically just leaving your login without a password.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    88. Re:no by That_Dan_Guy · · Score: 1

      I think many people are missing the point of what was being said in the article.

      Cryptography is not just about keeping secrets, it's also about verifying identity. The article pointed out that if CAs are under pressure from their local Gov'ts to issue false certificates to them (happened in Turkey) the whole PKI is useless for identity verification as you can't trust any CA after that.

    89. Re:no by tibman · · Score: 1

      Cool but GNOME had not been released 15 years ago. I'm not even sure if the kernel had module support either. It just got ELF at the time, as an idea for kernel maturity. But getting the key would be a slick way in. Like leaving the keys to your house in the mailbox : /

      --
      http://soylentnews.org/~tibman
    90. Re:no by the_B0fh · · Score: 1

      Gnome was started in 1997, so, right by there. It was many many years ago, in my first job, so pre-y2k.

    91. Re:no by hairyfeet · · Score: 1

      Beats the shit out of me Drinkypoo, you'd think that with over 20 years of exp they would at least understand I know WTF I was talking about, or why would they bring it to me in the first place?

      To me the bitch was the limewire installer was exactly what I said it was yet he expected me to "magically" make the limewire network come back to life so he could use it....WTF? I've had idiots that would tell me to "just hack it" like I can magically reset passwords on servers halfway around the world (I always make the "hack the gibson" joke they never get) but at least once i explain a little about how what they see on the screen is NOT actually on their computer? they at least see I can't magically make it work. This bozo had decided that I could rebuild the limewire network AND magically turn a fake installer into a functional one and thought if he got in my face he could get me to do it.

      But I spent 3 years playing behind chicken wire, had a gun put in my face by a mobster, so needless to say this fat fuck wasn't gonna intimidate me, I shoved his ass out the door and told him if he didn't leave I'd call the cops. But it amazes me sometimes how clueless a person can truly be, and not listening to me is expected but to not listen AND want me to do the work?

      --
      ACs don't waste your time replying, your posts are never seen by me.
    92. Re:no by OdinOdin_ · · Score: 1

      tripwire much ?

      http://www.linuxjournal.com/article/2160 "Tripping up Intruders with Tripwire, Issue #40, Aug 01, 1997"

    93. Re:no by OdinOdin_ · · Score: 1

      Sure you have to craft the file to match MD5 but also be interpreted as a substitute of the original but with evil data.

      This can become an easier problem to resolve if you are allowed unlimited length of input, but with a digest hash it becomes much harder if you also sign the input length the same as the original.

    94. Re:no by Anonymous Coward · · Score: 0

      you know .... you'd almost have to look ....

    95. Re:no by Anonymous Coward · · Score: 0

      The problem with "broken" hashes is that someone could modify your executable binaries, then pad it with garbage data that is planned to induce a hash collision. If it's trivial (and md5 is seen as being so,) then your "known good" files are replaced, but hash the same.

    96. Re:no by Anonymous Coward · · Score: 0

      As a hacker (the good kind) it took times of breaking windows to understand how it works to the level I now understand it at. Personally I wouldn't have it another way. real problem users, like yourself, feel they shouldn't be held accountable. "It's the computer's fault.

    97. Re:no by Sabriel · · Score: 1

      If you've got a system where the user(s) log in as admin/root a lot (for whatever reason), make the code signing app require rebooting into a special mode.

      If you've got an "attacker with temporary physical access", you've got bigger problems. Start looking at full disk encryption, multi-factor authentication, etc.

    98. Re:no by ls671 · · Score: 1

      Obviously you check file size too. Additionally, the intruder doesn't know which kind of checksum you use and nothing prevents you from using more than one checksum scheme. Damn it, just use rsync with incremental backups to detect changed files and use diff if you are really paranoid about collisions.

      --
      Everything I write is lies, read between the lines.
    99. Re:no by Anonymous Coward · · Score: 0

      Since KeePassX encrypts the key db, you can put it in Dropbox and share it. That's what I do. :)

    100. Re:no by PReDiToR · · Score: 1

      Knowing that I use "slashdot" for the site tag, or maybe "slashdot.org" as it can be configured to default to, does not mean you know what I use for my passphrase.
      I used his/her UID for an example. The previous reply to my post obviously used his code "*******" (which is all I could see) instead of his UID to create the password.
      This in NO WAY is less secure than using "hunter2" to log in, and using "slashdot" and "hunter2" yields "4bnth/jYK1JCBP32NZzGjQUHKd"

      --

      Do not meddle in the affairs of geeks for they are subtle and quick to anger
    101. Re:no by Sigg3.net · · Score: 1

      But I'm a dog person, you insensitive clod!

    102. Re:no by Sigg3.net · · Score: 1

      They want free stuff, it's not rocket science.

      There's always one person making a riot because his pirated, Russian XP isn't working "as advertised" and want a genuine version free of charge, because he "knows" IT people gets it for free.
      Usually screaming at the top of his lungs.

    103. Re:no by hughperkins · · Score: 1

      Check out Nic's password generator: http://angel.net/~nic/passwd.current.html

      I extended it a bit https://github.com/hughperkins/passwordbookmarklet :
      - longer passwords generated
      - the bookmarklet password field uses password characters
      - there's the option of using a bookmarklet with a 'confirm' field
      - added a console application (python) which invisibly copies the password to the clipboard, for non-web applications

    104. Re:no by darkonc · · Score: 1
      No problem with code signing, per se. Big problem with using Code signing to lock in market control and limit people's control of their own machine. -- Especilly the signatures are controlled by a company with an abysmal history of code security.

      Microsoft-controlled code-signing is like putting 3 bulky padlocks on a house with big, open windows.

      --
      Sometimes boldness is in fashion. Sometimes only the brave will be bold.
    105. Re:no by Anonymous Coward · · Score: 0

      Someone went to SEC+

    106. Re:no by Anonymous Coward · · Score: 0

      Except that when nothing is ever in plaintext, good encryption means good protection. If you have client-side encryption and upload everything crypted, your data is relatively safe even on a server run by the usual idiots/snitches. Of course you still have to make sure that whenever you do decrypt the data, it is in a safe, trusted environment.

    107. Re:no by Anonymous Coward · · Score: 0

      Use keepass in combination with dropbox. You should have all your.passwords with you everywhere on your phone. All encrypted of course

    108. Re:no by Anonymous Coward · · Score: 0

      You mean, you can't rebuild it? You can't make it better, stronger, faster? You don't have the technology?

    109. Re:no by GuB-42 · · Score: 1

      Considering how much crap uninformed users tend to install just to ask their their more knowledgeable friends to fix their mess, I don't think that putting a small barrier is a bad thing.

  3. Dress for suck-(cess) by Anonymous Coward · · Score: 1

    My vote is for just giving up and letting the bad guys have their way with us.

    1. Re:Dress for suck-(cess) by Anonymous Coward · · Score: 1

      You mean business as usual for a lot of companies? I've heard the adage, "security has no ROI" way too many times... with its companion, "Tata or Geek Squad can fix anything."

    2. Re:Dress for suck-(cess) by eksith · · Score: 1

      No... long answer, no way in hell and you can take my PGP from cold dead hands.

      --
      If computers were people, I'd be a misanthrope.
    3. Re:Dress for suck-(cess) by vux984 · · Score: 5, Informative

      His point wasn't that cryptography wasn't useful, but simply that dealing with modern threats doesn't require "better cryptography" because modern threats aren't attacking the crypto. They are attacking the public key infrastructure (PKI), they are attacking the end points before encryption/after decryption.

      Our security focus is there.
      In other words, PGP doesn't protect your email, if you have a virus on your system sending everything to an attacker after its decrypted. PGP doesn't protect your email if the PKI is hacked, and you are signing mail with public keys generated by people impersonating the intended recipients.

      Etc. Etc.

      A better PGP crypto algorithm isn't going to help you here.

    4. Re:Dress for suck-(cess) by mhajicek · · Score: 1

      Security has no ROI, but a lack thereof has a negative ROI. It may be better received if called "loss prevention".

    5. Re:Dress for suck-(cess) by viperidaenz · · Score: 1

      I don't need to take your PGP, I just need to take your private key.

    6. Re:Dress for suck-(cess) by viperidaenz · · Score: 1

      Tatas fix a lot of things, but security isn't one of them.

    7. Re:Dress for suck-(cess) by Anonymous Coward · · Score: 0

      Ah so you run windows, then.

    8. Re:Dress for suck-(cess) by tsotha · · Score: 2

      I have never run across a company that wasn't serious about security. The problem has always been keeping people out takes a different skill set and a different mindset than building things. Companies I've worked for had their systems compromised because they didn't understand the nature of the threat, not because it didn't have "ROI". By now I think most companies realize a bad hacking incident can be an existential threat to a product line or even the company itself.

      My current employer hands over tons of cash to a consulting firm that specializes in this sort of thing. As much as I think using consultants is usually a waste of money, in this case it probably makes sense.

      Personally I'd like to take the Neuromancer route and have a corporate hit squad run these fuckers down and shoot them (katanas would be good, too), but my boss won't go for it. Something about liability. Pffft.

    9. Re:Dress for suck-(cess) by heypete · · Score: 1

      I don't need to take your PGP, I just need to take your private key.

      Considering that my PGP key exists on a tamper-resistant smartcard specifically to prevent that type of attack, that would be impressive.

      Sure, one could apply the old rubber hose or steal the smartcard and extract the data from the chip but that seems a bit extreme.

    10. Re:Dress for suck-(cess) by Anonymous Coward · · Score: 1

      There is a limit to what you can do to secure the endpoints, but the PKI can be improved upon in certain situations.

      As an example, bitmessage (a bitcoin-inspired messaging application) and cjdns (a mesh routing engine) both follow basically the same idea: derive your address from your public key. In applications where this makes sense to do, it eliminates the need for a hackable PKI--keys can be distributed with little thought to security, because the validity of each key can be (and is) checked by everyone.

      Admittedly, the result in the above cases is that you get something which looks like a bitcoin address for bitmessage, and an fc00::/8 ipv6 address for cjdns. Not the most user friendly things to work with, and adding a human-readable version (something like a DNS lookup table) reintroduces a lot of the problems. But it's a start.

    11. Re:Dress for suck-(cess) by TCM · · Score: 1

      Just because there are weaker links doesn't mean stronger links should stop getting stronger or even become weaker.

      No idea WTF the author is smoking. Must be one of those post-privacy pussies, too, who just give up.

      --
      Of course it runs NetBSD. BTC: 1NT7QvbetmANwaMzhpVL6
    12. Re:Dress for suck-(cess) by viperidaenz · · Score: 1

      So you only ever use computers you own that haven't been infected with malware and never use a smartphone or tablet because they don't have smart card readers? Awesome case of paranoia you have there.

      If your paranoia is justified though, there's always this method.

    13. Re:Dress for suck-(cess) by heypete · · Score: 1

      So you only ever use computers you own that haven't been infected with malware and never use a smartphone or tablet because they don't have smart card readers? Awesome case of paranoia you have there.

      When I use PGP, absolutely.

      It's not paranoia, it's common sense: why would anyone use a potentially-untrustworthy system when dealing with secure communications? I also don't check my banking records from potentially-untrustworthy systems. Is that paranoid?

      In regards to tablets and smartphones, I haven't really found any that pique my interest. I prefer more standard computers and a relatively basic mobile phone.

      If your paranoia is justified though, there's always this method.

      Indeed. That is not the threat model I'm worried about -- I have no illusions about securing communications from major world governments that have a personal interest in reading them and who are willing to use force in pursuit of that goal. I'm more concerned about more mundane, everyday threats like malware. Using a smartcard provides effective protection against such threats.

  4. APT by Anonymous Coward · · Score: 5, Insightful

    Would have been nice to define APT...

    1. Re:APT by Dizzer · · Score: 5, Informative

      Advanced Persistent Threat

    2. Re:APT by Nerdfest · · Score: 1

      I'm guessing "Advanced Persistent Threat", but I may be wrong. Yes, It would have been nice to define it at first use.

    3. Re:APT by Frosty+Piss · · Score: 5, Informative
      --
      If you want news from today, you have to come back tomorrow.
    4. Re:APT by Omnifarious · · Score: 2

      I agree. Making it an acronym makes an annoying piece of jargon slightly inscrutable for people who aren't conversant with the field. APT in this case refers to Advanced Persistent Threat.

    5. Re:APT by fuzzyfuzzyfungus · · Score: 4, Insightful

      It's doubly annoying because(in PR-flack ass-covering speak) an "Advanced Persistent Threat" is "Any bad guy smarter than our dumbest sysadmin's stupidest mistake".

      It might have been a clear category at one point(and there still are attackers who are pretty clearly both advanced and persistent); but the constant "Well, we could say 'gosh, we fucked up, how stupid of us.' or we could say 'It was and Advanced Persistent Threat, total national security shit, probably chinamen or something!'" pressure hasn't helped...

    6. Re:APT by obarthelemy · · Score: 4, Insightful

      Actually, I know plenty of intelligent people who make mistakes. Almost as many as retards who take pleasure in calling others out.

      --
      The Cloud - because you don't care if your apps and data are up in the air.
    7. Re:APT by Anonymous Coward · · Score: 1

      "APT-get" is a well known tool available to Debian users for upgrading all the advanced, persistant and threatening installed packages on their pc.

    8. Re:APT by Score+Whore · · Score: 5, Funny

      Always Perky Titties. The thing is the nerds in IT are easily distracted by some nice sweater stretchers which enables the bad guys to have their way with the servers while the boobs are bouncing around.

    9. Re:APT by the_B0fh · · Score: 1

      damn, I wish I hadn't commented previously!

    10. Re:APT by kangsterizer · · Score: 1

      To be honest, it's a cool new word to say you've been massively rootkited by humans :P

    11. Re:APT by Anonymous Coward · · Score: 0

      My first thought is always that you shouldn't apt-get install threats.

    12. Re:APT by Anonymous Coward · · Score: 0

      I've seen many times on ./ that people who made remarks about acronyms or jargon like you did were treated as if they were stupid for not knowing it or lazy for not looking it up themselves. It's very refreshing to see you only got positive remarks so far.

    13. Re:APT by Anonymous Coward · · Score: 0

      Indeed, it would have been very apt to do that.

    14. Re:APT by bentcd · · Score: 2

      Advanced Persistent Threat

      Damn, that puts a whole new perspective on apt-get ...

      --
      sigs are hazardous to your health
    15. Re:APT by L4t3r4lu5 · · Score: 1

      Actually, I know plenty of intelligent people who make mistakes. Almost as many as retards who take pleasure in calling others out.

      This was ironically recursive, right?

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    16. Re:APT by Sigg3.net · · Score: 1

      # apt-get remove apt

      Problem solved!

    17. Re:APT by peawormsworth · · Score: 1

      Would have been nice to define APT...

      From this content, it is apparent that the original submitter did not know what ATP meant at the time of submission. Because the quoted article doesnt define it either.

    18. Re:APT by Anonymous Coward · · Score: 0

      Ah those wonderful times when "almost" doesn't mean almost. And the stupid idiot wouldn't even know what systeman admin is or does. So yeah troll more, idiot.

  5. Depends on your threat model by Omnifarious · · Score: 3, Informative

    If you're trying to protect your big organization against foreign spies, yes. If you are a little guy who wants to communicate without having that communication be laid wide open for a large organization to see, then I think encryption is still pretty useful. Even if just because managing all those separate unique intrusions over a long period of time requires a lot more resources than just tapping into a trunk line.

    1. Re:Depends on your threat model by Anonymous Coward · · Score: 1

      If you're trying to protect your big organization against foreign spies, yes.

      It's still useful and important. Not foolproof, but useful and important.

  6. The way I do security by Anonymous Coward · · Score: 5, Interesting

    I have a PC that I use for all of my financial stuff, record keeping, and other critical data. I don't encrypt the hard drive. I don't even password protect files.

    You know how I do security for the PC that handles my most critical data?

    It's not plugged into the fucking Internet. That's how.

    1. Re:The way I do security by masternerdguy · · Score: 5, Insightful

      Have fun when Joe the Burgler takes your computer.

      --
      To offset political mods, replace Flamebait with Insightful.
    2. Re:The way I do security by godel_56 · · Score: 0, Redundant

      I have a PC that I use for all of my financial stuff, record keeping, and other critical data. I don't encrypt the hard drive. I don't even password protect files.

      You know how I do security for the PC that handles my most critical data?

      It's not plugged into the fucking Internet. That's how.

      And wha

    3. Re:The way I do security by godel_56 · · Score: 2

      I have a PC that I use for all of my financial stuff, record keeping, and other critical data. I don't encrypt the hard drive. I don't even password protect files.

      You know how I do security for the PC that handles my most critical data?

      It's not plugged into the fucking Internet. That's how.

      And what do you rely on if your computer gets stolen? How about if your computer suddenly craps out and you have to take it in for repair, and the repair shop has full access to all your files as soon as the power supply is fixed?

    4. Re:The way I do security by CRCulver · · Score: 2

      If you move records from an internet-connected computer to this isolated computer via a removable drive, you may still be susceptible to attack. After all, Stuxnet and other viruses have spread this way. Viruses were already a problem for PC users long before network-connected device. And even if the computer is totally isolated from both networks and USB drives, the data can still be compromised through a TEMPEST attack (assuming you were a target for a state or especially savvy organized crime network).

    5. Re:The way I do security by swilde23 · · Score: 3, Insightful

      I think what most of the people responding to this post aren't realizing (or acknowledging) is that your security needs to be appropriate for the data it's protecting.

      If we're talking about a corporations backbone, then yeah saying "it's not connected to the internet" isn't acceptable.

      If instead we're talking about some John Doe's personal data, then you aren't going to be attacked in the same way. Keeping it on a drive that has no internet access is probably good enough.

      --
      There are 10 types of people in the world. Those that understand this sig, and those that beat up people who do.
    6. Re:The way I do security by Anonymous Coward · · Score: 0

      People still take their computers to repair shops? Everyone I know either fixes it themselves or they just buy a new one.

      In any case, there's no reason you couldn't just take your hard drive out and throw in an empty spare drive before taking it to the shop.

    7. Re:The way I do security by masternerdguy · · Score: 1

      I fix the computers of friends and co workers all the time.

      --
      To offset political mods, replace Flamebait with Insightful.
    8. Re:The way I do security by cffrost · · Score: 2

      How about if your computer suddenly craps out and you have to take it in for repair, and the repair shop has full access to all your files as soon as the power supply is fixed?

      Why would somebody (particularly somebody who posts on Slashdot) haul the entire machine to a repair shop to replace a dead PSU? Five minutes with a Phillips-head screwdriver and a replacement PSU — done.

      --
      Thank you, Edward Snowden.

      "Arguments from authority are worthless." —Carl Sagan
    9. Re:The way I do security by jythie · · Score: 1

      Not only that, but people are not really taking the APT element into account. The security that is appropriate for a computer siting around that no one knows about is pretty different from the security useful for when you have a targeted attack by a motivated entity. Even if you are just some random individual, a persistant attacker would probably do things like break into your house...

    10. Re:The way I do security by Anonymous Coward · · Score: 0

      Why would somebody (particularly somebody who posts on Slashdot) haul the entire machine to a repair shop to replace a dead PSU?

      Because a lot of people have no inkling of what they're doing and, to these people, computers are just magic boxes.

    11. Re:The way I do security by dbIII · · Score: 1

      People don't remove their drives that contain sensitive information before sending them in for repair? You are right, some people don't know any better, but the sort of people that are interested in this discussion would know that full physical access means being able to get to anything on the machine.

    12. Re:The way I do security by Anonymous Coward · · Score: 0

      Why would somebody (particularly somebody who posts on Slashdot) haul the entire machine to a repair shop to replace a dead PSU?

      Is the answer to that question not completely obvious? Taking my mother as an example, she couldn't figure out how to operate a web browser if people didn't email her URLs. She can knit an awesome scarf and cook an incredible meal, and 50 years ago she could assist a doctor in open heart surgery, but I don't think she can even set the time on her own watch.

    13. Re:The way I do security by L4t3r4lu5 · · Score: 1

      Ladies and gentleman, I present a quintessential example of the disconnect between "us" and "them".

      My grandfather designed fuel line systems for Rolls Royce in his youth; His engineering knowledge is staggering. However, I know for a fact that he hasn't got the faintest idea what a Molex connector is, and why his three year old HP PC likely doesn't need any.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    14. Re:The way I do security by Anonymous Coward · · Score: 0

      Oh, don't worry about Joe, he's just the plumber.

  7. Translation: by gman003 · · Score: 3, Insightful

    Encryption doesn't do shit if they're grabbing it before encryption or after decryption. It's not a magic security bullet. It has its uses, but now it's become easier for Eve to hack Alice and read the plaintext than to intercept and brute-force the ciphertext. And when Alice is talking to not just Bob, but Carol and Dave, well, that makes Alice a high-value target worth spending time on.

    1. Re:Translation: by Anonymous Coward · · Score: 0

      Encryption doesn't do shit if they're grabbing it before encryption or after decryption

      That's like saying porcelain bowls don't do shit if you shit your pants. The fact is, it does do shit, just not where you did it. That's by design btw.

    2. Re:Translation: by dbIII · · Score: 2

      As an example of the above, the disturbing trend of using proxies on encrypted web traffic is opening a lot of people up for a full man in the middle attack where encryption doesn't matter. When people start getting used to accepting certs for a proxy they can be more easily tricked into passing things through a rogue proxy that is put in place for harvesting credit card details or whatever. Combine it with an open wireless access point in a busy area, or spoofed SSIDs for a more targeted approach, and you've conned a pile of people that think they know a lot about computers and think they are doing the right thing.
      Also whatever criminal manages to crack a legitimate https proxy stands to gain a lot. It's only a matter of time because do you really think anyone that implements such a stupid idea is going to put in enough attention to detail to do it properly?

    3. Re:Translation: by Anonymous Coward · · Score: 0

      Your point seems to be that encryption isn't a magic bullet because it is too successful, prompting attackers to just give up on attacking it and instead slink around the sides to see if they can find another way of getting in. A reinforced door that caused your attacker to go in through through the window didn't fail - it succeeded. Your security failed, but that's something else.

  8. Understandable by Anonymous Coward · · Score: 1

    In a world where cryptography gets used for DRM purposes, it is not surprising to think that someone would say it was "becoming less important".
    If you understand cryptography, you know that the opposite is true: It is absolutely essential and therefore extremely important.
    It is not a silver bullet designed to kill every security problem; nothing ever will be. That doesn't mean it's not important.

  9. perhaps differently put by ewertz · · Score: 2

    Perhaps it's really just that encryption is a lesser part of the total solution, so in that respect, it's relatively less important than it used to be.

    Now get that meat off of my cyberlawn!

  10. Security was never about encryption by qbitslayer · · Score: 4, Interesting

    The use of encryption is only intended to provide a way for legitimate remote users to gain supervised access to the system without having to hack into it. The real culprit behind bad security is software reliability. Attackers look for and try to exploit the defects in the software. Why is software defective? Because (it's the bugs, stupid!) the Turing/Von Neumann model of computing is inherently insecure and unreliable. Why? Because timing is not an essential part of the model. I predict that this decade will see the end of the Turing madness and that the future of computing is non-algorithmic. There is no alternative and the sooner, the better.

    1. Re:Security was never about encryption by hamster_nz · · Score: 1

      I've read the links, and that is an awfully long bow to draw.

      The use of encryption is to try and limit information to those that are intended to see it.

      None of the ideas on your blogs address how to "end the Turing madness" in a way that will still allow you to post on Slashdot.

    2. Re:Security was never about encryption by qbitslayer · · Score: 1

      None of the ideas on your blogs address how to "end the Turing madness" in a way that will still allow you to post on Slashdot.

      I disagree but, just in case you missed it, read How to Solve the Parallel Programming Crisis.

    3. Re:Security was never about encryption by DamnStupidElf · · Score: 1

      Non-algorithmic computing won't keep authentication, authorization, or privilege escalation bugs from happening. It won't prevent side-channel attacks or social engineering. It won't provide automatic segregation and compartmentalization of data. All the major problems we have today will still exist; they'll just happen synchronously.

      What you should actually look into is formally verifiable software design where the model of computation and data representation can be formally analyzed and every program can be proven to adhere to a security policy that enforces capability-based access to data and resources, limited access to timing information to prevent remote timing attacks, fine-grained authentication and authorization directly tied to capabilities, and a formal proof verifier that can check the entire system from the BIOS to the running applications every time you turn the computer on. Forget trusted computing; we need provable computing.

    4. Re:Security was never about encryption by hamster_nz · · Score: 1

      If you truly believe that then you should get an FPGA development kit and start your revolution. The are excellent at evolving a large state vector over time,

      A large FPGA may have 2.5 megabits of state and clock rates of 500MHz, so you can update over 1,000,000,000,000,000 bits of state every second - about 1000 times what a CPU can do., They also have 300 pins of I/O, and a dozen interfaces of > 10Gb/s and the logic transform can be dynamically reprogrammed. Oh, can have 5,000 GigaMACs (multiply + accumulates per second) - about 4,000x that of a CPU core.

      Maybe get yourself a small one - small development boards are under $100. Have a go - let me know how you get on. The same board can implement a system equivalent to a 486 CPU - 32 bits, 100MHz. Should be enough to get started with.

    5. Re:Security was never about encryption by Anonymous Coward · · Score: 0

      Computers are too difficult to configure, that is what is the problem. It allows a service to be provided that should not be active (e.g. insmod). You rarely need that but nobody removed the service (being able to call insmod). Hacking will always take place but afterward you have a resource you can do so much more with. In general one starts to weave a web to see if anyone does things that the system should not do. That is only an afterthought.

    6. Re:Security was never about encryption by steelfood · · Score: 1

      I'm not sure that's possible. Humans think linearly. We're horrible at multitasking, and that applies to both sexes. The point of attack is still going to be the human interface, which is going to be linear.

      You can theoretically use this idea to harden the software and hardware down all you want (though I'm not sure how you'd do that on a circuit level because electrical signals are processed linearly unless you outright move away from electrical signals and into something with more dimensions like chemical signals), but you can't remove the human element from computer security.

      The tradeoff, as is the same in the non-electronic world, is between convenience and security. Most people aren't willing to trade a significant portion of their convenience for securing their data. It's a cost-benefit thing. You can actually calculate the amount of time spent being inconvenient and if it's more than what the data is worth as a secret, then it's not a practical security model. And most of the time, the data is worth less than the cost of the security around it.

      --
      "If a nation expects to be ignorant and free in a state of civilization, it expects what never was and never will be."
    7. Re:Security was never about encryption by Raenex · · Score: 1

      The use of encryption is only intended to provide a way for legitimate remote users to gain supervised access to the system without having to hack into it. The real culprit behind bad security is software reliability.

      Encryption is used to send a message from A to B across an insecure network. Other uses are to prevent someone from getting access to stored data, such as on a portable flash drive. This has nothing to do with software reliability. Not acknowledging such basic facts makes you a crank.

  11. This guy by Anonymous Coward · · Score: 0

    hates bitcoin.

  12. certificates by manu0601 · · Score: 3, Insightful

    From TFA

    One way to help shore up defenses would be to improve--or replace--the existing certificate authority infrastructure, the panelists said

    Indeed. IMO SSL public keys could be stored in DNSsec protected DNS records. That way one would only have to trust the manager of the root zone and the TLD, which would be a good improvement compared to the CA debacle.

    1. Re:certificates by Lorens · · Score: 1

      Indeed. IMO SSL public keys could be stored in DNSsec protected DNS records. That way one would only have to trust the manager of the root zone and the TLD, which would be a good improvement compared to the CA debacle.

      Right, and when you buy example.com you should be able to sign certs for whatever.example.com for free.

    2. Re:certificates by manu0601 · · Score: 1

      Exactly, plus the ability to roll a new key with no delay.

  13. Re:Write better code!!! by Anonymous Coward · · Score: 0

    kids who who have hacked the kernel were self-motivated/taught.

    These are the only ones that the industry needs. The rest can fuck right off. It won't help to teach kids programming (shit I mean coding, nobody programs anything anymore)if they aren't interested. They will do the laziest shit they can get away with, and it won't matter what language you use the better idiot will be born. The age of the App is upon us. Have fun with all these lil' coders that don't know they didn't program shit and they are just using templates and can't even debug AT ALL because "the compiler won't let me make a mistake."
    I just hope nobody wonders why most of their computers resources are devoted to error correction. It's fucking obvious now.

  14. Wasted CPU cycles by Anonymous Coward · · Score: 0

    If you really want to protect your network, disconnect it from the internet. Encryption should be used to prevent sniffing or try to stop it anyways, in the intranet as a secondary defense. If you actually need the internet, you should have 2 networks, one with your internet facing servers, then a firewall allowing very specific access to the intranet network and heavy monitoring.

  15. Active Defense System by wakeboarder · · Score: 2

    Why can't you build a system to monitor and defend against attacks? Once a virus gains control of your system it is quite easy to find and remove based on file signatures (time installed,ect). If you know what you have and something changes you should be able to identify it. It would be easy to identify attacks on a network when things go outside the norm. "Well, lets see somebody opened up a bunch of ports and is transferring files to some random IP in X country that isn't on my list of recently accessed http sites, I think I'll shut those down. Oh, a user is downloading 20% more classified files than normal users, maybe we should pay him a visit and shut down his access until we figure out what is going on. Implementing such a system would be difficult, but patterns should be statistical and you should be able to see most of what goes on. Yes people could slip through the cracks, but if you develop a good model, you should be able to spot the differences between malicious and normal behavior.

    1. Re:Active Defense System by Anonymous Coward · · Score: 0

      Well, that is exactly what they already do. You also need to MITM the encrypted connections so that you can inspect the traffic. Or disallow encryption to everybody in the first place and then add exception according to real business needs.

      Otherwise the bad guys can use Google Mail and the like to exfiltrate massive data sets.

  16. relative by e**(i+pi)-1 · · Score: 0
    The quote was clearly understood "relative to other measures". Besides that one has to keep in mind that the top experts are often wrong. Look at some quotes:
    • Everything that can be invented has been invented
    • Who wants to hear actors talk?
    • There is no reason anyone would want a computer in their home.
    • The bomb will never go off. I speak as an expert in explosives.
  17. Encryption doesn't protect you by elucido · · Score: 1

    so if you know the information the enemy will find out through you.

  18. Legal system threats by gmuslera · · Score: 1, Troll

    Another reason that it could become less important is if the zone becomes a patent minefield. Maybe math is not patentable, or shouldn't be (but even natural genes get patented) but there are enough borders around it that could be used as excuse that could be a tool to force only the use of "approved" encryption methods.

  19. Is he saying about all uses of cryptography? by osoriojr · · Score: 2

    Governments are trying to follow all our steps over the internet, intercepting and parsing everything we do. Encrypting our communications and trying to encrypt everything is the secure method to make the Internet freedom to us all.

    1. Re:Is he saying about all uses of cryptography? by compro01 · · Score: 2

      What's he's saying is encryption doesn't matter if there's shit in the system grabbing your stuff before the encryption or after the decryption.

      --
      upon the advice of my lawyer, i have no sig at this time
  20. He's probably just fed up. by Animats · · Score: 4, Interesting

    I suspect he's just fed up with the state of software security, which is appallingly bad. We now have patch-and-release on everything. This turns out to be a failed strategy against competent attackers.

    I used to work on secure microkernels in the 1980s. I thought that by now we'd have provably secure microkernels in ROM with a mandatory security model enforced. Systems like that have been built a few times for the three-letter agencies, but never went mainstream. Instead, we have bloated operating systems with a high churn rate, and far too much trusted software per system.

    Ballmer used to call this "strategic complexity". As Ballmer once put it, when asked why Microsoft kept adding functions to Windows, "If we stopped adding functions to Windows, it would become a commodity, like a BIOS. And Microsoft is not in the BIOS business".

    Most applications should be running with far less privileges than they have. But if they are locked down properly, their ad tracking, update checking, and self-modification won't work. The user would actually be in charge.

    Cryptography only provides a secure way to communicate between secure regions. If there are few or no secure regions, it doesn't help much.

    1. Re:He's probably just fed up. by IamTheRealMike · · Score: 1

      Secure microkernels in ROM with mandatory enforced security models did go mainstream, actually. Hundreds of millions of people have one in their living room, it's called a games console and they have a pretty enviable track record of being difficult to hack even by extremely competent attackers who have physical access to the machine. The sad thing is that despite Microsoft having a lot of in-house expertise in how to build these kinds of system, they deployed exactly none of it to build secure business workstations, instead that's been left to Google with ChromeOS which (you guessed it) is made up of layers of sandboxes with a secure ROM that integrity checks the next level up before running it. If you disable extensions, which I think admins can do remotely for managed domains, it's proven extremely difficult to penetrate.

  21. Article leaves out some steps... by khb · · Score: 1

    Upon reflection, and not surprisingly, the expert has made a good point.

    If due to an Advanced Persistent Threat (APT), your secret data was captured after it was decoded (as it must be to be actively used, or created, or transferred, at some point) or if the private keys are compromised (either due to torture, pressure on appropriate authorities, or captured as created (see above)) the benefit(s) of encryption are greatly reduced (even if the cryptosystem itself is very secure).

    It is a bit of a chilling thought, and yes other posters have pointed to various good zones of defense, but Shamir's point is that some existing APTs in the wild have penetrated to the deepest levels.

    As for the "air gap" method, as has been pointed out in other places, that's often compromised even for very secure infrastructures by people with laptops, cellphones, or compromised printers that are moved from one side of the "air gap" to the other....

  22. Yes, because ... by dbIII · · Score: 1

    The problem as I see it is that not enough people actually care so it doesn't get used when it should. Other options that are not quite as good but you can actually get people to use are worth a try. Even military intelligence aerial camera footage gets sent in the clear in real time using publicly available codecs for anyone tuned to the right frequency for hundreds of miles to pick up. Trivial encryption is seen as just too much of a hassle. It's not seen as important.

  23. I do not agree! by endus · · Score: 4, Insightful

    I was just having a discussion about this at work today. Encryption should be ubiquitous now. There is no excuse. It's not "free" in terms of the resources it takes up, but it's pretty close. Everything should be encrypted in transit. Everything should be encrypted at rest. "Well you mean the table with the PII and not...." NO! I mean EVERYTHING. The servers drive should be encrypted. The entire database should be encrypted. Every network connection should be encrypted.

    This doesn't mean encryption is a panacea solution to APTs or to any other security threat, but its an absolutely critical layer which is still not widely implemented enough. To prevent tampering, to prevent certain types of attacks, to prevent breaches through physical theft, etc. Saying encryption isn't as important anymore is like saying that keyboards aren't that important anymore. Sure, management shouldn't spend a lot of time worrying about them, and should be focusing on other problems instead....but that doesn't mean everything will be cool if everyone's keyboard is stolen overnight.

    It needs to be there, and by there I mean everywhere. And its not. Every day developers are looking at security guys like, "huh??" because they are looking for encryption to be incorporated into the product. Or, they want to "just get the system built out" without encryption, but they'll totally enable it once everything is working perfectly and all the testing is done (FYI developers, security guys aren't falling for that, we realize that you really mean, 'we'll think about enabling it until we realize how many things it will break, and then we'll ship the product without it, ignoring the enormous liability it creates'). You would think things would be different now that its 2013...they are different, but not that much different. Security still isn't regarded as a core piece, or even an important feature, of most products.

    1. Re:I do not agree! by DigitAl56K · · Score: 3, Insightful

      I am a proponent for more widescale use of encryption, but I am against braindead application of it as you seem to advocate for. As has been called out time and time again, the application of the encryption is critically important to it fulfilling its role. It's easy to get it so wrong in practice that all you provide your users is a false sense of security that encourages them to put more highly sensitive material than they otherwise would have at risk. Then there are other considerations. Once you bring encryption into the fold on every single aspect of your product, how easy is it to test and debug? Is your time to market now twice as long because you have to develop special QA tools rath than use something off the shelf? Is the data actually sensitive? What are these "tampering" and "certain types of attacks" that this encryption is going to protect against? Do you and your team actually understand what they are? If you don't, how do you know the encryption scheme you're using protects against them? What about export restrictions? Where does your product need to be distributed? Does your encryption help at all if your servers are rooted, since they can presumably decrypt all the data anyway? Is the encryption giving you a false sense of security around your customers data? If everything your product does is encrypted, are your customers going to be happy about their ability to implement compatible products? How can customers trust and validate your product if they can't see how it works?

      "Encrypt everything" isn't a very well thought-out plan.

    2. Re:I do not agree! by IamTheRealMike · · Score: 1

      Encryption is not in any way "free". The calculations might be fast but the complexity of the key distribution and management infrastructures are never free.

    3. Re:I do not agree! by FireFury03 · · Score: 3, Insightful

      The servers drive should be encrypted. The entire database should be encrypted.

      Its not so simple. A server requires the drive to be mounted (and therefore decryptable) in order to function. So from the time the server is powered up until the time it is powered down, the file system is vulnerable - for a server that is powered on all the time, this means the window of opportunity for an attacker is huge. It stops a burglar from getting at the data after they unplug the machine and walk off with it, but if your server is in a secure datacentre then this isn't such a big worry - the concern is the server being compromised *while its running* (and as mentioned, servers tend to be running all the time). This could happen either by a remote attack, or by someone physically accessing the machine. So really, for an always-on server there often isn't a lot of point in encrypting it. Add to this that, unless you want to store the encryption key on the server itself (which rather defeats the point), you need to manually load it every time the server boots, which isn't great for failure resilliance.

      And especially for I/O heavy servers (frequently the case with big DB servers), encryption is *not* free - it can have a significant performance hit.

      There are places where filesystem encyption on servers makes sense - this is where the encrypted filesystems are only mounted for brief periods of time. For example, a server that is performing remote backups of another server can retrieve the key from the machine its backing up, mount the FS, do the backup, unmount the FS and wipe the local copy of the key. The window of opportunity for an attacker is relatively short there (the duration of the backup); although obviously if an attacker can load persistent malware on the machine they can have it capture the key when the backup next starts.

    4. Re:I do not agree! by indymike · · Score: 3, Informative

      Security isn't a "core piece" because it is a pain in the ass for everyone but security people and easy to defeat most of the time. If you get root, collecting keys and salt for secure hashes becomes a lot easier. A good example is DRM - almost every crack comes from extracting keys. Most of the time, when you think encryption, your time would be better invested in say, keeping software up to date, auditing user permissions and doing other basic things that actually do have a big impact on real security. Almost every security choice is a trade between secure and easy to use. Magic solutions that claim somehow make everything secure often are not magic and not very secure. The let's encrypt everything concept is a virus of the mind - it sounds good, but in application is often riddled with a combination of bugs, assumptions and mistakes that result in big holes and big bills from security consultants. Oh, and with encryption you also inject a probability of data loss... some idiot losing a key is more of a threat that unauthorized access.

      --
      -- Mike
    5. Re:I do not agree! by Anonymous Coward · · Score: 0

      > It's easy to get it so wrong in practice that all you provide your users is a false sense of security

      Blablabla. It's exactly that mindset, that has done more than anything else I can think of to PREVENT encryption and other such technologies from ever being actively considered by users. "If I can't do it right, I might as well save myself the hassle". And they're, as much as it hurts to say, completely right!

      rSa is right...crypto is merely a part of an overall security approach. It's not, and was never meant to be, the end-all, be-all. Yet if you look at any kind of documentation or forums, you will find pages and pages of ominous warnings about everything that could go wrong, usually based on the notion of not destroying some obscure "sense of security" on part of the user, which is utter bullshit because it mostly doesn't exist. As it is, browsers don't even have the famous lock icon anymore, which alone took years of attempts to "teach" users to look for it, nevermind the fact, that 99.9% percent of user-relevant interactions are plain-text...and stored in Utah.

      So what rSa really is saying, I think, is not that crypto itself is less and less important per se, but that it FINALLY loses its totally overrated sense of importance in the overall picture of wrong-from-the-get-go black and white approaches. Reality, in a bad way, has set in, broke in, and is demolishing the 'total security or nothing at all' nonsense.

      We need hybrid approaches, that make security a default, but in various levels clearly visible and electable by the user(s). This can go from 0 (plain-text all the way) to (close to) 100% security. Those who rather have no crypto than a half-way approach can turn it all the way down, if they choose to. I think, it'd be stupid, but hey... Likewise, those who want close to 100% can go all the way with it...akin to enabling "advanced" menus in various programs. By default, opportunistic encryption should be enabled at some decent, non-intrusive level and thus: Joy for everyone! :-)

      This, of course, does not eliminate the issue of side-channel leaks or attacks. It was never meant to be! PGP, back in the day, did also nothing about the camera in your ceiling fan. That's why it's part of an overall concept, that the user him/herself needs to determine the depth and extent of, that's appropriate and doable. And crypto certainly has a major part in that...if user-friendly implemented.

    6. Re:I do not agree! by endus · · Score: 2

      "Getting it wrong" in the implementation stage is a function of developers not viewing security as part of their job. I'm not saying that we can eliminate mistakes and develop perfect code every time, but you have to try. The more experience developers get with implementing it and the more universal it becomes, the fewer mistakes they're going to make when implementing it. Right now, it seems to be regarded as a novelty by most developers.

      I don't buy the "false sense of security" argument at all, sorry. If it's not encrypted I can absolutely guarantee its not secure. If it's encrypted then at least that's one layer of protection to help mitigate issues at the many other layers they can occur.

      I also don't buy that implementing encryption is going to double your time to market. That's another excuse used because the initial impact is large, but as developers gain experience with it the impact will be reduced.

      Here's the thing with your other questions. When the product gets built, maybe the information isn't sensitive or regulated. It will be, though. This will happen either by the regs changing, because of new customer requirements, or because the scope of what the product is handling will increase. I see it every day. Developers don't seem to get eyes on the questionnaires that security gets from customers too often, but they should. Customers are asking VERY detailed security questions now and some have very very stringent requirements. So your choice is, a.) build security into the product and make it part of the value proposition or b.) wait until you get hammered by a customer and either have to reinvent the wheel in three months (or two weeks!) or, worse, lose the business. This happens over and over and over again but no one seems to understand that getting AHEAD of these requirements is going to save money in the long term.

      Export restrictions are a valid point, that one I accept.

      "If your server is rooted" is specious. If someone spearfishes an employee and gains remote access to their machine they will be able to bypass the firewall...so we shouldn't have firewalls? No, that's obviously not true. Integrity, audit, access control are critical almost no matter what data you are hosting. Even if it's not regulated data, your customers will eventually be asking.

    7. Re:I do not agree! by endus · · Score: 1

      You're right about key management. Good point.

    8. Re:I do not agree! by endus · · Score: 2

      I get the point about the I/O heavy servers.

      I don't agree with the always on server argument, though. Yes, it's not going to protect against many types of attacks, but it will protect against some and that is what's important. It's another layer. More importantly, it's a layer that is being increasingly asked for by customers whether or not any of us think it makes sense for a particular application. Building encryption in after the fact is an absolute nightmare and usually the costs and impact to production is going to be higher if you wait until you have to get it done in a month or you will lose a big deal. Better to implement it in the first place and put it in your marketing material so the question never even gets asked.

    9. Re:I do not agree! by endus · · Score: 1

      I totally agree that it doesn't solve all your problems. If your security people are telling you it does you need new security people. The problem is that keeping software up to date, auditing user permissions and doing other basic things doesn't have as big an impact as you might think.

      Well...ok...keeping software up to date does...and I can certainly write a huge diatribe about that too that will be no less universal and impassioned.

      But it's all about layers and it's all about getting ahead of regs and requirements. Turn security into a feature of the product, not something you bolt on at the last minute. The more we implement encryption universally the easier it will be for developers and the more mature key management solutions will be.

    10. Re:I do not agree! by indymike · · Score: 1

      Getting ahead of regs and requirements doesn't make anything secure. It's busywork.

      --
      -- Mike
    11. Re:I do not agree! by endus · · Score: 1

      You must be a manager to have such a negative and limited point of view. If you look at the regs from the point of view of a manager, it's a checkbox to check. If you look at it from the perspective of a security engineer it's a driver to implement legitimate controls. All the regs have fluff and vagaries, but they all also have very useful requirements and provide a stick to make the business pay for reasonable controls.

      It's also about liability. Sure, you can lie to your customers, but in addition to being unethical it means that if you have a breach you are in for a tremendous shitstorm. Comply with or, better yet, get ahead of the regs and you will be in a much stronger position to a.) not have a breach in the first place, b.) fare well in court if you do have a breach.

  24. The ideology of "ME!" by Anonymous Coward · · Score: 0

    Unfortunately for your grand plan, the owner of the code and the owner of the computer aren't the same person. Fortunately for you the owner of the computer can elect to not run code they aren't the owners of. Now whither that ideology leaves you with a useful computer is open to debate.

    1. Re:The ideology of "ME!" by Hatta · · Score: 1

      Code cannot be owned. Problem solved.

      --
      Give me Classic Slashdot or give me death!
  25. Re:Write better code!!! by Anonymous Coward · · Score: 0

    Why are there so many people who think programming is should be treated like reading, writing, and arithmetic? It would be nice if I wasn't competing with high school drop outs the next time I'm looking for a job.

  26. Obvious protection from APT by Anonymous Coward · · Score: 0

    ..just don't use apt-get.

  27. How about that? by satuon · · Score: 1

    Stop using email.

    1. Re:How about that? by Anonymous Coward · · Score: 0

      Why? Email is harmless, unless you run windows. But nobody have to. There is both a cheap DIY alternative and an expensive alternative. Neither is vulnerable to email attacks.

  28. APT? by Anonymous Coward · · Score: 0

    apt-get penetrate
    wtf is APT??

    1. Re:APT? by xenocide2 · · Score: 1

      Advanced Persistent Threat. The idea is that your threat is a state agent deliberately after you, not just the economically cheapest target (ie the one with the weakest security).

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

  29. Memory Safe Languages by Anonymous Coward · · Score: 0

    Many (not ALL, though) security issues are a direct result of using C or C++, which both do not provide Memory Safety. Java and C# could theoretically provide this (forget the implemtation issues for a second), but they are inefficient as they force a simplistic memory model onto developers. You can't have stack allocation, value object arrays, objects directly embedded into other objects and probably most importantly, you cannot control memory dealloction. As icing on the cake, you don't have synchronous destructors.

    Here is a language which aims to provide memory safety without having to compromose on efficiency:

    http://sourceforge.net/p/sappeurcompiler/code-0/2/tree/trunk/doc/SAPPEUR.pdf

    http://sourceforge.net/p/sappeurcompiler/code-0/2/tree/trunk/doc/manual.pdf

    http://sourceforge.net/projects/sappeurcompiler/

    Captcha: Anteater

  30. The REAL Problem by Anonymous Coward · · Score: 0

    ..is that a running piece of code can be subverted by means of buffer overflows, dangling pointers and so on. You don't really need to infect executable code.

    For example, imagine an exploit in SQLite. Then they virus could come in via an exploit in the Firefox or Chrome html parser and then proceed to persist itself in the SQLite database file of the browser. Each time you run the browser it will read the sqlite file (because it needs to load the bookmarks, for example) and that will restore the virus.

    All your "secure validation" claptrap will not catch this, as the executables are NOT modified.

    Memory Safe Languages such as Sappeur, Java (if the runtime is correctly done), C# could defend against against this kind of scenario in most cases.

  31. Just because THEY can doesn't me WE shouldn't by Eraesr · · Score: 2

    If there's some elite group of hackers who like to target high profile websites and services that can get past the most complex forms of encryption, then does that automatically mean we shouldn't use encryption anymore? For all I know, at the very least, encryption will keep out the 13 year old bedroom hackers who write vbscripts and call it a virus.

    Similar to me having MAC filtering enabled on my wireless router. I know MAC filtering won't keep out the determined hacker, but it will be enough of a blockade for some wannabe punk that thinks it's cool to spend a weekend trying to access insecure wifi routers. To keep out more advanced and experienced intruders, more is needed, but that's no reason for me to just open the gate to every laptop owner with half a braincell who bookmarked a "hacking 101" tutorial.

    1. Re:Just because THEY can doesn't me WE shouldn't by Anonymous Coward · · Score: 0

      The point is that encryption is almost orthogonal to other security measures in many important use cases. I can easily set up an encrypted channel to facebook. When that is done they need to have secure input parses to stop me from subverting their systems and reading/inmterferring other people's data. If they have an SQL insertion weakness, for example, I own that database. Encryption would only be of help if facebook had a small, trusted and limited user group. Obviously a no-go for Mr Zuck.

      But yeah, encryption is an important tool in the security toolbox. Like a hammer in a real toolbox. Just don't try to fix a screw with a hammer, because that is the only tool you know.

    2. Re:Just because THEY can doesn't me WE shouldn't by Sigg3.net · · Score: 1

      I used to log into unsecured Wifi network routers and change the SSID to "You need to protect your network" all caps.

      It was probably illegal but the number of unprotected networks dropped to nil. Today routers are usually protected out of the box, and the owner is legally responsible for encrypting it.

  32. APT? by Porchroof · · Score: 2

    What is APT?

    --
    Fata viam invenient.
  33. Rocking Chair philosopher by Anonymous Coward · · Score: 0

    In other words, he is saying he will be ready to retire in a couple of years. Good for him, it's hard work being a cryptographer these days, for goodness sakes!

  34. Re:Write better code!!! by Anonymous Coward · · Score: 0

    You sound like an obese monk of the 13th century bitching about commoners learning to read and write. Imagine all the "unlicensed" works of writ !!!!

  35. It's a matter of motivation by opscure · · Score: 3, Insightful

    The larger problem here is motivation of software developers, white hats, and black hats. The developers; whether it be open source or proprietary, tend to code towards a particular functionality and usually with deadlines. The white hats are preforming a job function to the best of their ability usually no more than 40-50 hours a week in teams. Whereas, the black hat is playing a game or solving a puzzle for personal enjoyment reasons. Now, I'm not saying that there is any weakness to any of the aforementioned groups, but when people do things for enjoyment, it tends to yield a higher chance of success especially when the black hat needs only to find a single point of attack in a system that largely extends from the digital realm or job functions of the software developer or the infosec ops.

    1. Re:It's a matter of motivation by Anonymous Coward · · Score: 0

      And the Programmer Pimps (aka "managers") will demand High Efficiency. There is no time to use condoms,as that would take away precious time from the programmer-whore. A smaller number of customers could be served in the same amount of time. Medical checkups would take even more time and reveal nasty truths about the Programmer Pimp's Assets.

      So, security is too expensive and we all run the uncalculated risk to acquire the Chinese AIDS. It's Business, you know !

  36. Except That by Anonymous Coward · · Score: 0

    ..you don't really need to store a virus directly inside a piece of executable code. If I have two fitting Oracle exploits and have access to the Oracle Server, I can first inject myself into the process. No useful way for you to fingerprint processes. The second exploit would be somewhere in the code which reads the records, indices and so on from mass storage. My virus would write its code inside the database or index file and not touch the executables and dlls/shared objects. Again, there is no useful way to fingerprint the database/index files and compare them with "good" fingerprints.
    Whenever you access the table/index my virus is loaded into the Oracle database server process. Booom - there goes your nice concept of "fingerprints will detect virus infection".

    We need to harden the code against exploits in the first place. Here is one approach:

    http://sourceforge.net/p/sappeurcompiler/code-0/2/tree/trunk/doc/SAPPEUR.pdf

    http://sourceforge.net/p/sappeurcompiler/code-0/2/tree/trunk/doc/manual.pdf

    http://sourceforge.net/p/sappeurcompiler/code-0/2/tree/trunk/doc/

    And no, memory safe languages DO NOT magically eliminate all security weaknesses, but they eliminate a large percentage of the worst exploits. We also need to look at practical ways of formal verification. We need to invest into "proven correct" infrastructure such as compilers, XML parsers, CSV parsers, operating systems and the like. I think only governments will do that, if anyone. Commercial companies have been an utter failure in the security arena.

  37. Anybody who sends a password in plaintext by durdur · · Score: 1

    in response to a reset request is not hashing passwords and would fail a security audit (but I have certainly seen sites like this). There is no reason for the remote site you are logging into to ever store your password, vs. storing a hash (a strong hash, repeated multiple times to make brute force reverse hashing difficult).

    1. Re:Anybody who sends a password in plaintext by demonlapin · · Score: 1

      It doesn't send my old password; it sends a replacement password - Wqu@%$ or something like that - but it sends that in plaintext.

  38. continued by Anonymous Coward · · Score: 0

    'We should rethink how we protect ourselves. Traditionally we have thought about two lines of defense. The first was to prevent the insertion of the APT with antivirus and other defenses. The second was to detect the activity of the APT once it's there. But recent history has shown us that the APT can survive both of these defenses and operate for several years.""

    ... "because executives make decisions where security is an afterthought because it impeds capitalism (or consumerism); therefore, we open our networks to webmail and social networking, and attach consumer devices in the name of progress and productivity because we don't understand basic risk calculations and feel our protections are adequate for today when we should be thinking of the possiblities of tomorrow."