Slashdot Mirror


Spoofed White House Card Dupes Many Gov't Employees, Steals Data

tsu doh nimh writes "A run-of-the-mill malware-laced e-mail that spoofed seasons greetings from The White House siphoned gigabytes of sensitive documents from dozens of victims over the holidays, including a number of government employees and contractors who work on cybersecurity matters, writes krebsonsecurity.com. The story looks at several victims who fell for the attack, and suggests it may be related to a series of similar document-harvesting runs throughout 2010. Government security vendor NetWitness notes that these types of incidents are blurring the lines between online financial fraud and espionage attacks."

173 comments

  1. Merry Christmas by Dexter+Herbivore · · Score: 5, Funny

    Honourable employees of venerable government of USA. Please click on link to receive free gift from People's Republic of... ummm... errr... Canada!

    1. Re:Merry Christmas by Toe,+The · · Score: 2

      To retrieve card just click on this totally legitimate official White House e-mail address: elvis.com.au/(something)

      Yeah, that address actually appears in the card, according to TFA.

      Like... seriously?

    2. Re:Merry Christmas by Anonymous Coward · · Score: 0

      Everyone knows the forensic analysis will point to Assange's wikileaks.

  2. Merry Freaking XMas... by Super+Dave+Osbourne · · Score: 1

    The governmint can't keep track of used hard drives, so this is not a big threat in real terms. When they can tell the US citizens where all the data for nukes and secrets is on their hard drives I'll care more about malware in emails.

    1. Re:Merry Freaking XMas... by interval1066 · · Score: 1

      :The government can't keep track of used hard drives, so this is not a big threat in real terms."

      Ok, so how about the government agency who's dept. heads were caught spending all their time in the office surfing for porn and generally goofing off last year? Were they a threat?

      --
      Python: 'And then suddenly you have a language which says "we're all stuck with whatever the whiniest coder wants".'
    2. Re:Merry Freaking XMas... by Mikkeles · · Score: 1

      No, they were a blessing! They weren't actively involved in screwing the citizenry ;^)

      --
      Great minds think alike; fools seldom differ.
  3. Hey, whatd'ya know... by Haedrian · · Score: 1

    "malware-laced e-mail"
    "contractors who work on cybersecurity "

    I guess everyone falls for a good old spoof. Not just 70 year old grandmas like it was suggested in the last article on spoofing.

    1. Re:Hey, whatd'ya know... by c6gunner · · Score: 2

      No, not at all. This just shows that there are idiots everywhere. Anyone who's ever worked in IT has had to deal with a coworker or boss who is so incompetent that they'd probably screw up a fry-chef job at McDonalds. I'm not exactly shocked that a few of them clicked a spoofed e-mail.

  4. Really? by betterunixthanunix · · Score: 1

    The people entrusted with these sensitive documents are not trained to check for digital signatures on emails that come from "the white house?" Do these people even bother to sign their messages?

    --
    Palm trees and 8
    1. Re:Really? by TaoPhoenix · · Score: 1

      Wikileaks Round 2!

      --
      My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
    2. Re:Really? by Anonymous Coward · · Score: 0

      Somebody wrote a moron detector.

    3. Re:Really? by Alumoi · · Score: 2

      Trained people do NOT get those jobs.

    4. Re:Really? by arth1 · · Score: 1

      Training has little to do with it. You need the personality traits of common sense and healthy suspicion, which no amount of training will imbue you with. At best, you can be a parrot, but won't be able to apply those traits to new and unknown situations, which is what was required here.

    5. Re:Really? by spamking · · Score: 2

      Training has little to do with it. You need the personality traits of common sense and healthy suspicion, which no amount of training will imbue you with. At best, you can be a parrot, but won't be able to apply those traits to new and unknown situations, which is what was required here.

      Bull. Training has alot to do with it. Sure some people won't "get it" and continue to do stupid stuff while on a PC at work, but to blatantly write off training is stupid. Tons of Federal employees grew up without PCs and were "trained" to use them at work. Many of these folks actually pay attention to training and react accordingly to various situations.

      However, there are those folks who will NEVER get it and continue to open up every email attachment they get regardless of who it comes from and if they're expecting it or not.

    6. Re:Really? by arth1 · · Score: 1

      However, there are those folks who will NEVER get it and continue to open up every email attachment they get regardless of who it comes from and if they're expecting it or not.

      "Who it comes from" should never be a consideration for how safe it is, both because (a) what you see is usually only a claim of who it came from, and (b) that person's machine might have been compromised, and sends out e-mails from that user's real account.

      Even "if they're expecting it" isn't a guarantee. If the user's machine has been compromised, it may very well infect outgoing e-mail attachments.

      No, common sense and healthy suspicion is needed, and there is no training that bestows either.

    7. Re:Really? by Anonymous Coward · · Score: 0

      racist.alert

  5. SSDD by Anonymous Coward · · Score: 1

    Same shit, different day. We're used to being screwed by the Obama Whitehouse.

    And the Bush II Whitehouse.

    And the Clinton Whitehouse.

    And...

    1. Re:SSDD by TaoPhoenix · · Score: 1

      Naw AC, this $hit is *Different*. It's not anything at all like the $hit you grew up with, it's a whole new paradigm!

      --
      My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
    2. Re:SSDD by Haedrian · · Score: 2

      Error: Could not find string variable 'hit'

    3. Re:SSDD by somersault · · Score: 2

      Ah thanks. I always read that as "Solid State Disk Drive". I wondered why it was a mission name in MW2.

      --
      which is totally what she said
    4. Re:SSDD by Bigbutt · · Score: 2

      And I read it as Single Sided Double Density.

      [John]

      --
      Shit better not happen!
    5. Re:SSDD by TaoPhoenix · · Score: 1

      Good one.

      It's an old joke from sites with silly profanity filters.

      --
      My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
    6. Re:SSDD by GameboyRMH · · Score: 1

      Holy crap how old are you? :P

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    7. Re:SSDD by morgan_greywolf · · Score: 1

      I read it as Single-Sided Double Density as well. I'm 38.

    8. Re:SSDD by Bigbutt · · Score: 1

      53. Been into computers since 79. A company bought the place I was programming at the first hard disk I'd ever used; a 10 megabyte seagate I think in a Leading Edge computer :)

      [John]

      --
      Shit better not happen!
  6. pack.exe as Perl/ZeuS Trojan? by AHuxley · · Score: 1

    Really silly q, but why do the scripts seem to be just so Windows based/Windows friendly?
    Is it so hard to get Mac OS X, Linux or other OS's to run something perl like via a click click of something cute in a email?
    Could anyone make something stacked/packed to be Win7/OS X/Linux aware?

    --
    Domestic spying is now "Benign Information Gathering"
    1. Re:pack.exe as Perl/ZeuS Trojan? by Haedrian · · Score: 1

      Off the top of my head I'd say that if you're executing something which you got from the internet, the executable bit will need to be turned on manually. Installing things also requires root privilages, so if you're using a *nix I'd say its much harder to do that.

    2. Re:pack.exe as Perl/ZeuS Trojan? by betterunixthanunix · · Score: 4, Informative

      Most GNU/Linux systems (and I assume but cannot really say for sure about Mac OS X) will not just execute an arbitrary file that you download. Generally you have to at least set execute permissions on the file to get it to run, or feed it to its interpreter on its own (if it is a script). Additionally, for a secure desktop, one would generally set "noexec" on the home directories partition, so that users cannot just execute random code.

      Really though, this is all superficial by comparison with multilevel security systems, which for someone with top secret clearance seems like an obvious measure. MLS policies should forbid a program that you download from some random website from even opening a file that is "Top Secret," let alone sending a copy to some other system. A lot of research went into such systems, which are designed around the assumption that the threats are internal (e.g. a malicious program that is already running on the system) and that the goal is to prevent leaks (as opposed to the more common goal of restricting unauthorized access).

      --
      Palm trees and 8
    3. Re:pack.exe as Perl/ZeuS Trojan? by The+MAZZTer · · Score: 1

      You could write it in something cross-platform and common, like Java, and trick people into opening the .jar file and running the program.

    4. Re:pack.exe as Perl/ZeuS Trojan? by TaoPhoenix · · Score: 2

      Why is the quality of malware better than the quality of some commercial SFW ware?

      --
      My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
    5. Re:pack.exe as Perl/ZeuS Trojan? by Haedrian · · Score: 1

      Hello Employee

      Merry Christmas! Attached please find card. Remember to set executable bit to yes before running this jar file.

      Regards

      The Whitehouse

      Ps - If you fell for this one you will need to retake your computer proficiency test.

    6. Re:pack.exe as Perl/ZeuS Trojan? by AHuxley · · Score: 1

      Thanks, you would think Windows would be banned, reduced to admin ect. No air gap. UFO seekers with dial up and now more perl fun. I guess Windows keeps the 'fix it again' contractors very busy and happy.

      --
      Domestic spying is now "Benign Information Gathering"
    7. Re:pack.exe as Perl/ZeuS Trojan? by L4t3r4lu5 · · Score: 1

      Don't blame Windows. This was a case of government employees being duped by an email Christmas Card. They may as well have "checked out this screensaver!" or pictures of "Anna Kornikova"

      I suggest a new stipulation in government contracts: You will be given a one-day basic data security course. You will be trained in how to identify emails which are not genuine, and how to dispose of them properly. Once completed, you will sign to say you have undertaken the course and will enact all advice and policy contained therein. Any data breaches which would have been avoided by following said advice and policy will result in immediate dismissal for gross negligence, and prosecution under appropriate data protection legislation (In the UK, that's up to £500,000 personal fine and 6 months in prison. Your employer is legally prevented from reimbursing you for the fine.)

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    8. Re:pack.exe as Perl/ZeuS Trojan? by mcgrew · · Score: 1

      things also requires root privilages

      Only if you're trying to install something that can fuck up the whole system. It's not hard at all to install FireFox in userspace, although it won't be available to other users unless they have rights to the directory it's installed in.

      Windows is the OS that insists that all its programs be installed in root, and some idiots write programs that insist you run them as administrator (why does MS allow this?).

      "Open the pod bay doors, HAL"
      "I'm sorry, Dave, I can't do that."
      "SuDo open the pod bay doors!"
      "OK"

    9. Re:pack.exe as Perl/ZeuS Trojan? by david.emery · · Score: 1

      Blame Windows. These vulnerabilities don't exist, or at least are not exploitable/exploited to the same degree on other platforms.

      I'm still waiting for a -successful attack- like this on the Mac. Given the growing Apple market share, particularly concentrated at the high end (i.e. more wealthy) of the market, I'm still not buying the argument that 'all computers are equally vulnerable.' But then, I don't support purely random searches to prevent terrorism, either.

    10. Re:pack.exe as Perl/ZeuS Trojan? by betterunixthanunix · · Score: 1

      Interestingly, Mac OS X (last I checked) did not have a built in MLS policy framework; Windows 2000 and up do, and enterprise GNU/Linux distros do. It really comes down to a question of competence, namely, are these systems configured to actually take advantage of their security systems? Unfortunately, the answer appears to be no; you can sneak data out of secure environments using a CD, you can have a random program from the net read classified documents, etc.

      If anything, we should blame the IT staff.

      --
      Palm trees and 8
    11. Re:pack.exe as Perl/ZeuS Trojan? by Anonymous Coward · · Score: 0

      Windows is the OS that insists that all its programs be installed in root...

      Bzzt... Wrong, it doesn't. In fact, it works the same way Linux does in this regard. Try installing Google Chrome browser and see where it gets installed. Any properly written app can be installed like that. Many current installs will ask if you want it "for all users" or "just for you" and allow you to choose. Now, are a lot of programmers / setup writers lazy and make you install to "C:\Program Files"? Yes. Does Windows require this? Absolutely not.

    12. Re:pack.exe as Perl/ZeuS Trojan? by Anonymous Coward · · Score: 0

      Of course it's windows. Did you not read the posts above yours about Microsoft,by default, allowing unknown programs to run as root. And real OSs ,by default, don't.

    13. Re:pack.exe as Perl/ZeuS Trojan? by betterunixthanunix · · Score: 2

      It's not hard at all to install FireFox in userspace

      It can be, if you mounted the home directories partition with "noexec".

      --
      Palm trees and 8
    14. Re:pack.exe as Perl/ZeuS Trojan? by david.emery · · Score: 1

      Valid point, but I think we're conflating a couple of issues:
          1. vulnerability to these kinds of attacks
          2. existence of management controls to turn off some classes of access

      You can't have "a random program from the net read classified documents" unless there's a cross-domain guard of some sort to bridge the classified and unclassified networks.

    15. Re:pack.exe as Perl/ZeuS Trojan? by gstoddart · · Score: 1

      Really silly q, but why do the scripts seem to be just so Windows based/Windows friendly?

      Because it's just so damned easy? Sadly, some of the "user friendly" settings Microsoft has done over the years makes some of this stuff happen pretty easily -- stuff like hiding the extension of well known documents so that evil-virus.jpg.exe looks like evil-virus.jpg.

      Hell, at one point, Microsoft made an urban myth true -- that you could get a virus/malware without even clicking on it, just by reading the email that contained it as they decided to just go ahead and run it for you. Up until then, those of us in tech were telling our family who forwarded all of the urban legends that it simply wasn't true -- and then one day it was.

      Microsoft has gotten a whole lot better over the years, but sometimes in order to "simplify" things for the user, they do something fairly boneheaded that ends up messing up everybody. Sometimes, the training wheels get caught in your pants and do more damage than if you'd only fallen and skinned your knee. :-P

      Is it so hard to get Mac OS X, Linux or other OS's to run something perl like via a click click of something cute in a email?

      Are you feeling left out or something? I can understand pissing and moaning that people don't make games and the like for Linux, but that the malware doesn't work? I don't get that one.

      Part of me also suspects that it's a lot harder to encode that since you'd need to be executing code within the email (before anybody clicked on anything) to determine the platform and possibly actions. I don't think that's really feasible for the most part -- but I'm sure it's possible using something obscure. I just mostly suspect it's not worth the effort -- if 90%+ of people are running Windows, why go to the trouble for the rest to spread a virus?

      --
      Lost at C:>. Found at C.
    16. Re:pack.exe as Perl/ZeuS Trojan? by L4t3r4lu5 · · Score: 1

      Yes, and I discarded them out of hand. Computers don't do anything unless they are told to. I can tell OS/X, Linux, any OS to run downloads with admin / root permissions as soon as they download by default. I can also set any of these OS's to not allow execution of any downloaded content whatsoever. The fact that one is on by default, the other off, is neither here nor there. A human either set those permissions, or left them as they are, and a human downloaded an unknown file of unknown origin, of dubious relation to their work, and ran it. Windows did not download the eCard and install the trojan, a user did.

      I'm real glad that hating an OS for a user-space issue comes so easy to you. Blaming others is a useful skill, especially if you're an idiot yourself.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    17. Re:pack.exe as Perl/ZeuS Trojan? by L4t3r4lu5 · · Score: 1

      These attacks are more difficult because as you say, lower market share makes other OSs less tempting targets, and also they are more secure by default (noexec on home directory), but that is not the issue. A government employee downloaded an eCard, and opened it, while attached to a classified network. That's a user-land issue, not a software issue. It doesn't matter how secure your OS / network is when you have users that careless / dumb.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    18. Re:pack.exe as Perl/ZeuS Trojan? by david.emery · · Score: 1

      No evidence in the base article this was loaded on a machine in a -classified- network.

      "lower market share" does NOT make attacks more difficult, it just reduces the number of potentially vulnerable machines.

    19. Re:pack.exe as Perl/ZeuS Trojan? by operagost · · Score: 1

      Blame Windows. These vulnerabilities don't exist, or at least are not exploitable/exploited to the same degree on other platforms.

      No, really... don't. The only "security" feature *nix has over Windows in this respect is the execute flag. If Linux suddenly because a viable desktop platform, I assume you that the first feature to be clamored for would be a user-friendly way of setting or ignoring the flag (like a dialog box on which everyone would automatically click "OK"). The trojan scanned the document folders on the machine, which would be accessible to any program unless you had it running as a "nobody"... but then how would your programs keep their configuration settings?

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    20. Re:pack.exe as Perl/ZeuS Trojan? by david.emery · · Score: 1

      MacOS X, which is Unix underneath the Apple GUI, doesn't have these problems, and It is a "viable desktop platform" (unless you're a Sold-your-soul-to-Microsoft CIO/IT guy...)

    21. Re:pack.exe as Perl/ZeuS Trojan? by geekoid · · Score: 1

      It's due to install base.

      It's an easy attack, and the things that make Linux secure would not be tolerated by the general public. Having to set permission to execute? that wuold last 15 seconds before a demand to automate it happen. And then there you are.

      AS a note, install base isn't in and of itself the only reason, and it's foolish to think so.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    22. Re:pack.exe as Perl/ZeuS Trojan? by mcgrew · · Score: 1

      Well, yes, it all depends on what distro and how you install it.

    23. Re:pack.exe as Perl/ZeuS Trojan? by Anonymous Coward · · Score: 0

      I don't see anywhere in the TFA where it says Top Secret material was leaked. In fact, I don't see where it claims anything of value to the government was leaked. All I see is somebody that should have known better was aced.

    24. Re:pack.exe as Perl/ZeuS Trojan? by Frosty+Piss · · Score: 2

      MLS policies should forbid a program that you download from some random website from even opening a file that is "Top Secret," let alone sending a copy to some other system.

      I seriously question the idea that Classified was downloaded from any Government / Military computers by this malware, SIPRNET and NIPRNET are two distinct networks. No one is opening greeting card email on SIPRNET. It simply isn't happening.

      There is a difference between For Official Use Only (FOUO), which can be on any gov computer, and actual classified material.

      Now, *Contractors*, who knows...

      If these "hackers" were serious, they would have sent out Lady GaGa cd's to random gubment employees...

      --
      If you want news from today, you have to come back tomorrow.
    25. Re:pack.exe as Perl/ZeuS Trojan? by GameboyRMH · · Score: 1

      ...or you just don't see a need to shell out for a closed OS to get something *nix based when many Linux distros could do the job, while costing you less and keeping you free of Apple's whims...

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    26. Re:pack.exe as Perl/ZeuS Trojan? by GameboyRMH · · Score: 1

      Actually Windows only allows the program to run as whatever the current user is. The problem is that on XP and earlier, that was usually an administrator.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    27. Re:pack.exe as Perl/ZeuS Trojan? by Anonymous Coward · · Score: 0

      When did you last use a "*nix" system? In the 1990s? There are far more security policy features available on modern *nix systems then just the executable flag and the old POSIX bits. Have you ever heard of AppArmor (to give a mainstream Linux example)? There are other MAC implementations out there as well. It is possible to limit access beyond simple uid/perm bits, and the mechanism definitely exists to allow finer grained control, even if it is sometimes difficult to implement into a smooth process.

      I'm not saying this is a panacea, but you seem to be ignorant of modern security features available.

    28. Re:pack.exe as Perl/ZeuS Trojan? by morgan_greywolf · · Score: 1

      The only "security" feature *nix has over Windows in this respect is the execute flag.

      That's not true at all.

      First off, the #1 installed-base Windows platform isn't Seven, or even Vista, it's still Windows XP, due mostly to the fact that corporate IT departments are still mandating IE 6. And most users on XP are still running everything with administrator privileges.

      Secondly, these are corporate users; they're running Outlook, which still will happily run executables attached to e-mails, not to mention VBScript, ActiveX, etc. Sure, the government IT admins should know better than allow executable attachments to e-mails, but this isn't the case here, obviously. There are no *nix mail clients which encourage this situation like Outlook does.

      Thirdly,due to distribution and platform fragmentation (as opposed to the WIndows monoculture) you can't be sure that a given executable binary will even run on the victim's machine unless you statically link everything or the executable is a script; even then there are no guarantees (and being a script means that it's easily inspected, perhaps by automated means) And even with a statically-linked executable, it still might not run. (Plus statically-linked *nix executables have the added disadvantage of being quite large and consuming tons of memory.)

      I could go on, pointing out additional problems that still exist in Vista and Seven, but as I've pointed out, Windows 7 and VIsta are irrelevant to the discussion at hand. Besides, most of the security problems on Windows aren't strictly technical; they're a perfect storm of technical problems and a monoculture of ignorance actively encouraged by Microsoft.

    29. Re:pack.exe as Perl/ZeuS Trojan? by GameboyRMH · · Score: 1

      Having to set permissions to execute something is quite rare. You either use something like a .deb or .rpm installer package, or download a .tar with the files already set as executable when you extract them.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    30. Re:pack.exe as Perl/ZeuS Trojan? by pjbgravely · · Score: 1

      Most GNU/Linux systems (and I assume but cannot really say for sure about Mac OS X) will not just execute an arbitrary file that you download. Generally you have to at least set execute permissions on the file to get it to run, or feed it to its interpreter on its own (if it is a script). Additionally, for a secure desktop, one would generally set "noexec" on the home directories partition, so that users cannot just execute random code.

      Compressing the files before sending them gets around the victim having to set it as executable.

      Using a shell script and telling the user to run it from /bin/sh will get around noexec.

      When the majority of boxes run GNU/Linux we will still have to deal with clueless lusers rooting their boxes.

      --
      Star Trek, there maybe hope.
    31. Re:pack.exe as Perl/ZeuS Trojan? by c6gunner · · Score: 1

      You can install many programs in windows without needing root privilidges. Or, alternately, you can download a portable version of the program and put it anywhere you want. Or, if no portable version exists, get Universal Installer and extract the files to whatever location you want. Very few programs actually NEED root privilidges to run on windows, it's just that most people aren't aware of the alternative, and most software vendors couldn't be bothered to offer an easy non-root-install option.

    32. Re:pack.exe as Perl/ZeuS Trojan? by chrismcb · · Score: 1

      I ASSUME this is a "windows bashing" without mentioning windows post? Windows can do the same thing you suggest. The problem is, when people get sent an e-card in the e-mail they want to see it. Doesn't matter if they are on a linux system, a Mac, or on Windows.

  7. New Rule: Detachment by digitaldc · · Score: 1

    New Rule: NEVER open an attachment.
    OR - Never open an attachment to an email (or any file sent to you) unless you know who sent it to you, and you have confirmed that they did send it to you, and they did send it at a certain time and date with the same file name.

    This should be mandatory for all employees who do not understand the danger of phishing, trojans or malware attacks.

    --
    He who knows best knows how little he knows. - Thomas Jefferson
  8. Encryption? DRM? Hello? by Haedrian · · Score: 1

    I'm still amazed that you can just suck sensitive documents off people's computers. Wouldn't these be encrypted? Or at least require a certain key to open?

    People put so much research into making your music/software only run on one computer (DRM) - and yet they can't extend it to only allow the opening of sensitive documents on certain computers? These aren't pictures of your last holiday in Greece...

    1. Re:Encryption? DRM? Hello? by somersault · · Score: 1

      These aren't pictures of your last holiday in Greece...

      But I'm a suspected terrorist who just had a holiday in Greece! And I was sure those guys with cameras were government operatives! Well, at least the malware authors didn't get a good look at me in my speedos.

      --
      which is totally what she said
    2. Re:Encryption? DRM? Hello? by arth1 · · Score: 1

      People believe encryption works differently than it does.
      Bitlocker, for example, is largely worthless except specific scenario, because when you mount the drive, it becomes unencrypted for all users.
      EFS is somewhat better, because the file contents will only be available to the user who owns the key, or who has access to import that key.

      But neither will protect the currently logged in user or any processes he starts from accessing the documents. You need a vault for that. (Programs that encrypt/decrypt files in place, give them a new name to signify that they're encrypted are usually unsafe. The unencrypted file can be brought back by the "Versions" snapshot feature, unless it's turned off. Which is why a vault is far better.)

    3. Re:Encryption? DRM? Hello? by Anonymous Coward · · Score: 1

      Encryption on our Windows systems are tied in to customer's Windows log ons. Once they log on, encryption is open and files are then available to running processes. The encryption's primarily to prevent access of files if hard drive is obtained by bad guys.

      On Macs, we have customers use encrypted disk images as well as File Vault (encrypts user directory), They have to authenticate to the disk images after they have logged on to their systems. 'Course, most customers go and set the disk images to auto-open (prompt for login) as soon as their desktop comes up. Files are then available to customer's runtime processes.

      I've never seen a set up of requiring a password for individual files, but then I only support equipment used for S and TS levels.

    4. Re:Encryption? DRM? Hello? by russotto · · Score: 1

      Believe it or not, people do actually have to get work done, even with sensitive documents. Make it so e.g. they have to type in a 100-character passphrase and enter a one-time password from a key card every time they open the document, and they're going to leave the document open all the time or spoil the security in some other way.

    5. Re:Encryption? DRM? Hello? by GameboyRMH · · Score: 1

      If they required a key to open every file it would be too annoying.

      But this sort of thing requires a DRM-ish approach (send A to C without B seeing when B and C are the same thing - the user's computer), which is somewhere between very difficult and impossible to pull off successfully.

      I think the first step to securing these government networks is to switch to a more secure OS and go centralized. Use diskless network booting thin clients and/or virtualized desktops (I'm thinking they can use net-booting thin clients at the physical office, and if they want remote access, they can VPN in and connect to a virtual machine via remote desktop). Keep everything in one place so it can't get lost and nobody can fuck with the OS. Now that everything's in one place, backups, maintenance and monitoring are easy. No more idiots running around with infected laptops full of important information or leaving computers in taxis and on trains. This would fix a huge number of problems right off the bat.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    6. Re:Encryption? DRM? Hello? by GameboyRMH · · Score: 1

      Too late, you've been caught - and what a ladies man you are!

      http://www.sportouring.com/itemImages/image/borat-mankini-2.jpg

      (^only technically SFW)

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    7. Re:Encryption? DRM? Hello? by GameboyRMH · · Score: 1

      Exactly, full-disk encryption adds to the computer's physical security, it adds nothing to software security.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    8. Re:Encryption? DRM? Hello? by Em+Adespoton · · Score: 1

      Believe it or not, people do actually have to get work done, even with sensitive documents. Make it so e.g. they have to type in a 100-character passphrase and enter a one-time password from a key card every time they open the document, and they're going to leave the document open all the time or spoil the security in some other way.

      This is why we have keychains. The documents should always be encrypted on disk, and swapspace should always be encrypted. The only place you should find unencrypted classified docs is in memory, and then only when the document is open. Sure, a keylogger or memory scraper can still get the open document, but a contractor working on classified documents isn't going to have all 5,000 of their classified documents open all the time; they might have one or two. Those will leak, the others will be received without the encryption key, and so will be largely useless. This level of security has been freely available, vetted, and even USED BY PRIVATE CITIZENS AND CORPORATIONS for over a decade. It introduces almost no overhead for the end user, and once the infrastructure change is complete, adds very little overhead for the sysadmin. It is recommended practice by the NSA and the CIA; why aren't all government offices REQUIRED to meet this level? After all, they are pretty much requiring it of the healthcare industry.

  9. they could stop it immediately by JustNiz · · Score: 1

    just by giving up their windows obsession and using Linux instead.

    1. Re:they could stop it immediately by Anonymous Coward · · Score: 0

      That's right, who could forget that Linux is so magically advanced that it doesn't give access to a user's documents for an application the user has willingly executed.

    2. Re:they could stop it immediately by FrootLoops · · Score: 1

      Well, the ZueS trojan doesn't seem to run on Linux. There's also Unix's standard execute file permission to consider.

    3. Re:they could stop it immediately by Haedrian · · Score: 1

      Simple solution is not putting the sensitive documents as user's documents but give read permissions only to root or another user which has a seperate password. If you want to access the documents, you need to su. If a program looks for them, it won't find them.

    4. Re:they could stop it immediately by ScentCone · · Score: 1

      just by giving up their windows obsession and using Linux instead

      Right, because users never willingly install or run applications on Linux. Oh, but you're going to say that Linux provides granular enough security to prevent that. So does Windows, if you're using a recent version. Doesn't matter. This is an admin issue, and a social hacking issue.

      --
      Don't disappoint your bird dog. Go to the range.
    5. Re:they could stop it immediately by FrootLoops · · Score: 1

      You're suggesting Linux as a solution to people who click on random email attachments? Aside from software compatibility issues, these people are probably barely capable of doing what they do on Windows, which they use at home and can ask other people about, and are already used to. Imagine yourself offering phone tech support to these people during the switchover, trying to talk them through a simple command line task. Personally, that thought makes me cringe.

    6. Re:they could stop it immediately by NeverVotedBush · · Score: 1

      Um, you do know about KDE, Gnome, and other desktops that make it where users don't need to open terminal windows, right?

      I think most Linux users see desktops very similar (though IMO better) to Windows. They open programs the same way, look at directories the same way, etc.

      And in both Windows and Linux, you can grab a terminal window and go all command line if you want to.

    7. Re:they could stop it immediately by geekoid · · Score: 1

      Would not help.. at all.

      They ran a program that did this, they could also be tricked into running a program in Linux.

      Linux can NOT stop any user from doing stupid shit. It protects them in that properly set up recovery is simple.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    8. Re:they could stop it immediately by JustNiz · · Score: 1

      It help a lot to be running Linux because normal users cant extend or modify the operating system or its configuration. Normal Windows users (and processes they run) can.

    9. Re:they could stop it immediately by GameboyRMH · · Score: 1

      That's actually possible with Linux, and trivially easy to do. Mount /home as noexec, don't give user the root password, and they can click on the dancing bunnies all they want.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    10. Re:they could stop it immediately by GameboyRMH · · Score: 1

      Imagine yourself offering phone tech support to these people during the switchover, trying to talk them through a simple command line task.

      I actually had to do that, it was nearly impossible to get my sister to open a terminal window (she had never used it before and had no idea it even existed) on her Ubuntu laptop and type in "alsactl restore" but it turned out she just had her headset plugged in wrong, so it wasn't needed anyway.

      So, problems so far when switching clueless users to Linux: 0

      Problems avoided by not running Windows: OVER 9000!!!

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    11. Re:they could stop it immediately by GameboyRMH · · Score: 1

      Yep all the clueless users I've switched to Linux (Ubuntu and variants) don't even know their computer has a CLI at all.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    12. Re:they could stop it immediately by FrootLoops · · Score: 1

      Yes, I know. Troubleshooting Windows doesn't often involve the command line (of course, sometimes it does) while troubleshooting Linux very often does. Certainly in some tasks like the ones you mentioned the differences are very superficial.

  10. Again...vague on the most important detail... by Anonymous Coward · · Score: 0

    Windows, Linux, or Mac? What platform was affected? Why don't they EVER tell us? *sigh*

  11. Awful Attempt by Anonymous Coward · · Score: 1

    Ok I was among those that received this spoofed WH holiday e-card and let me tell you, it was an AWFUL spoof attempt. I can't/won't go into the specifics, but it was terrible and anyone who fell for it should be smacked silly.

    1. Re:Awful Attempt by Anonymous Coward · · Score: 1

      ...or given a job in the government. Oh wait.

    2. Re:Awful Attempt by operagost · · Score: 0

      You can call federal government employees stupid all you want, but they earn almost twice as much as the average American. They have been getting big raises every year while the rest of us who actually produce have been getting pay cuts or freezes.

      --

      Gamingmuseum.com: Give your 3D accelerator a rest.
    3. Re:Awful Attempt by Anonymous Coward · · Score: 0

      They have been getting big raises every year while the rest of us who actually produce have been getting pay cuts or freezes.

      Ha, ha, ha. Pull the other one!

      Signed,

      Every Public Employee (besides elected officials or chancellors of big public universities, of course)

  12. Read the victim list by Anonymous Coward · · Score: 5, Insightful

    It's not so much the crime than the type of victims:

    -An employee at the National Science Foundation’s Office of Cyber Infrastructure.
    -An intelligence analyst in Massachusetts State Police
    -An unidentified employee at the Financial Action Task Force, [in a government body whose purpose is to fight] money laundering and terrorist financing.
    -An official with the Moroccan government’s Ministry of Industry, Commerce and New Technologies.

    Me, I'm an idiot with no influence, but the people who set policies and can put people in jail should know better.

    1. Re:Read the victim list by prezkennedy.org · · Score: 1

      I'm a database engineer, received the e-mail, looked at it for about a minute, became suspicious because the White House doesn't have my e-mail address, noticed the links, and discarded it without a second thought because it was an obvious hoax .

      --
      It started back in Team Fortress Classic
  13. Re:will be sorted by the "tea Party" representativ by Cornwallis · · Score: 1

    I'm sure you think you're being clever but there is/was a point to holding the lid on technology in the White House.

    You may or may not recall how the Clinton staffers all made fun of the Bush 1 White House upon learning they didn't use email and had "old fashioned" phones.

    Guess what? The Bush 1 administration had a good handle on leaks because they didn't rush to embrace the latest and greatest unlike just about everyone now.

  14. Belarus by Max_W · · Score: 2, Insightful

    This type of activity is illegal in Belarus too. The streets there do have names and houses are numbered. True, it is not in English.

    Still if it was some kid, a call from the Interpol to Belarus police, and the employees probably could have they files back. Sometimes learning foreign languages at school could be very useful.

    1. Re:Belarus by socsoc · · Score: 1

      What?

    2. Re:Belarus by Max_W · · Score: 3, Informative

      In the article it is written that files were sent to a server in Belarus. My point is that it is not like they were sent to the Mars.

      And if there were a good working relationship between criminal police in D.C. and in Minsk, this could be easily solved or even prevented.

    3. Re:Belarus by Max_W · · Score: 1

      Belarus is a country in Eastern Europe, with the capital - Minsk.

    4. Re:Belarus by NeverVotedBush · · Score: 1

      Dude, while I have no special information, that is most likely just a compromised box and the files were ultimately sent elsewhere.

      There might be information about the next link in the chain or there might not. If it was real espionage, I doubt there will be traces and there will be a number of intermediaries.

    5. Re:Belarus by Gilmoure · · Score: 1

      It's not a large, sea-going mammal with really large tusks?

      Who knew?

      --
      I drank what? -- Socrates
    6. Re:Belarus by GameboyRMH · · Score: 1

      "The bank robbers went into this warehouse! They must live here or at least be the legal owners! Quick, somebody pull up the information on this place and assemble a SWAT team!"

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
  15. Re:New Rule: Detachment by couchslug · · Score: 1

    New Rule:

    Don't run an insecure operating system. One thing people forget about government employees is that they can be given fucking orders to change, and they don't have to fucking like it. You can literally tell people to "do it and shut up".

    For example, when the USAF went from green screen Unix terminals to Windows, snivelling wasn't an option. Obey orders or be punished.

    If security is ever taken seriously, issue orders to change, fry those who refuse, end of story.

    --
    "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
  16. Re:will be sorted by the "tea Party" representativ by betterunixthanunix · · Score: 1

    To be fair, though, there is at least one government agency that uses the latest and greatest (or so we think) and that has remained secure:

    http://en.wikipedia.org/wiki/National_Security_Agency

    --
    Palm trees and 8
  17. Shows you the by p51d007 · · Score: 1

    mentality of the average government drone.

  18. So you mean by VincenzoRomano · · Score: 2

    That GOV documents like ehm ... cables can LEAK out without the intervantion of an insider?
    Interesting ... indeed.

    --
    Maybe Computers will never be as intelligent as Humans.
    For sure they won't ever become so stupid. [VR-1988]
    1. Re:So you mean by ScentCone · · Score: 1

      without the intervantion of an insider?

      What are you talking about? They don't leak out on their own. If someone installs a piece of software that grants a third party access to their desktop, then you've just had an insider getting involved. The difference is between an insider doing it stupidly but unintentionally, vs someone like PFC Manning, who stupidly did it on purpose.

      --
      Don't disappoint your bird dog. Go to the range.
    2. Re:So you mean by Anonymous Coward · · Score: 0

      That GOV documents like ehm ... cables can LEAK out without the intervantion of an insider?

      Of course not. This leak requires the assistance of at least two of these insiders:
      - the IT "professional" that decided against using multi-level security even though government acquisition regulations require the functionality
      - the drooling drone that clicks on the "ooh! shiny!" link in a random e-mail
      - the HR "professional" that decided against providing proper drone training for handling highly sensitive documents

    3. Re:So you mean by tophermeyer · · Score: 1

      - the HR "professional" that decided against providing proper drone training for handling highly sensitive documents

      As a professional responsible for training and development programs, I have to take offence at that one. There is nothing indicating this was an issue with lack of training. In my experience one of the things the government is very good at is distributing trainings on how to handle sensitive materials. However one thing that many employees are bad at is learning things that don't immediately impact their day to day existence.

      If dimwits or super egotistical self described savants can't be bothered to pay attention to trainings or take their content seriously, you can't blame HR.

    4. Re:So you mean by Ungrounded+Lightning · · Score: 1

      ... vs someone like PFC Manning, who stupidly did it on purpose.

      My impression is that Manning did it after considerable thought, out of a personal moral code which (though you or I may not agree with it) rated the disclosure as a moral act.

      So "stupid" (as opposed to, perhaps, "misguided") doesn't necessarily apply to him. But it almost certainly does to whomever designed the handing of all those documents such that he could get hold of them. B-)

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    5. Re:So you mean by ScentCone · · Score: 1

      out of a personal moral code

      Something tells me that his personal moral code was not brought to bear on each of a quarter million stolen documents. He spread around documents that identify intel sources that are working against the regime in Iran, for example. Does his personal moral code have room in it for things like how that regime will use that knowledge to apply pressure to that ex-pat's family, still in Iran? Either he thinks that things like that are no big deal (which means his moral code is absurd), or he really wasn't using any moral compass as he spewed out everything he could his hands on and deliver to Assange in the interests of getting his 15 minutes of fame ... which also means his moral code is broken.

      I used the word "stupidly" because he clearly wasn't thinking about the consequences to other people, wasn't thinking about the consequences for himself, or the consequences for his fellow servicemen and women.

      --
      Don't disappoint your bird dog. Go to the range.
  19. I was having trouble waking up this morning... by Anonymous Coward · · Score: 0

    The real tip off that this wasn't real it that it was a CHRISTMAS card from the white-house, Kwanzaa, would have been more believable.

    ...so thanks for the much-needed facepalm.
    (For future reference, just get it over with and call the guy a nigger; it's immediately obvious that that's how you feel, so you don't need to dance around that shit.)

  20. Practicin' my terminology... by dogsbreath · · Score: 1

    "malware-laced e-mail"

    Ok... isn't this a tautology?

    "contractors who work on cybersecurity "

    and isn't this an oxymoron?

    Signed "anxious to learn"

    1. Re:Practicin' my terminology... by Anonymous Coward · · Score: 0

      "malware-laced e-mail"

      Ok... isn't this a tautology?

      "contractors who work on cybersecurity "

      and isn't this an oxymoron?

      Signed "anxious to learn"

      No and no. I rarely get emails (maybe once a year) that either (a) aren't from a real person I know or (b) I didn't sign up for. Maybe you should stop using hotmail or whatever.

      Also, the fact that contractors are passed around to various agencies doesn't make them less secure. They still must have the same clearance as someone who works for one company.

    2. Re:Practicin' my terminology... by Anonymous Coward · · Score: 0

      Touchy. You seem humor-challenged today.

      You are probably a fairly competent consultant who doesn't get exposed to a lot of the really bad practices that many of your peers exhibit. There is only so much that can be done: certainly it is fairly easy to keep contractors from bringing bad stuff in, but leaking information is tough to stop.

       

  21. funny.... by Anonymous Coward · · Score: 0

    Funny how the "professionals" are totally clueless where they think that even in this day and age of "understanding" (hello to you, navy guy who just wanted to make some people laugh) that they can trust emails, even on Xmas day.

    This time, this one time, I'm rooting for the bad guys.

  22. Re:will be sorted by the "tea Party" representativ by AHuxley · · Score: 1

    Yes the NSA got it right from day one via COMINT only (above top secret), slap on eg Trine, Dinar, Vipar, Froth designations. Then make sure only Gout cleared people can read Gout message. Unless oathed, briefed, certified, you dont get in.
    Now we have Windows and any modem using UFO hunter can have a go.

    --
    Domestic spying is now "Benign Information Gathering"
  23. Re:will be sorted by the "tea Party" representativ by Cornwallis · · Score: 1

    To be fair, though, there is at least one government agency that uses the latest and greatest (or so we think) and that has remained secure:

    I don't think so! :)

    http://it.slashdot.org/article.pl?sid=10/12/17/1540256

  24. Re:New Rule: Detachment by MadKeithV · · Score: 1

    Rule 0: don't allow stupid people near important data.

  25. freeze the bank account of the sender! by kubitus · · Score: 1
    isn't this the obvious solution to hit these bad people who do such things?

    Block their credit cards too!

    1. Re:freeze the bank account of the sender! by FrootLoops · · Score: 1

      If only.... Maybe we should hit the recipients who fell for it? Naw....

      I had to give some phone tech support today to somebody who installed random internet toolbars and eventually complained to me about their machine running so slowly. It's not like they're a bad person, terrible at their job (the opposite, really), they're just terrible at maintaining a computer. I suppose it's a little more serious when you have sensitive information on your machine.

      Earlier today I was also reading an article written by a coder who rederived Atan2. To me that's similar--the article was about 3D graphics, and the guy should have known about Atan2, especially if he's gonna play the expert by writing an article. Analogously, these government employees should known about bad email attachments.

      I suppose my point is people make mistakes. It's easier to be annoyed at stupid people's mistakes and think the Atan2 guy's mistake was less serious just because it's more technical. But, virtually everyone is stupid compared to someone else, so that extra annoyance is arbitrary.

  26. Re:will be sorted by the "tea Party" representativ by FrootLoops · · Score: 1

    Well, the relevant quote is "There's no such thing as 'secure' any more", which isn't quite the same as the NSA saying "we are not secure but we believe X's network is."

  27. Espionage Case-in-Point by Bob9113 · · Score: 1

    A run-of-the-mill malware-laced e-mail that spoofed seasons greetings from The White House siphoned gigabytes of sensitive documents ... espionage attacks.

    Looking for the upside here: It is nice to have a solid case of espionage as an example against which to compare and contrast WikiLeaks.

    Hypothesis: When a person or organization uses deception or other coercion to manipulate a person with clearance into exposing sensitive information, that is espionage. Whether WikiLeaks engaged in espionage is a question of whether WikiLeaks engaged in such deception or other coercion.

    Is that a valid principle?

    1. Re:Espionage Case-in-Point by Anonymous Coward · · Score: 0

      Whether WikiLeaks engaged in espionage is a question of whether WikiLeaks engaged in such deception or other coercion.

      Is that a valid principle?

      It might change the severity of the punishment. In the wikileaks case, the informant knowingly broke the law, so I would presume the punishment for the perpitrator should be harsher than a person who was tricked into relieving sensitive data.

  28. Re:Serves them right for trusting Obammy by Anonymous Coward · · Score: 0

    The date may have changed, but the facts have not. As inconvenient as it is for you to understand, your black messiah is a fraud.

  29. Re:jar by TaoPhoenix · · Score: 1

    Check out this Screensaver from the upcoming Star Wars MMO!

    Binks.jar.jar

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  30. Re:New Rule: Detachment by TaoPhoenix · · Score: 1

    You can't get your plausible deniability if you pick someone good!

    --
    My first Journal Entry ever, in 8 years! http://slashdot.org/journal/365947/aphelion-scifi-fantasy-horror-poetry-webzine
  31. These gov employees are high-tech terrorists... by flyingfsck · · Score: 1

    They should be charged with sexual crimes and placed under house arrest forthwith...

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  32. Re:New Rule: Detachment by jd3nn1s · · Score: 1

    What privileged operation is required to access resources that are readily available to the user context? None that I can think of. You can read files and connect to the network without root/administrator. This can only be solved with a combination of policy and user education. AV and attachment filtering would be a start. As this was a targeted attack I don't think that security by obscurity would necessarily work (i.e. running a different OS)

  33. Re:New Rule: Detachment by Haedrian · · Score: 1

    But that would be the end of the government as we know it :(

  34. Re:New Rule: Detachment by Anonymous Coward · · Score: 0

    Wait, I've got an even better idea, Einstein! How about cryptographically signing your damn messages and only opening attachments from legit senders?

  35. Re:Serves them right for trusting Obammy by Anonymous Coward · · Score: 0

    Don't you have a street corner to go stand on?

  36. "Criminal police" indeed by SteveFoerster · · Score: 1

    If the criminal police in the U.S. and those in Belarus had a good working relationship, presumably they would just cooperate to exploit their governmental authority to accomplish even more crime.

    --
    Space game using normal deck of cards: http://BattleCards.org
  37. What ever you do .. by doperative · · Score: 1

    What ever you do, don't mention Windows or Redmond :)

  38. Re:New Rule: Detachment by MadKeithV · · Score: 1

    You make that sound as if it's a bad thing.

  39. Re:will be sorted by the "tea Party" representativ by operagost · · Score: 1

    Ironic, because President Clinton himself only ever sent two emails.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  40. Sensitive Data + Malware Solution by TheoMurpse · · Score: 1

    If a government employee works with sensitive data and has his computer infected with malware due to his own mistake (esp. the types in cybersecurity), he should be fired and so should the networking guy who should have offloaded the sensitive data to a computer not connected to the Internet. This is what I consider unforgivable incompetence.

    1. Re:Sensitive Data + Malware Solution by geekoid · · Score: 1

      That's a great way ti repeat the mistakes and keep retraining.

      Or, you know suck it up and fix the problem. THAT is what should happen.

      But people like you want to run around blaming the victims.

      --
      The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
    2. Re:Sensitive Data + Malware Solution by TheoMurpse · · Score: 1

      blaming the victims

      Excuse me? *runs EXE screensaver advertising Glee Girls Nude!* *reveals nuclear codes*
      *is upset when is fired for being stupid*

      And I fail to see how a network admin is a "victim" when he "engineers" a crappy security system.

      And I have worked for the federal government. You aren't even ALLOWED on a computer that can access the Internet until you go through security training. So better to fire the moron who doesn't pay attention to his RIDICULOUSLY FRIGGING IMPORTANT security training than risk him not giving a shit and doing it again.

    3. Re:Sensitive Data + Malware Solution by Ungrounded+Lightning · · Score: 1

      And I have worked for the federal government. You aren't even ALLOWED on a computer that can access the Internet until you go through security training.

      If it's anything like the security training I've seen in the private sector, it's a joke.

      (My second favorite bit in one I saw was where the mandatory training would only run on Internet Explorer if you wanted your "grade" to count. My favorite part was where the script - which already has your single-login-id-for-everything-in-the-company asks you to enter your password so it can check whether it's a "good" one. B-b )

      The question is: Why are they (government departments or enterprises) deploying Windows and related systems at all in a secure environment, rather than removing it entirely as fast as they can retrain their personnel? They're already known to be the most exploitable and exploited systems by orders of magnitude.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    4. Re:Sensitive Data + Malware Solution by TheoMurpse · · Score: 1

      The question is: Why are they (government departments or enterprises) deploying Windows and related systems at all in a secure environment, rather than removing it entirely as fast as they can retrain their personnel? They're already known to be the most exploitable and exploited systems by orders of magnitude.

      Because when people like me say such people should be fired, people like you say "don't blame the victim"! :)

  41. Ugh! by mschaffer · · Score: 1

    I just love our government.
    So how long until they try to blame this on Wikileaks or Assange?

  42. Re:New Rule: Detachment by geekoid · · Score: 1

    new rule: don't allow attachments, ever.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  43. Re:will be sorted by the "tea Party" representativ by geekoid · · Score: 1

    Bush one didn't have the scope of attack, and in meat space, they did NOT have a handle on leaks.

    You are correct in that government agency should move forward cautiously and wisely. However when they do that the citizens laugh at the 'old' systems.

    --
    The Kruger Dunning explains most post on /. http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect
  44. Why Windows is to blame. by whoever57 · · Score: 2

    Don't blame Windows. This was a case of government employees being duped by an email Christmas Card. They may as well have "checked out this screensaver!" or pictures of "Anna Kornikova"

    Apologists like you are why we have lousy computer security as a nation.

    You blame the users, elsewhere people blame the sysadmins for not locking down the systems. Which is it? Neither, because the root problem is that Windows is designed to be used in a non-locked down mode.

    How many people actually run Windows as non-admin users? It's a pain. Why is it that sysadmins don't lock down Windows machines? If this were not the norm, one could blame a few sysadmins for not doing their job properly, but it reflects how most Windows systems are used. Why is this? The answer lies in how people expect to run Windows -- from developers through to users -- they all expect the systems to be open.

    So, while in theory Windows systems should be locked down, and users should not click on such things, in practice they are not locked down and people click on dangerous links because that is the way Windows is designed.

    Car analogy: if a car manufacturer built cars with ineffective brakes, would you blame drivers for not braking early enough?

    Where Windows is today is that the driver can make an adjustment that would make the brakes work properly, but if that were done, the car would be limited to 50mph. No-one chooses that option.

    --
    The real "Libtards" are the Libertarians!
    1. Re:Why Windows is to blame. by GameboyRMH · · Score: 1

      How many people actually run Windows as non-admin users? It's a pain.

      Actually in Win7 it's no worse than running Linux as a standard user. Most everything works, and for any corner cases that don't, you get a graphical popup window that prompts for a password.

      In this particular case it isn't really Windows' fault. The only way to work around the Dancing Bunnies problem is to prevent the user from executing arbitrary code - on a Linux distro that doesn't have /home mounted as noexec, the exact same thing could have happened, with some idiot running Dancing Bunnies.sh that installs a trojan to the userspace and has it run when the desktop environment launches.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:Why Windows is to blame. by whoever57 · · Score: 1

      on a Linux distro that doesn't have /home mounted as noexec, the exact same thing could have happened, with some idiot running Dancing Bunnies.sh that installs a trojan to the userspace and has it run when the desktop environment launches.

      We should be careful of false dichotomies. Just because Linux might have the same weakness, does not make it any less WIndows' fault.

      However, Windows 2000 has been out for over 10 years, Windows XP has been out almost 10 years. We have had enough time to realize that training users to not click on the dancing bunnies is not an effective strategy to prevent this type of problem. Hence the problem is that WIndows doesn't have a mechanism to prevent execution of arbitrary code which is normally on and not easily overridden by the user.

      Thought experiment: why doesn't MS offer a locked-down-by-default version of WIndows ("Windows for Government" or Windows Secure")? It could be just the same as a normal version except that all the security options default to it being secure, rather than open? There are a number of possible reasons and they all point to MS being the root cause of the PC security problems found by Windows users.

      --
      The real "Libtards" are the Libertarians!
    3. Re:Why Windows is to blame. by c6gunner · · Score: 2

      How many people actually run Windows as non-admin users?

      In an enterprise environment? The majority. On government systems? EVERYONE.

      This e-card had nothing to do with admin rights, so claiming that "the root problem is that Windows is designed to be used in a non-locked down mode" is silly, at best.

      Or, to put it in simpler words: "Apologists like you are why we have lousy computer security as a nation."

    4. Re:Why Windows is to blame. by whoever57 · · Score: 2

      In an enterprise environment? The majority. On government systems? EVERYONE.

      So, what you are saying is that it is impossible to lock down Windows so that it is secure?

      --
      The real "Libtards" are the Libertarians!
    5. Re:Why Windows is to blame. by c6gunner · · Score: 1

      Oh, it's quite possible. Just encrypt the entire disk with truecrypt, and then throw away the key. I guarantee nobody will be able to break into that system for at least a decade or two. You can do it with Linux, too - use LUKS instead of truecrypt.

      Other than, that, it depends on what your definition of "secure" is. Once again, this e-mail has absolutely dick all to do with OS security. If you allow users to have documents, and you allow users to run files, and you allow users to send and receive e-mails, then you're creating an environment where a user can run a program which copies all of his documents and e-mails them to someone else. Period, full stop. If you don't want that to happen, you can either educate your users, or remove one of the requirements. Maybe you can go back to using inter-office mail envelopes instead of e-mail.

    6. Re:Why Windows is to blame. by lennier · · Score: 1

      If you allow users to have documents, and you allow users to run files, and you allow users to send and receive e-mails, then you're creating an environment where a user can run a program which copies all of his documents and e-mails them to someone else. Period, full stop.

      Semicolon, parenthesis: that doesn't actually follow logically.

      If you allow users to run files which by default have full access to read all the user's documents and create emails, then yes, such a thing can happen.

      But in an OS properly designed for security, it is not the case that merely being able to run a file also grants that file all user permissions.

      This - sandboxing executables into a minimum set of rights unless the user explicitly grants them full permissions to act on their behalf - is the part which Windows didn't really even try to do until Vista (despite having a full ACL model sitting around mostly unused in the kernel).

      Worse, the pervasive COM architecture meant that once you ran an .exe or .dll, it could send messages to orchestrate every installed component, like Office and Outlook, without the user's awareness, let alone permission.

      This is why admins hate Windows. It is wide open in ways that properly designed OSes needn't be.

      --
      You are not a brain: http://books.google.com/books?id=2oV61CeDx-YC
    7. Re:Why Windows is to blame. by whoever57 · · Score: 1

      Other than, that, it depends on what your definition of "secure" is. Once again, this e-mail has absolutely dick all to do with OS security. If you allow users to have documents, and you allow users to run files, and you allow users to send and receive e-mails, then you're creating an environment where a user can run a program which copies all of his documents and e-mails them to someone else. Period, full stop

      Once again, I will label you as part of the problem. Essentially, you have given up on the idea of security.

      There is no reason why users should not be able to send and receive emails without being able to run random executables. There is no reason that it should not be possible to configure a ciomputer so that random executables cannot be executed.

      I'll say it again -- 10 years of "educating users" has failed. What did Einstein say about repeating an action and expecting a different result?

      --
      The real "Libtards" are the Libertarians!
    8. Re:Why Windows is to blame. by c6gunner · · Score: 1

      There is no reason why a computer shouldn't be able to just sit there and look pretty.

      The more control you take away from users, the less functional the machine becomes. There needs to be a balance between security and functionality, and the Vista experience has made it pretty clear that users won't willingly put up with an OS that throws dialogues and password requests at them every time they try to do anything.

      Moreover, you started this discussion by blaming Windows, so the least you can do is admit that you were wrong, and that your "solution" would need to be implemented on pretty much every OS in existence. If you can't even do that, I certainly won't waste any more time on you.

    9. Re:Why Windows is to blame. by c6gunner · · Score: 1

      Meh. You have a point, but that type of sanboxing isn't done on any user-oriented OS, and probably never will be. It's too much of a hassle, the average user won't understand it, and if you make it simple enough that they can grant rights with a click most of them will just hit "ok" no matter what. That type of security model would be helpful to power-users who get careless once in a while, and would be good for corporations that want to heavily lock down what a user can do, but they'd be completely useless for the average user.

      My employer just stops executable from being received through e-mail in the first place. Much simpler solution.

    10. Re:Why Windows is to blame. by c6gunner · · Score: 1

      P.S. This bit:

      "I'll say it again -- 10 years of "educating users" has failed. What did Einstein say about repeating an action and expecting a different result?"

      Is just fucking stupid. It's like someone in the 1920's looking at the motor-vehicle accident rate and saying "10 years of educating drivers has failed". It's only a failure if there's a practical way to fix it. Otherwise it's just a fact of life.

    11. Re:Why Windows is to blame. by Anonymous Coward · · Score: 0

      Is just fucking stupid. It's like someone in the 1920's looking at the motor-vehicle accident rate and saying "10 years of educating drivers has failed". It's only a failure if there's a practical way to fix it. Otherwise it's just a fact of life.

      I'm fairly confident that there had not been 10 years of educating drivers in the 1920s. Plus, computers have developed much more in the last 10 years than cars did. But, continuing the theme, what's happened to cars and drivers in the last 30 years -- masses of safety improvements, with little change in the education given to drivers. If we take cars as the model, we should be making computers more secure, not relying on the users to reduce the rate of problems.

      Other people have mentioned how security could be improved -- sandboxes, make it harder or impossible for users to run executables, perhaps anti-virus and other tools need better analysis techniques to identify not just specific threats, but potentially threatening behavior. But, you appear to be resistant to the concept that anything can be done other than "educating users, Good luck with that.

      In summary, when you call people "fucking stupid", you would be best advised to look in the mirror.

  45. Re:New Rule: Detachment by VJ42 · · Score: 1

    Rule 0: don't allow stupid people near important data.

    Rule -1: Don't allow stupid people.

    --
    If I have nothing to hide, you have no reason to search me
  46. What do they earn? by Anonymous Coward · · Score: 2, Interesting

    I'd love to see a salary list of all the morons that fell for this. I'm sure most make pretty solid money, yet are too stupid or gullible to see these obvious scams for what they are. Fucking pathetic. God bless america!

  47. Re:New Rule: Detachment by dave420 · · Score: 1

    Without something decent to instantly take over and maintain our lives, yes, it would be a very bad thing indeed.

  48. Re:will be sorted by the "tea Party" representativ by folderol · · Score: 1

    There never WAS any such thing as 'secure' and probably never will be! Hmmm... Folderol's first theorem :) "A system's security is inversely proportional to the value of the material being protected."

  49. Re:New Rule: Detachment by GameboyRMH · · Score: 1

    Your username/post combo makes you sound like an anarchist :P

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  50. Re:New Rule: Detachment by GameboyRMH · · Score: 1

    Running a different, more secure OS isn't security by obscurity (especially when going from closed source to open source). It's just better security.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  51. Re:will be sorted by the "tea Party" representativ by GameboyRMH · · Score: 1

    They know how to use email, that's how they send emails around saying Obama is a Muslim who isn't actually an American citizen and that net neutrality means bringing back the fairness doctrine.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  52. Documents available at wikileaks.ru by billstewart · · Score: 1

    Or should it be .su, like it was back when the original ASCII IBM Christmas Tree hack came out?

    In Soviet Russia, Wiki Leaks You!

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  53. I guess it's time... by Somewhat+Delirious · · Score: 1

    ...to also start monitoring government employees and contractors for suspicious levels of happiness, a love of cute furry pets and high levels of chrismas card appreciation:
    http://www.msnbc.msn.com/id/40916433/ns/us_news-wikileaks_in_security/
    (Jacob J. Lew, director of the White House Office of Management and Budget, suggests that agencies use psychiatrists and sociologists to measure the “relative happiness” of workers or their “despondence and grumpiness” as a way to assess their trustworthiness.")

    --
    The surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.
  54. You've never been to the ex-USSR, right? by Zontar_Thing_From_Ve · · Score: 1

    Let me tell you how this would work in neighboring Ukraine. I'd bet it's the same in Russian and Belarus.

    Assuming you can get someone like Interpol to contact the local police, then you'll have a rather corrupt and slothful police organization to deal with. I can assure you that they do not care one whit about an American security problem as they view all people in NATO countries as rich people who deserve it when bad things happen to them. If you can get the police to actually try to contact someone, the only reason they'll go at all is to tell the crooks that if they were to pay a "fine" directly to the police, the police can forget all about the case. Or if the US government somehow makes enough of a stink that it actually has to be prosecuted, the judge can always be bought off. And keep in mind that this in Ukraine where in general the population actually likes the USA as does the government. The US government is not liked in Belarus.

    1. Re:You've never been to the ex-USSR, right? by Max_W · · Score: 1

      The most common way of communicating is misunderstanding. This was my point that the working relationship is to be constructed to prevent such things.

      Certainly this is a hard task. There are linguistic, cultural, economical barriers. But it's too easy and convenient to say that everybody is corrupted in Belarus police and Interpol and nothing can be done at all.

  55. The text of the email by AftanGustur · · Score: 1
    The greeting card was actually well done, I have seen much worse APTs that this:

    ** THE LINKS ARE STILL SERVING THE MALWARE AND HAVE BEEN REMOVED**

    From: Megan Cote, megan.cote at whitehouse.gov
    Subject: Re: Merry Christmas!
    Date: 2010-12-23 15:10:55 GMT

    As you and your families gather to celebrate the holidays, we wanted to take a moment to send you our
    greetings. Be sure that we're profoundly grateful for your dedication to duty and wish you inspiration
    and success in fulfillment of our core mission.

    Greeting card:

    ** Removed **
    ** Removed **

    Merry Christmas!

    ___________________________________________
    Executive Office of the President of the United States
    The White House
    1600 Pennsylvania Avenue NW
    Washington, DC 20500

    --
    echo '[q]sa[ln0=aln80~Psnlbx]16isb572CCB9AE9DB03273snlbxq' |dc
  56. Re:will be sorted by the "tea Party" representativ by Ungrounded+Lightning · · Score: 1

    They know how to use email, ...

    Hardly surprising, given that the Tea Party was organized on the Internet in the first place. Its existence was dependent on having a broadly-deployed communication medium that was usable by the common citizens and wasn't subjected to government or mainstream media censorship.

    It's the first major US example of the Internet enabling an anti-establishment rebel/liberation movement. (Remember how much talk there used to be about how free network media would enable those? B-) )

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  57. Copies of files. by Ungrounded+Lightning · · Score: 1

    Still if it was some kid, a call from the Interpol to Belarus police, and the employees probably could have they files back.

    I think the point was that copies of files were sent to the server, not that the files were sent there and deleted on the original machine.

    So it's not that they're missing, just that somebody has access to sensitive information that he shouldn't be able to look at.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  58. Where is the NSA in all of this? by madbavarian · · Score: 1

    This incident underscores how little influence the NSA really has when it comes up against lobbyists and morally-corrupt senators trying to ingratiate themselves to the same lobbyists. It is shameful that this country has a group that is very, very good at analyzing security issues yet it isn't allowed force use of a secure operating system within the government.

  59. Re:New Rule: Detachment by jd3nn1s · · Score: 1

    But you've ignored my main point which is that no alternative OS protects from this scenario (without using some unmanageable SELinux configuration that you will switch off): User gets program as attachment, authorises the running of said program and program accesses everything user normally accesses. Therefore no privilege escalation. It is not 'more secure' in this scenario.

  60. Re:New Rule: Detachment by GameboyRMH · · Score: 1

    In Linux, you can use AppArmor which is not a PITA, or you can mount /home as noexec, leaving the user with no way to execute unauthorized code.

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  61. Re:New Rule: Detachment by MadKeithV · · Score: 1

    I'm an anarcho-syndicalist.

  62. Re:New Rule: Detachment by jd3nn1s · · Score: 1

    Both of these suggestions are cool. You could also use AppLocker on Windows to do application whitelisting.