Slashdot Mirror


Watch a Cat Video, Get Hacked: the Death of Clear-Text

New submitter onproton writes: Citizen Lab released new research today on a targeted exploitation technique used by state actors involving "network injection appliances" installed at ISPs. These devices can target and intercept unencrypted YouTube traffic and replace it with malicious code that gives the operator control over the system or installs a surveillance backdoor. One of the researchers writes, "many otherwise well-informed people think they have to do something wrong, or stupid, or insecure to get hacked—like clicking on the wrong attachments, or browsing malicious websites...many of these commonly held beliefs are not necessarily true." This technique is largely designed for targeted attacks, so it's likely most of us will be safe for now — but just one more reminder to use https.

166 comments

  1. This is just evil. by sabri · · Score: 2

    And evil doesn't cover it.

    --
    I'm not a complete idiot... Some parts are missing.
    1. Re:This is just evil. by Lazere · · Score: 1

      In other words, there has to be a bug on the client that lets the web page run arbitrary code

      Yep, that's called a browser. Arbitrary code is exactly what a webpage or video is. This is the exact reason driveby malware via ad networks still happens. If you have ISP level access and can inject malicious code in unencrypted pages, you win. The solution to this, from a web hosts view, is to encrypt everything.

    2. Re:This is just evil. by mythosaz · · Score: 4, Informative

      Rendering HTML isn't "executing arbitrary code" in any meaningful way.

    3. Re:This is just evil. by Noah+Haders · · Score: 3, Insightful

      Rendering HTML isn't "executing arbitrary code" in any meaningful way.

      "I disagree" -- hackers.

    4. Re:This is just evil. by BancBoy · · Score: 1

      Whew! I thought you were going to say hosts file. Thank heavens for that. Uh oh...

      --
      [UID-HeinzIntel]
    5. Re:This is just evil. by mysidia · · Score: 5, Insightful

      Yep, that's called a browser. Arbitrary code is exactly what a webpage or video is.

      No. Full stop. A webpage or video is a page which may contain some script language which is to be executed within a certain restricted context pertaining to the webpage domain.

      It is code execution, but not arbitrary code execution. A webpage is not supposed to be able to run arbitrary code within the meaning of arbitrary instructions on the CPU; only certain safe instructions within a highly limited scope.

    6. Re:This is just evil. by Anonymous Coward · · Score: 0

      Cats are cool.

      Totally safe, honest!

    7. Re:This is just evil. by Anonymous Coward · · Score: 0

      Would those who are claiming something can't be done please get out of the way of those doing it.

      Thank you.

    8. Re:This is just evil. by LordLimecat · · Score: 4, Insightful

      Its running code, but not arbitrary. There are limits to what code is allowed to execute. The HTML5 spec does not, for instance, allow you to read arbitrary memory locations.

      "Executing structured code" perhaps?

    9. Re:This is just evil. by Anonymous Coward · · Score: 0

      You could theoretically sandbox the CPU in its own user mode process so it can't do anything more malicious than get into an infinite loop. I think I recall Google playing around with that idea for Chrome a couple of years back, in fact. That said, the status quo today is that if you can run arbitrary CPU instructions you can pwn the system.

    10. Re:This is just evil. by Anonymous Coward · · Score: 0

      I'm not claiming it can't be done. I'm just saying there's no difference between this problem and the one where a malicious banner ad or web page exploits a known bug in your client. In either case, the solution is to keep your system patched. Unless you think the "state actors" know about vulnerabilities or backdoors that the general scum don't, of course.

    11. Re:This is just evil. by Richy_T · · Score: 1

      Yep. Hard to inject malware into a computer stuck on the BSOD.

    12. Re:This is just evil. by Richy_T · · Score: 1

      "sandbox" is the word you're reaching for.

    13. Re:This is just evil. by Anonymous Coward · · Score: 0

      lol, that didn't do shit. maybe if you were using an insecure browser like chrome or ie and allow javascript on every random site out there. better luck next time.

    14. Re: This is just evil. by Anonymous Coward · · Score: 0

      NaCl? It was great tech...too bad it didn't have legs.

    15. Re:This is just evil. by currently_awake · · Score: 1

      If you have control of the network (ISP) between the user and the web site you can man-in-the-middle the crypto and do this with https.

    16. Re:This is just evil. by doccus · · Score: 1

      It appears the ISP has to be complicit in this process.. and of course they would never agree ;-)

    17. Re:This is just evil. by mysidia · · Score: 1

      For example, if the browser is allowed to make network connections then it can run a spam-bot.

      A script running on a page can make network connections; HOWEVER, it can only connect back to the same hostname that displayed the page.

      Also, the connection can either be to a non-well-known port, or it can be to a HTTP/HTTPS URL with the same hostname.

    18. Re:This is just evil. by Anonymous Coward · · Score: 0

      And evil doesn't cover it.

      Must be a dog guy... ;-)

    19. Re:This is just evil. by Anonymous Coward · · Score: 0

      Umm... I have worked for an ISP for 14 years now, and I would be appalled if something like this was happening on our network. I absolutely know our management would agree, as well as my co-workers.

      Why such animosity toward ISPs on /.? I know many, many people in this industry, and NONE of them are as portrayed on /. Our industry tends to weed out those types, because we need the trust of our customers to continue doing business.

      Maybe I'm naive, being in the rural midwest. But please consider that there are MANY of us out here that are trying our damndest to provide a service that we can be proud of and that customers are happy with. And maybe that's the difference between us and the Comcasts of the world. We have to meet our customers face-to-face on the street every day. We deal with them in our everyday lives, both personal and business. I think maybe the Comcasts (and ATT, Verizon, etc.) lose that perspective.

      Please don't put us all in the same category... Some of us out here are really trying our best, just like any other IT job in the world.

      Posting anon because of my job.

  2. https is useless by bbn · · Score: 5, Insightful

    What good is https going to be against the state? You think they can not coerce Verisign et al to hand over a copy of the root keys?

    1. Re:https is useless by Anonymous Coward · · Score: 0

      The keys that verisign uses are there to sign the certificate. The actual encryption is handled by the keys on your server. The private portions should never be sent to any one for signing.

    2. Re:https is useless by HaeMaker · · Score: 4, Interesting

      Correct. What make anyone think: NSA agents aren't working at Google, Microsoft, Verisign, etc. Anyone checks who actually signed the certs. Almost all devices trust a few DoD root certs by default. Going to slashdot is safe? No SSL here. Do any of these GIFs, JPGs or PNGs contain exploits? If they want you, they can't get you?

    3. Re:https is useless by gameboyhippo · · Score: 5, Insightful

      Right. And if you have the keys then you can sign your own certificates. Thus allowing Eve to pretend she's Bob.

    4. Re:https is useless by heypete · · Score: 4, Informative

      What good is https going to be against the state? You think they can not coerce Verisign et al to hand over a copy of the root keys?

      Sure, they could, but I doubt they are.

      If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots. That's basically a death sentence to companies like VeriSign (rather, their cert-issuing division).

      While typical users won't notice, there's still plenty of risk to getting caught, particularly when targeting anyone using major web properties: Chrome, for example, has a bunch of high-profile sites "pinned" and will report back to Google if bogus certs are being used (they identified a bunch of MITMing with compromised certs in Iran in this way). Other add-ons like Perspectives make it easier to detect if unexpected certs are showing up.

      Could they get away with issuing infrequently-used certs for highly-targeted, one-off uses? Possibly, but each time they do the risk to their entire business increases.

      I suspect the government would much prefer to do things sneakily in the shadows, rather than involving major CAs in such a risky role.

    5. Re:https is useless by Charliemopps · · Score: 1

      What good is https going to be against the state? You think they can not coerce Verisign et al to hand over a copy of the root keys?

      That's not how it works. But of course, if they are inside Google, and Microsoft (and they are) then you're screwed. But, in my experience with keys, these sorts of attacks have to be very directed. You can't just "Hack everyone" it's an exploit you'd have to hack on an individual basis. Usually because most sites, and client computers are such unique devices. Most corporate websites have been developed over decades and are a mess of hundreds of different programmers over years. I'm involved peripherally in maintaining a couple of different large(ish) sites and the code makes me cry at times. But on the other hand, good luck hacking that without bringing the whole site down, we can barely maintain it ourselves! :-p

    6. Re:https is useless by Anonymous Coward · · Score: 0

      The keys that verisign uses are there to sign the certificate. The actual encryption is handled by the keys on your server. The private portions should never be sent to any one for signing.

      That's a nice history lesson. You can shove that shit right back in your magic hat, along with with the Constitution, Democracy, Santa Claus, and the rest of the imaginary shit kids still play make-believe with these days.

    7. Re:https is useless by Anonymous Coward · · Score: 0

      Of course, more than just a state can pull MITMs. Remember when a significant chunk of traffic passed through Iceland for some reason?

    8. Re:https is useless by AaronLS · · Score: 1

      Your response doesn't invalidate how cryptography works. It's solid math and there's no magic about it.

    9. Re:https is useless by TechyImmigrant · · Score: 4, Informative

      If the state can forge certs, the state can redirect your traffic to their youtube proxy and insert the malware just behind the fake thing you authenticated with. Your own private keys will not protect you.

      This is one of the many reasons why the public PKI is broken.

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    10. Re:https is useless by Anonymous Coward · · Score: 0

      >If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots.

      HAHAHAHAno. Thanks to the demon that is backwards compatibility browser vendors have implicitly or explicitly confirmed that they cannot actually revoke root certs. Or, more specifically, that many websites rely on that particular root to verify their identity and would break horribly if a root cert got revoked. i.e. revoking a misbehaving root will break the web.

      A better solution would be the ability to provide multiple root certs, which is not technically feasible today, and won't be for a while - even things like SSL vhosts are considered unreliable due to the prevalence of legacy browsers that don't know how to use the proper TLS extensions for hostname identification. So maybe in 10 years we can start telling site operators that they can turn on multiple certs, and 10 years after that browser vendors will have enough data to determine if it's safe to actually revoke a root cert or not. In the meantime you will have to convince HTTPS services that it's worth paying n times as much in certification costs to avoid a hypothetical root revocation.

    11. Re:https is useless by Anonymous Coward · · Score: 0

      If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots. That's basically a death sentence to companies like VeriSign (rather, their cert-issuing division).

      I wouldn't be too sure of that.

      Of all the companies that have aided the NSA, how many are out of business or even really hurting?

    12. Re:https is useless by AmiMoJo · · Score: 3, Informative

      Chrome pins Google's certs, so if anyone did try to make new fake ones the browser would flag it up. I believe there is a plug-in for Firefox that alerts you when certs change too.

      This vulnerability has been known for a long time.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    13. Re:https is useless by Noah+Haders · · Score: 1

      naïve. the NSA influenced the RSA standards board to introduce a cryptography algorithm that they had already hacked.

    14. Re:https is useless by mi · · Score: 0

      If the state can forge certs, the state can redirect your traffic to their youtube proxy and insert the malware just behind the fake thing you authenticated with.

      And that is, how things ought to be — unless we want to strip the state off their power to search us (and trail us).

      Yes, the state ought to need a proper warrant to exercise that power. But, without the described capabilities, police would not be able to do, what the warrant allows (and their job demands!) them to do.

      --
      In Soviet Washington the swamp drains you.
    15. Re:https is useless by drolli · · Score: 1

      They dont have to hand over the keys. Just get another certificate from another vendor using fake identities.

    16. Re:https is useless by Anonymous Coward · · Score: 1

      Eve? Is Bob cheating on Alice?

    17. Re:https is useless by PopeRatzo · · Score: 1

      And that is, how things ought to be — unless we want to strip the state off their power to search us (and trail us).

      That is a discussion we should have. "Searching" and "trailing" have come to mean something very different than they did when the US Constitution was written.

      Yes, we should be having that discussion right now. A power to "search us (and trail us)" might very well not be something we want to have by default. They should first be required to meet a much higher standard than currently, and that standard should be applied by someone besides a secret court that interprets secret laws, and operates secretly.

      --
      You are welcome on my lawn.
    18. Re:https is useless by heypete · · Score: 1

      >If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots.

      HAHAHAHAno. Thanks to the demon that is backwards compatibility browser vendors have implicitly or explicitly confirmed that they cannot actually revoke root certs. Or, more specifically, that many websites rely on that particular root to verify their identity and would break horribly if a root cert got revoked. i.e. revoking a misbehaving root will break the web.

      Why not? There have been roots that have been revoked due to being compromised and which have issued bogus certs (e.g. DigiNotar). That's caused some chaos, but people adapted.

      Sure, VeriSign is large and commands (either directly or through its subsidiaries) a substantial fraction of the CA market. Nuking it would be a Very Big Deal that browsers wouldn't take lightly, but I have no doubt that if it were shown that VeriSign (or Comodo, or other CAs) were found to be issuing bogus certs for the government to compromise people, they'd get their roots pulled by browsers. That's a death sentence for a CA, hence my skepticism in response to the proposal that they're actively assisting governments.

      A better solution would be the ability to provide multiple root certs, which is not technically feasible today, and won't be for a while - even things like SSL vhosts are considered unreliable due to the prevalence of legacy browsers that don't know how to use the proper TLS extensions for hostname identification. So maybe in 10 years we can start telling site operators that they can turn on multiple certs, and 10 years after that browser vendors will have enough data to determine if it's safe to actually revoke a root cert or not. In the meantime you will have to convince HTTPS services that it's worth paying n times as much in certification costs to avoid a hypothetical root revocation.

      Agreed. That would be nice.

    19. Re:https is useless by heypete · · Score: 1

      If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots. That's basically a death sentence to companies like VeriSign (rather, their cert-issuing division).

      I wouldn't be too sure of that.

      Of all the companies that have aided the NSA, how many are out of business or even really hurting?

      Companies like what? The ones making network-tapping hardware and whatnot cater toward a limited market, not the general public. Certificate authorities directly transact with server administrators, but their primary audience are end-users and they have wide public exposure. If a CA was found to be doing shady things, browsers would remove their roots. That'd basically kill off the offending CA.

    20. Re:https is useless by PopeRatzo · · Score: 4, Insightful

      If VeriSign gets caught issuing bogus certs for the government, browser vendors will revoke their roots.

      Hasn't history taught us that, "They wouldn't dare" is not something on which to base trust?

      I'm sure there was some dim bulb somewhere who believed, long ago, that AT&T "wouldn't dare" help the government spy on people because then all their customers would cancel their service.

      No, you've got to do better than, "I wouldn't think of doing such a thing" when it comes to 21st century governments.

      --
      You are welcome on my lawn.
    21. Re:https is useless by jedidiah · · Score: 2

      Security is fine if you are no one of interest. It doesn't matter if it's physical security or computer security. Once you are important enough for anyone to be interested in, most security measures are completely meaningless. This is just the harsh reality.

      For most of us, security measures just dissuade the opportunitistic idiot trying for an easy score with no particular interest in you as an individual.

      Once you've managed to attract unwanted attention, you will have to engage more serious security measures (in general).

      --
      A Pirate and a Puritan look the same on a balance sheet.
    22. Re:https is useless by grcumb · · Score: 1

      Eve? Is Bob cheating on Alice?

      Ah, she told you her name was Alice?

      You poor naive thing....

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    23. Re:https is useless by mysidia · · Score: 1

      were found to be issuing bogus certs for the government to compromise people, they'd get their roots pulled by browsers. That's a death sentence for a CA, hence my skepticism in response to the proposal that they're actively assisting governments.

      They might engage in this indirectly by CROSS-SIGNING an intermediate CA which the government would have control over.

      Verisign would then have plausible deniability, since the government agency produced all the required "audit papers" indicating compliance with the required policies.

      Nothing bad would happen to verisign --- at most some browsers would add the rogue government CA to the "Untrusted certificates list", and maybe some other root CAs would add the intermediate CA to their CRLs in order to invalidate the CA.

    24. Re:https is useless by pla · · Score: 3, Interesting

      unless we want to strip the state off their power to search us (and trail us).

      Dingdingding! We have a winner!

      Two and a half centuries ago we allowed the government those powers, under certain strict conditions, for the good of society as a whole. The government has repeatedly shown itself incapable of acting up to its side of that bargain. We The People therefore need to strip them of that power entirely. Can't find physical evidence of a crime without making my computer tell on me? Then It didn't happen.

      "But we need the government to have those powers to preserve the public order", you say? No. The sort of crimes the NSA catches (heh, I typed that as "commits" and had to correct it) have nothing to do with you and I in our daily lives. They protect megacorps and the government itself, and nothing else.

    25. Re:https is useless by grcumb · · Score: 2, Interesting

      Going to slashdot is safe? No SSL here.

      GCHQ has already spoofed Slashdot in the past. So no, going to Slash dot is not safe.

      If they want you, they can't get you?

      All right then. Let's all just roll over and die, why don't we?

      Look, I get your cynicism, but don't let it run to fatalism. There are things you can do:

      • - Stop making it easy on them. Stop using Windows. Seriously. Understand that what's convenient for you is often convenient for them.
      • - Stop using proprietary software at all. Yes, yes, HeartBleed nothing is safe bla bla bla. I'm not talking about safe, though; I'm talking about safer. And FOSS is, objectively, a safer environment, and will remain so even after it becomes popular.
      • - Start building and using federated, encrypted, decentralised, peer-to-peer systems. I honestly don't know why geeks didn't do this years ago, but why the fuck is Facebook the state of the art in social media? I mean, seriously. It's not only a privacy disaster area, it's a badly polished piece of shit to boot. We know that They don't like TOR because it's harder for Them. We know That they don't like bittorrent because it's harder for Them. So why the fuck are we not taking a clue from that and creating a UseNET we can go back to? I mean, I get why the peons don't, but we're geeks, for fuck sake. That used to mean something.
      • - Start re-imagining an internet whose physical characteristics resemble its protocols. At the outset, we thought it would be cool to have generic protocols that ran more or less transparently on any old network at all. What we didn't realise was that just because stupid networks were possible, that didn't mean they were inevitable. The whole ICANN/ITU fiasco is all the evidence we need to see that the world's telcos have begun to realise how much ground they've lost and they want it back. But that doesn't mean we have to give it to them. Mesh topologies using low-power devices are the only we we cut them back down to size.

      You can get all fatalistic if you like, but if your only response to the encroachments of authority is to run further and faster, then (apologies to Scotsmen everywhere) you're not a real geek.

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    26. Re:https is useless by Anonymous Coward · · Score: 0

      Sounds like your average mmorpg.

    27. Re: https is useless by Anonymous Coward · · Score: 1

      Eve is Bob, cheating on Alice.

      FTFY. This is how man in the middle works.

    28. Re:https is useless by Altrag · · Score: 3, Insightful

      What's inconvenient for them is often impossible for us. Try running most AAA games under Linux. A few will come with ports, and a few more will deliver a port 2-3 years later when nobody cares anymore. The vast majority are either Windows-only or Windows+Mac. Indie games tend to be somewhat better for this but most casual gamers just want the big name games.

      And it gets even worse in a business environment where you often have software restrictions imposed on you by corporate policy and frequently by the fact that you need to interact with vendors/customers who use Windows-only products.

      "Just stop using Windows" is a stupid catchphrase. Its like trying to end starvation by saying "just give them food." Actually its worse because food is a pretty good solution to starvation whereas its pretty unproven that FOSS software is "objectively" safer than closed software (I mean its probably true, but until Linux becomes a significant hacking target, we can't say definitively that the lack of exploits is due to better software rather than due to fewer people attempting to exploit it.)

      Similarly with Facebook. Its the "state of the art" in social media because of absolutely nothing to do with privacy protection. In fact a lot of its popularity was initially based on its _lack_ of privacy considerations -- "Facebook stalking" and such activities. I mean that probably wasn't the main driving factor (being fresh and simple right around the time that Myspace was bloating itself out of existing is likely the biggest contributing factor. I doubt FB would have gotten as big as it did if Myspace had stuck to being a site people actually enjoyed using rather than letting themselves be overrun by commercial interests.)

      And lastly protocols. Protocols are king. If TOR or similar ever comes out with a product that you can just install and "it works," then we might be getting somewhere. I mean "it works" as in it starts up with Windows, and immediately funnels all traffic through its own pipes and doesn't significantly impact the speed of watching a cat video on Youtube and basically in all ways stays the fuck out of the way. If it can get to that level, we might see some better adoption. As long as its something you have to consciously connect and disconnect and slows down your connection by 50% and whatever else, it won't pick up widespread adoption. Look how long its taking IPv6 to get off the ground and its got built-in support by every major OS and network equipment provider! (Disclaimer: I haven't used TOR myself in a few years so I don't know how close to this ideal its gotten.)

      At the end of the day, the real problem isn't Windows or lack of encryption or any other technical issue -- the problem is that 90% of the population doesn't care. Or I should say, doesn't care _enough_. We care enough to sign online petitions and shit that's easy to do in the hopes that someone who has more time on their hands will be able to make a difference (openmedia.ca up here in Canada is a great example of an organization that has taken the "enough" qualifier to heart and used online petitions to make significant changes in the way our government treats privacy and other online issues.)

      But on their own? Most people are too busy to worry about things that have a very low chance of ever impacting them directly. Its one thing for the NSA to tap a billion email accounts. Its another for them to filter through that data and pick targets. Yes everyone gets uppity when they pick a target wrong, but unless that target happens to be "me", most people have jobs and families and other things to do than worry about it for longer than it takes to exclaim "damned go'ment!"

      TL;DR: "just fix everything" is great in principle, pretty much impossible in practice.

    29. Re:https is useless by grcumb · · Score: 1

      TL;DR: "just fix everything" is great in principle, pretty much impossible in practice.

      Okay, so go back to the top of my post and read it again for my response to 'It's too hard.' :-)

      If you think that 'just fix everything' is what I'm saying, then you haven't even done me the justice of thinking about what I'm suggesting. I am saying that we geeks should know better, that we should do what we did in the 80s and 90s and turn our collective back on the well-trodden path and build our own internet, only this time with hookers and blackjack. Then I offered a few key suggestions about things we as geeks could fairly easily work on to move us in that direction.

      To assume that I simply want to snap my fingers and effortlessly get all that and a pony is to fundamentally misunderstand what it is to be a geek. We build things for ourselves. When things don't work the way they should, we change them.

      Now, I'm not suggesting you're not a True Geek (or Scotsman, for that matter). I'm just saying that if you're going to say 'too hard' about a situation such as this...

      ... No, fuck it. I am saying you're not a Real Geek :-)

      --
      Crumb's Corollary: Never bring a knife to a bun fight.
    30. Re:https is useless by mi · · Score: 1

      That is a discussion we should have.

      We should. But, unless you are going to suggest, the government ought not to have such powers at all (as pla argues below) — ever — then this is not the place for this discussion.

      Because if, in your opinion, sometimes they do legitimately need this capability, then they ought to remain able to circumvent https — without spooking the subject.

      --
      In Soviet Washington the swamp drains you.
    31. Re:https is useless by PopeRatzo · · Score: 1

      But, unless you are going to suggest, the government ought not to have such powers at all

      I'm suggesting that it should not be an inherent power of government. It's one they are granted when evidence is presented to a court for a warrant. In a public hearing.

      I'm pretty sure that the past decade has taught us that government does not respect this constitutional requirement. So, they should get a time out from those powers until they can demonstrate that they know how to behave. I would rather take my chances with the armies of terrorists and child molesters that we are constantly being told are invading our shores from Canada, or something, than with a government that believes they have the power to search (and tail) every single citizen because they think that's the most efficient way to catch a bad guy.

      So no, they should not be able to circumvent https until they've shown they can act responsibly.

      --
      You are welcome on my lawn.
    32. Re:https is useless by Altrag · · Score: 1

      I'm not sure which well-trodden path you're talking about.. the only significant change in "the internet" in the 80s and 90s was the introduction and popularization of the web, the latter of which really only gained ground when it became available out of the box with Win95. Sure there was AOL and Compuserv and whatnot but those weren't taken over by geeknet 0.1, they were taken over by easy access to Internet Explorer.

      And yes, "we" as geeks should and mostly do know better.. that's why things like TOR exist in the first place. But while geeks accounted for 90+% of the internet population back in 1991, the opposite is true now. If you're content limiting yourself to whatever content is available through TOR, whatever games and business software are available through Linux, etc, then power to you. I applaud your ability to stick to your ideals!

      But here in the real world where the rest of us live, there exist motivations beyond "will this ban me from the True (or Real?) Geek club"?

      You're absolutely correct about me though. I am not a True Geek, a Real Geek, nor even a Scotsman. I used to be one of the former (or at least much closer to it) to back when I had more free time and less life experience. Things change. Priorities change.

      Should people practice computer safety? Absolutely. Web admins in particular should turn on https by default since there's no reason not to unless you're intentionally being shady.

      Should people practice computer safety to the exclusion of their ability to do their jobs, websites they like that don't have https support or whatever else they do? Can't say I agree with that, even for geeks. Its just so incredibly beyond overkill that its not even funny.

      I'm not saying we shouldn't aim for end-to-end security, and I'm definitely not saying that geeks won't be the ones trying to pave the way. I AM saying that until there's a significant content saturation under whatever solution they come up with, that its unrealistic for most people -- even geeks -- to completely shut out the existing systems.

      Oh and just to be really pedantic, since the article is about injection attacks, there's absolutely nothing stopping the injections from being done directly at Youtube -- except Google's objections -- so https is at best only reducing the problem, not eliminating it. The only way to be 100% secure online is to unplug your internet connection and never plug it in again. But that kind of defeats the purpose.

    33. Re:https is useless by mi · · Score: 1

      It's one they are granted when evidence is presented to a court for a warrant. In a public hearing.

      That's not how things are spelled-out in the Constitution. And it does not make any sense. A public hearing will alert the suspect.

      I'm pretty sure that the past decade has taught us that government does not respect this constitutional requirement.

      No, we've known it for much longer.

      So, they should get a time out from those powers until they can demonstrate that they know how to behave.

      They are not children, to whom such an approach may be applicable. Nor will the criminals be willing to join the "cease-fire" you propose... Bad as government's intrusions into privacy are, they have neither killed nor raped many people.

      Not even the scariest abuses — when police get a "hint" obtained with unwarranted search and perform "parallel reconstruction" — have targeted innocent people. Not yet. The time will surely arrive, but for the time being it is the IRS — not the NSA — that is used to suppress opposition. Them and the government's power to audit . But not the eavesdropping.

      We have the Constitution, we just need the government to obey it. The previous President was often accused of "shredding" the document, but the current one is actually doing it.

      In other words, we have the laws already — we just aren't following them. Creating new laws will not help that...

      I would rather take my chances with the armies of terrorists and child molesters

      How about fraudsters, thieves, rapists and murderers, embezzlers of public funds and bribe-takers? I don't think, I'm willing to have even a 10% higher rate of those things in exchange for unbeatable https.

      --
      In Soviet Washington the swamp drains you.
    34. Re:https is useless by Anonymous Coward · · Score: 0

      - Stop making it easy on them. Stop using Windows. Seriously [imagicity.com]. Understand that what's convenient for you is often convenient for them.

      10,000 Linux servers hit by malware serving tsunami of spam and exploits
      Kernel.org Linux repository rooted in hack attack

      Those stories must be a lie and they were really running Windows, right? Oh and there are plenty of other examples to be found.

      - Stop using proprietary software at all. Yes, yes, HeartBleed nothing is safe bla bla bla. I'm not talking about safe, though; I'm talking about safer. And FOSS is, objectively, a safer environment, and will remain so even after it becomes popular.

      Open SSL has not only Heartbleed but CCS Injection Vulnerability and many more vulnerabilities, GnuTLS & Apple's SecureTransport (yes it is "free software") had the goto fail problem, Debian OpenSSL with broken entropy generation and predictable keys, Android's SecureRandom using weak entropy for it's PRNG, etc. The list really can go on and on and on.

      We know that They don't like TOR because it's harder for Them.

      It is?

      FBI Admits It Controlled Tor Servers Behind Mass Malware Attack

      The FBI Is Infecting Tor Users with Malware to Catch Kiddie Porn Creeps

      Tor security advisory: "relay early" traffic confirmation attack

      The US government agencies have unlimited resources to run Tor exit nodes and to write malware to infect people who use Tor.

      Hopefully no one actually listens to your stupid advice.

    35. Re: https is useless by Richy_T · · Score: 1

      Alice, what's the matter?

    36. Re:https is useless by Richy_T · · Score: 1

      It's the wrong question anyway. We shouldn't be trusting arbitrary third parties (Verisign, Thawte etc) to validate who we should trust. This has always been the case. This government stuff has just thrown it in the spotlight.

      The violations of the constitution are pretty bad in themselves, however.

    37. Re:https is useless by hairyfeet · · Score: 1

      how to write a Linux virus in 5 easy steps using the exact same tricks used to infect Windows. Say that is only hypothetical? How about some real world pwning like kernel.org and its not a fluke by any means. Oh and what happens when the "secure" Linux kernel gets used by a target worth hitting? A million plus infected systems that is what.

      Linux "security" is security by obscurity, simple as that. The "many eyes" myth was proven false by Heartbleed which sat there for fricking years without being caught, the ONLY advantage having the source gets you is the ability to keep old versions alive after the devs move on....that's it,that's all. Hell by the time one was to do even a piss poor code audit of even a tenth of a single distro release it would have been abandoned for 5+ NEW releases that your audit wouldn't cover, see how Ubuntu is on track to have 20 mainstream releases in the same support window as Win 7 for example.

      Source code isn't magic and considering how many thousands of people work on the code that goes into a single distro sticking a state actor in the mix would be trivial if the state desired it.

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

      Alice? Alice?! Who the fuck is Alice?!

    39. Re:https is useless by Anonymous Coward · · Score: 0

      As i understand it, Google has placed a Revocation backdoor in Chrome.
      (No Firefox addon will save you when in Chrome. duh)

      More details on Revocation, from people that *knows* security,
      https:grc.com/revocation/crlsets.htm

    40. Re:https is useless by IamTheRealMike · · Score: 1

      No, you've got to do better than, "I wouldn't think of doing such a thing" when it comes to 21st century governments.

      Alright. What do you propose?

      Fundamentally, encrypting all traffic all the time requires a public key infrastructure and the only way we know how to build one that works is to have trusted third parties. You trust your browser, for example. Your browser maker outsources ID verification of websites to CA's.

      Ultimately SSL cannot survive being explicitly banned or subverted by the state. It just can't. They can force browser makers to give them a back door. No system can survive explicitly being banned by the state. Luckily this has not (yet) happened - strong SSL is not illegal and there are no documents in Snowden's archive that discuss compromises of CA's, probably because when armed with a bunch of zero days you don't need to exploit a CA to strip SSL, you just infect the target. Much more stealthy.

      What's more, Google is pushing certificate transparency forward quite hard. CT is a system that requires certificates to be published to an audit log for a browser to accept them. It should make it much harder for a CA to issue certificates in secret. The audit logs can be data mined to look for bogus certs, e.g. certs that are issued but never show up in production usage, either by big well known targets like Google or by third parties. So far it's the best proposal that exists for how to raise the security of SSL. All others are busts.

    41. Re:https is useless by advocate_one · · Score: 1
      "browser vendors will revoke their roots."

      Oh come on who are these "browser vendors"? Microsoft (definitely in the NSA's pocket), Apple, yup owned... Google? definitely owned as well... Mozilla? one is also left wondering about them as well... Opera?

      at least with Firefox, we have source code...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    42. Re:https is useless by currently_awake · · Score: 1

      Modern society is based on trust. You trust the bridge you drive over to get to work won't fall down and kill you. You trust the brakes on your car will work. You trust the phone company to connect you to the police when someone breaks into your house. You can't live without trust. The issue isn't trust, it's how to enforce trust on fallible humans.

    43. Re:https is useless by Richy_T · · Score: 1

      It's who you trust. I really known nothing about Thawte and Verisign and the however many it is CAs in the browser now (do you?) and one instance of lapse of trust from them (which has happened) and you're screwed. It's really just the wrong infrastructure and implementation.

    44. Re: https is useless by Anonymous Coward · · Score: 0

      Bob gets to be between Alice and Eve? I wanna be part of that man in the middle thing....

    45. Re: https is useless by snowsnoot · · Score: 1

      Isnt DNSSEC supposed to solve this problem (and put the CAs out of business)?

    46. Re:https is useless by PopeRatzo · · Score: 1

      How about fraudsters, thieves, rapists and murderers, embezzlers of public funds and bribe-takers?

      Where do you live, the Barbary Coast?

      I don't think, I'm willing to have even a 10% higher rate of those things in exchange for unbeatable https.

      OK, so I am willing to have a 10% higher rater of those things in exchange for unbeatable https and a government that has much stricter controls over it's police powers.

      You must love the militarization of local police, all the masked and camouflaged cops driving Lenco BearCat's with .50's mounted on top. As long as you're not doing anything wrong, you have nothing to worry about, right, comrade?

      --
      You are welcome on my lawn.
    47. Re:https is useless by PopeRatzo · · Score: 1

      No system can survive explicitly being banned by the state.

      Then we need to see if the state can survive banning privacy.

      --
      You are welcome on my lawn.
    48. Re:https is useless by strikethree · · Score: 1

      Eve? Bob? Band of Brothers was destroyed in Eve years ago now. Stay up to date.

      --
      "Someone needs to talk to the tree of liberty about its ghoulish drinking problem." by ohnocitizen
    49. Re:https is useless by AaronLS · · Score: 1

      1. AC said SSL is magic, implying that they believe it is a hoax. I am simply pointing out they are an idiot who understands nothing about cryptography.
      2. Saying that someone has identified a potential weakness in a cryptography algorithm doesn't change the fact that it is deterministic and well understood among cryptography experts. There is still nothing magic about it.
      3. Your rebuttal implies that I was trying to claim that the NSA was innocent in some way or defend them. Obviously you have the worst reading comprehension in the history of mankind because no where in the two sentences do I make any such claim.
      4. There are documents that indicate NSA was looking for potential weaknesses in various security protocols and possibly tampering with devices, but there is no evidence that they influenced the SSL standard itself to introduce weaknesses. Tampering with a device to break its implementation of SSL is seperate concept from the SSL standard itself. Could they have influenced the standard? They could be powering their headquarters with goat fetuses for all we know. It's all wild speculation in the absence of evidence. All evidence points to them pouring large amounts of manpower and computing power into breaking SSL. If they did indeed influence the standard, then whatever influence that had had no negligible effect based on what we know of the kind of efforts they've had to throw at SSL. Evidence of their efforts doesn't show any significant success. Their only successes in any relation to SSL have been more traditional techniques that involve circumventing SSL, such as compromising a server so they can capture data before it is encrypted, since SSL is such a tough nut to crack. More evidence that they haven't cracked SSL. Besides, influencing the standard in that way would have required more foresight than most governments are capable of.

      Only one point is needed to show you're an idiot. The evidence is overwhelming.

    50. Re:https is useless by Noah+Haders · · Score: 1

      Are we good? See below:

      http://www.reuters.com/article...

      SAN FRANCISCO (Reuters) - As a key part of a campaign to embed encryption software that it could crack into widely used computer products, the U.S. National Security Agency arranged a secret $10 million contract with RSA, one of the most influential firms in the computer security industry, Reuters has learned.

      Documents leaked by former NSA contractor Edward Snowden show that the NSA created and promulgated a flawed formula for generating random numbers to create a "back door" in encryption products, the New York Times reported in September. Reuters later reported that RSA became the most important distributor of that formula by rolling it into a software tool called Bsafe that is used to enhance security in personal computers and many other products.

      Undisclosed until now was that RSA received $10 million in a deal that set the NSA formula as the preferred, or default, method for number generation in the BSafe software, according to two sources familiar with the contract. Although that sum might seem paltry, it represented more than a third of the revenue that the relevant division at RSA had taken in during the entire previous year, securities filings show.

  3. Reduced rights by SQLGuru · · Score: 2

    This is one of the reasons that I don't use an admin/root level account for normal activity. If I need those privs, I'll escalate my rights for a single action. While that also won't prevent all hacks, it drastically reduces my exposure.

    1. Re:Reduced rights by vux984 · · Score: 2

      This is one of the reasons that I don't use an admin/root level account for normal activity.

      A good practice to be sure.

      While that also won't prevent all hacks, it drastically reduces my exposure.

      Well, at least your device drivers are safe, and its a little harder for you to join a bot net.

      But pretty much everything you have of value can be accessed from user space, including all your documents. That's generally what identity and data thief hackers (and state actors) want.

    2. Re:Reduced rights by SQLGuru · · Score: 1

      They also have a harder time installing executable code.....if my browsing user can't install code, then they've only got memory to play with.

    3. Re:Reduced rights by Anonymous Coward · · Score: 0

      The attacks are designed to hack non-privileged accounts and escalate them into root level access which is the norm. I'm sure the malicious code doesn't even care if the account is an admin/root level to begin with. If anything you're probably increasing your exposure by using a non-privileged account.

    4. Re:Reduced rights by vux984 · · Score: 1

      not entirely true. It just can't install it in c:\program files or your platforms equivalent. It can drop executables in folders you DO have access to though, and run them from there. And even get them to auto run if it puts the start command in a settings file you can edit as that user.

    5. Re:Reduced rights by Anonymous Coward · · Score: 0

      There are thousands of privilege escalation exploits for Linux. Nobody needs root anymore.

    6. Re:Reduced rights by MightyMartian · · Score: 1

      Well, there have been a whole host of attacks associated with vulnerable versions of Flash and Java that could at least cripple a profile. I ran up against one of them around 2010. One of the staff at one of our remote locations suddenly had all their files supposedly disappear, desktop wiped out and the like, and a notification about a ransom if they wanted the files back. The user had no admin privileges, so I checked, and sure enough, the other profiles were untouched. What had happened is the auto updater for the workstation had failed.

      Now, while it's true that the operating system itself was not compromised, and no other systems or users on the network were compromised, certainly there was enough control to potentially view confidential data on shared drives. While this was relatively unsophisticated ransomware, it did teach me than merely obsessing about privilege escalation does not lead to a secure system. User profiles and directories can still potentially be vulnerable even if the malware can't root the system.

      --
      The world's burning. Moped Jesus spotted on I50. Details at 11.
    7. Re:Reduced rights by Anonymous Coward · · Score: 0

      So why is no one actually exploiting them?

    8. Re:Reduced rights by TechyImmigrant · · Score: 1

      What makes you think that they aren't?

      --
      I should use this sig to advertise my book ISBN-13 : 978-1501515132.
    9. Re:Reduced rights by sqlrob · · Score: 1

      A shell / powershell script is plain text.

    10. Re:Reduced rights by Anonymous Coward · · Score: 0

      In that same principle, you should do all your work on an iOS or unrooted Android device, where sandboxing is mandatory and applications have no access to other applications' data outside of very restrictive sharing channels. Privilege separation on modern operating systems was designed to isolate users in a multi-user environment, not to isolate a user from potentially malicious software. The latter requires ubiquitous sandboxing.

    11. Re:Reduced rights by AmiMoJo · · Score: 1

      Run your browser in a VM, preferably using a different OS to the host. No access to the host filesystem, isolated from the real machine. Then at least only your browser data is vulnerable.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    12. Re:Reduced rights by Anonymous Coward · · Score: 0

      Until they break into the virtualization software . . .

    13. Re:Reduced rights by SigmundFloyd · · Score: 1

      Run your browser in a VM, preferably using a different OS to the host. No access to the host filesystem, isolated from the real machine.

      Simply chroot the browser, no?

      --
      Knowledge is power; knowledge shared is power lost.
    14. Re:Reduced rights by Richy_T · · Score: 1

      Android actually uses standard Unix rights to do its separation. I wonder how hard it would be to apply that to a more regular Linux install. It would mean effectively turning it into a single user system, of course (though there may be a way to make it limited multi).

    15. Re:Reduced rights by jhantin · · Score: 1

      A shell / powershell script is plain text.

      Well then, the obvious solution is to disable #! recognition and set-executionpolicy restricted, so shell scripts become useless! ... then watch as everything grinds to a screeching halt.

      Oh well, back to the drawing board.

      --
      ...when you're writing a game...tweak the difficulty of "Easy" to something [your mother] can cope with. -- onion2k
  4. In the crypt by Impy+the+Impiuos+Imp · · Score: 1

    Interesting. Unencrypted command-and-control channels embedded in the commnications of custom application communication.

    Next up: Buffer overruns and similar by violating the same stream or data stream.

    --
    (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
  5. I'd love to use https! by XanC · · Score: 5, Interesting

    ...So why does Slashdot redirect HTTPS back to HTTP??

    1. Re:I'd love to use https! by Anonymous Coward · · Score: 5, Informative

      because slashdot is not run by tech people anymore, its just a large ignorant media conglomerate that cares not for it users until it starts to affect the bottom line.

      Besides enabling https could take minutes of labor time from literally ones of administrators to implement that's not free you know

    2. Re:I'd love to use https! by Anonymous Coward · · Score: 0

      So they can ignore your nobeta=1 url.

    3. Re:I'd love to use https! by Anonymous Coward · · Score: 2, Interesting

      Simplicity and overhead.

      HTTPS has overhead in encrypting all content. This can be mitigated by processors with AES instruction set, but it still impacts the scalability for the site. Most content on slashdot can probably be cached and thus CPU usage is kept to a minimum as users scale.

      Staying in HTTPS but requesting HTTP resources has to be done carefully to avoid browsers from throwing cross domain violations. It's more trouble than it's worth.

      No one with the know-how and resources to capture your slashdot HTTP cares what inane comments you are making or what you're reading. I'm sure some kooks think otherwise, but the government has bigger fish to fry. The HTTPS is used for critical steps, such as logging in to prevent accounts from being compromised.

    4. Re:I'd love to use https! by Anonymous Coward · · Score: 0

      Well, because this is how they can use "network injection appliances" to target and intercept your unencrypted /. traffic and replace it with malicious /. beta code that makes ... well, I seriously don't know why somebody would do something this bad.

    5. Re:I'd love to use https! by Anonymous Coward · · Score: 0

      After logging in, your browser tells the website who you are via cookies which can be intercepted over an unencrypted connection to impersonate you and steal your data and probably change your account password and email address. The truth is that what protects you is people's lack of interest. Using HTTPS exclusively for logging in is a useless practice.

    6. Re:I'd love to use https! by AvitarX · · Score: 1

      It protects from password re-use attacks.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    7. Re:I'd love to use https! by choprboy · · Score: 1

      Staying in HTTPS but requesting HTTP resources has to be done carefully to avoid browsers from throwing cross domain violations. It's more trouble than it's worth.

      I think that is the real crux... I was stunned to recently see that, in a completely clean browser, just going to the Slashdot root page loads 45 third-party domain cookies. That is excluding slashdot.org and dice.com properties....

    8. Re:I'd love to use https! by Anonymous Coward · · Score: 0

      Because Slashdot is trying to intercept your communications and inject your browser with malware.
      Everybody else is using HTTPS except Slashdot.

    9. Re:I'd love to use https! by Anonymous Coward · · Score: 1

      Did you forget that sites like Slashdot were spoofed/emulated to feed malware? Who gives a fuck about the comments, make it a bit harder for anyone to just inject code.

    10. Re:I'd love to use https! by tepples · · Score: 1

      Someone who hijacks your session identifier from a cleartext cookie can change your password.

    11. Re: I'd love to use https! by AvitarX · · Score: 1

      But they don't have the password to other sites, of the password is reused (as most are). It limits the compromise to a single site.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
  6. Problem solved. by nimbius · · Score: 1

    https everywhere. https://www.eff.org/https-ever...
    and for those of you wondering why slashdot redirects to http, it could be any number of conspiracy theories but the most obvious: a BigIP appliance controls ssl handoff and they dont have the licenses for every freaking connection.

    --
    Good people go to bed earlier.
  7. Flash vulnerability? by Animats · · Score: 3, Interesting

    Presumably this attack is via a Flash vulnerability. So why is there no mention of Adobe in the article? Why isn't Adobe being held responsible? Why are there still vulnerabilities in Flash? Who audits that code? Well?

    1. Re:Flash vulnerability? by Anonymous Coward · · Score: 0

      Whoa, hang on a second...youtube has changed back to Flash?

      WTF, when did this happen?

      Why did they change from HTML5?

      I need to check this out......

      *comes back from youtube*

      You sir, are incredibly misinformed.

    2. Re:Flash vulnerability? by Animats · · Score: 2

      Didn't look at the source of a Youtube page, did you? Look for "http://s.ytimg.com/yts/swfbin/player-vflZsDuOu/watch_as3.swf". Videos can also play with "HTML5 video", but there's Flash code there to be executed.

    3. Re:Flash vulnerability? by timeOday · · Score: 4, Informative
      No, I don't think it's a Flash vulnerability. It is awfully obscured in the article by general hand-waving, but I think the idea here is to trick people into installing an executable that isn't really Flash by causing an executable that presents itself as a Flash update to request installation. Since this happens while they are visiting youtube (with a man-in-the-middle doing the injection), the user may assume it is a legit update and install the malware.

      In other words, Flash and Java are "exploited" only in the sense that people are so used to being pushed security updates, that they may accept a fake update delivered on an insecure connection. Accepting a so-called Flash update from any untrusted site would accomplish the same thing. It really just boils down to the fact that every site is an untrusted site if you're not using https, since you don't know who all is in the middle.

    4. Re:Flash vulnerability? by Animats · · Score: 1

      It is awfully obscured in the article by general hand-waving...

      Agreed. Anyone know what kind of exploit this is?

    5. Re:Flash vulnerability? by onproton · · Score: 5, Informative

      From the article: "A step-by-step breakdown of how such an attack might occur is as follows: 1. A target is selected and their name is entered into the Network Injection GUI. 2. The target’s traffic stream is located based on their ISP’s RADIUS records. 3. As per the rule on the network injector (as shown in Figure 14), the appliance waits for the target to visit YouTube. 4. When this traffic is identified, it is redirected to the network injection appliance. 5. The legitimate video is blocked and malicious flash (SWF) is injected into the clear-text portion of the traffic. (Represented by the kitty skull and cross bones.) 6. The target is presented with a dialogue to upgrade their flash installation. If this upgrade is accepted the malicious SWF enables the installation of a ‘scout agent’ which provides target validation. 7. If the target is assessed as correct (i.e., the desired person), and safe for install (not a malware analysis honeypot), then the full agent is deployed. 8. Surveillance of the target commences."

    6. Re:Flash vulnerability? by Anonymous Coward · · Score: 0

      So you still need to make a dumb decision for this to work.

      So much for not being safe from this if you know what you're doing.

      I'm sure there are ways to infect without user interaction but this example isn't it.

    7. Re:Flash vulnerability? by ayesnymous · · Score: 1

      Barton Gellman says it is a Flash vulnerability in this Washington Post article: http://www.washingtonpost.com/...

  8. HTTPS may not be secure either by Anonymous Coward · · Score: 1

    I've seen a lot of web tracking bugs inserted into https traffic coming from unencrypted sources.

    This is in major US companies too. Ebay, Paypal, Microsoft, etc. So, either these companies are dropping it in, or the https is being proxied somewhere.

    1. Re:HTTPS may not be secure either by The+MAZZTer · · Score: 1

      This is why your browser will NOT display the green lock if a HTTPS pages references HTTP resources.

    2. Re:HTTPS may not be secure either by ArcadeMan · · Score: 1

      That's why I only use HTTPSOS.

    3. Re:HTTPS may not be secure either by zlives · · Score: 1

      the article talks about state actors with physical access to ISP's... i don't think https is going to protect anyone that is target in such a manner.

  9. All the more reason-- by wierd_w · · Score: 2

    Really, revelations like this are all the more reason to run a fully rom based OS for anything touching the internet.

    Before somebody says something absurd, this is basically what a thin client does anyway. The difference is that you keep the system image inside the thin client itself, rather than pulling it from the network. A modified chromebook would work just fine. An sdcard slot that is hardware designed to be electronically incapable of raising its line voltages to write-enable levels, while still being physically accessible by the owner, would round out the package for where to store the system image.

    Everything else is stored exclusively in RAM, and blanks completely on power off.

    If the user WANTS persistent data, they can use external media. it comes in quite acceptable sizes these days.

    This could very easily be done with a chromebook with some simple modifications. Instead of doing google chrome, pack it with a squashfs knoppix image.

    watch all the seditious cat videos you want.

    1. Re:All the more reason-- by El_Oscuro · · Score: 1

      I once had a computer which did that, a Commodore 64. I am pretty sure most others at that time were that way too. The whole "store the O/S on a R/W hard drive" was an IBM PC/Microsoft idea, as were viruses.

      A ROM based system with Ubuntu or Knoppix would be pretty sweet for surfing teh Interwebs.

      --
      "Be grateful for what you have. You may never know when you may lose it."
    2. Re:All the more reason-- by Anonymous Coward · · Score: 0

      An sdcard slot that is hardware designed to be electronically incapable of raising its line voltages to write-enable levels

      It's not that easy anymore. Instead if having a dedicated Write Enable line, SD cards use a packet based communications protocol, with (among others) read and write commands. To disable writes, you'd need a controller that acts like a firewall. If you want a dedicated Write Enable line, try Compact Flash, which is basically the "good old" parallel IDE.

    3. Re:All the more reason-- by Anonymous Coward · · Score: 0

      "I once had a computer which did that, a Commodore 64. I am pretty sure most others at that time were that way too. The whole "store the O/S on a R/W hard drive" was an IBM PC/Microsoft idea"

      You might want to check who made the environment the C64 booted into: http://en.wikipedia.org/wiki/Commodore_BASIC

    4. Re:All the more reason-- by wierd_w · · Score: 1

      That would work too, but getting your hands on CF cards is getting harder and harder, and so is the likelihood that end users will have a card reader capable of using them.

      Chromebooks dont use CF.

      This does throw a nasty little wrinkle in.
      we would need a custom SD card ASIC that purposefully does not accept writes, and does not have any code inside its firmware to facilitate writes.

      That's gonna make it significantly more expensive though.

      there's a possible alternative though, but it still requires custom hardware fab. A filter sleeve.
      It does a man-in-the-middle between the actual sdcard and the sdcard slot. it allows read requests through, but denies write packets. It instead lies, and says a write was denied, emulating the behavior of the write protect notch on the sdcard logically to the controller, while actively also prohibiting the write from getting through at all. The ideal form factor here is in the "SDHC to microSDHC adapter sleeve" format. Sits inside a real SDHC slot, accepts microSDHC, but strictly enforces write protection.

  10. Pure FUD by Anonymous Coward · · Score: 0

    fear, uncertainty, doubt. that's all this story has to offer.

  11. I must be missing something by K.+S.+Kyosuke · · Score: 1

    How is HTTPS going to protect me against this? It doesn't solve the problem of holey network-facing applications.

    --
    Ezekiel 23:20
  12. Not wrong, or stupid, or insecure, just run Flash by raymorris · · Score: 1

    TFS says:
    > many otherwise well-informed people think they have to do something wrong, or stupid, or insecure to get hacked—like clicking on the wrong attachments, or browsing malicious websites...many of these commonly held beliefs are not necessarily true. ... [Adobe Flash can be exploited by an ISP].

    Hmm, so you don't have to do something stupid or insecure, just run Flash and Java. :)

    Flash is mostly used for ads and malware, neither of which I want, so I don't run Flash in my default browsers. For many years, there has been precisely one site for which I ever had any interest in having Flash installed, that was Youtube. Not anymore. Youtube no longer requires Flash. https://www.youtube.com/html5

  13. This is just evil. by Anonymous Coward · · Score: 0

    So how does this work? Do you get a black box with the words "Please type 'Windows-R, cmd[enter], net user nsa foobar /add, net localgroup administrators nsa /add' before you can watch your cat video."? In other words, there has to be a bug on the client that lets the web page run arbitrary code, in which case the solution is to patch your damn system.

  14. Simpler way: virtualization + snapshot by raymorris · · Score: 2

    You COULD modify the hardware etc., or just fire up Virtualbox, KVM, or qemu full screen for your web browsing and such. Set the virtualized image read-only, except when installing new software on it.

    Beneath the virtual machine can either be a dedicated hypervisor or an very small Linux installation which has only a tiny attack surface.

    1. Re:Simpler way: virtualization + snapshot by Anonymous Coward · · Score: 1

      Set the virtualized image read-only, except when installing new software on it.

      And hope you don't have to do a page swap, or have any applications that need to write temporary files. You'll also have to be okay with the performance hit from downloading *everything* from every site you visit every time you visit, since the browser cache won't exist. To get around that, I suppose one could set up a set of RAM disks mapped to the appropriate paths if there is enough memory available in the VM, but those would only exist for the current session and would get wiped out each time the VM was shut down.

    2. Re:Simpler way: virtualization + snapshot by raymorris · · Score: 1

      > I suppose one could set up a set of RAM disks mapped to the appropriate paths if there is enough memory available in the VM, but those would only exist for the current session and would get wiped out each time the VM was shut down.

      Yep, that's generally how you do it. As the title of my post suggests, you can also use on-disk snapshots for that, so again any altered files are reset on reboot. Reboot can take only seconds because many of the OS disk blocks are cached in host RAM. Live CDs have those paths all worked out and you can customize from that basis. Even simpler, you CAN just run a live CD directly. CD-R is physically read-only after it has been burned, so you can be certain that no malware or hackers have modified your system.

  15. Tax Rebate by CanHasDIY · · Score: 2

    state actors involving "network injection appliances" installed at ISPs.

    So, since we're being charged by the bit now, and the government is taking my bits (that we pay for) off the pipe and replacing them with their bits (that we also pay for)... wouldn't that imply that these "state actors" should be on the hook for at least part of our ISP usage bills?

    --
    An enigma, wrapped in a riddle, shrouded in bacon and cheese
  16. Re:Not wrong, or stupid, or insecure, just run Fla by Anonymous Coward · · Score: 0

    just wait till backdoors get installed in your fancy html5 browsers.... or the network card firmware and OS and something that gets logged as a malformed packet triggers an automatic installation of government spyware... pre loaded in the hardwares memory

    netgear doesn't need to advise it's customers and if they manufacture oversease there is plausible deniablity from both our government and the manufacturer.

    more likely China gets $$ and trade for pulling shit like that already

  17. Corrected story :) or maybe :( by davidwr · · Score: 1

    $FUTURE_DATE: Citizen Lab released new research today on a targeted exploitation technique used by state actors involving "network injection appliances" installed at ISPs and with the possibly-coerced "cooperation" of https: web sites or the companies issuing https: certificates. These devices can target and intercept encrypted YouTube traffic and replace it with malicious code that gives the operator control over the system or installs a surveillance backdoor. One of the researchers writes, "many otherwise well-informed people think they have to do something wrong, or stupid, or insecure to get hacked - like visiting an unencrypted web site, ...many of these commonly held beliefs are not necessarily true." This technique is largely designed for targeted attacks, so it's likely most of us will be safe for now - but just one more reminder to not trust the person on the other end to not cooperate with The Man in the middle. It is unknown how long such attacks have been happening but they might date to 2014 or earlier.

    --
    Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
  18. weird headline by Anonymous Coward · · Score: 0

    So... https will protect me while watching cat videos?

  19. Its ok by Anonymous Coward · · Score: 0

    I don't watch cat videos. :-)

  20. One reason I use.... by Anonymous Coward · · Score: 0

    ...OpenDNS. I bypass my ISP all together when it comes to getting web content using their DNS. Hopefully OpenDNS doesn't ever get hacked of course but since they deal with security, they are better on top of things then most IPSs are when it comes to DNS lookup injection issues. :)

    1. Re:One reason I use.... by Anonymous Coward · · Score: 0

      Might help more if you don't use your ISP's infrastructure at all.

  21. Just one more reminder to use https? by lippydude · · Score: 1

    "This technique is largely designed for targeted attacks, so it's likely most of us will be safe for now — but just one more reminder to use https."

    Except if the local proxy is designed to intercept https traffic and replace the senders digital signature with its own. ref

  22. Targeted exploitation technique? by lippydude · · Score: 1

    Will this targeted exploitation technique work if the target isn't Microsoft Windows ©

  23. Certificate Patrol by DrYak · · Score: 2

    I believe there is a plug-in for Firefox that alerts you when certs change too.

    Certificate Patrol is an example of such extension.

    It does detect strange changes in certificate authority (for exemple when a Man-In-Middle attacker is using a bogus certificate signed by rogue CA or by stolen keys from some CA).
    It also detect un-called-for changes in certificate (for exemple, the actual authority has been coerced by the government to sign their spy-server keys, and thus you get a new legit-looking certificate, even if the old hasn't been revoked and and is still well within its validity range)

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Certificate Patrol by Anonymous Coward · · Score: 0

      Well I have it running and the certificates change multiple times a month. So it's hard to know if it's just google jumbling things around or if I get spied on..

      I'm probably spied on on several occasions because I take some effort to avoid being tracked and try to preserve my privacy, but then they have a lot of work digging through all this traffic.

  24. chroot is for cross-compiling, not security by raymorris · · Score: 1

    It's trivial to step out of chroot. Chroot was not designed for security. It's very similar to cd and getting out basically consists of making a symlink and doing cd. Chroot is for cross-compiling, installing grub, etc. - changing the DEFAULT. value of / that your session uses.

    AMD's virtualization is much more appropriate for security, as it's designed to make it such that a guest can't even KNOW whether it's a guest or not, much less escape and access the host system.

  25. ftfy by raymorris · · Score: 1

    it's just a large ignorant media conglomerate that cares not for its AUDIENCE

    FTFY

  26. Clearly by fyngyrz · · Score: 4, Interesting

    Java and so forth is not limited enough. Not even close. And outside of that, there's the whole "ooops, the bug let some code execute" that will plague browser-side executables forever, or as close to it as makes no difference.

    This is one of the core (ha) problems with client-side execution in a general purpose machine.

    If you want to host a reputable website, then the more you can put active functionality for the user in server-side CGI, the better you can actually take that high road. All this java-loaded stuff on websites is a constant invitation to problems. It's an idea that is only safe in a world without bad guys. And our world is hardly that -- even the ones that are supposed to be the good guys (the government) are bad guys now.

    But if you can tell your users "turn off client side execution" and your website will still work, then all they need is a browser that can read HTML, CSS and CGI and follow the HTTP and HTTPS protocols. Then if you can get browser manufacturers to quit pretending that HTTPS provides "identity" so the browsers drop the SCARE tactics for self-signed certificates, we can all enjoy the web without nearly as much risk for the surfer or paid blackmail for the site owner.

    For all of us who remember how to read and enjoy real web sites, this would just be another (good) day. On the other hand, if you're one of those who doesn't read, likes to type "tl;dr" (and thinks it's funny, instead of sad as heck) and/or one of the video-addicted, you're probably completely screwed. :)

    --
    I've fallen off your lawn, and I can't get up.
    1. Re:Clearly by Anonymous Coward · · Score: 0

      I had a hard time reading this, and may even agree with what you are saying, if it wasn't an odd feeling that you are confusing Java and JavaScript. I keep thinking, that still happens these days?

    2. Re:Clearly by Anonymous Coward · · Score: 0

      Java?

    3. Re:Clearly by tepples · · Score: 1

      then the more you can put active functionality for the user in server-side CGI, the better you can actually take that high road.

      True, in the future, it'll become feasible to just stream web applications over the Internet using something like RDP, VNC, or OnLive. But in the present, the latency and monthly transfer cap of satellite and cellular Internet makes that impractical.

      Then if you can get browser manufacturers to quit pretending that HTTPS provides "identity" so the browsers drop the SCARE tactics for self-signed certificates

      What's wrong with identity? Without identity you can't be certain that a man in the middle isn't changing your traffic on the way in. If it's the cost, you can always get a certificate for a personal site without charge from StartSSL.

    4. Re:Clearly by JBdH · · Score: 1

      cgi, really?

    5. Re:Clearly by fisted · · Score: 1

      Do not you understand what CGI is, son? Protip: It's not Computer Generated Imagery in this context.

    6. Re:Clearly by Anonymous Coward · · Score: 0

      "Government" "good guys"????????

      The government hasn't been the good guys since, well, EVER. They've been people who want power over everyone else since time immemorial. From the thugs who ruled by club in the caves to the "divine right of kings" to current authoritarians who "know better and want to rule for our own good".

      For a century those in the US had limits on these power-hungry authoritarians, but nowhere in the world now are the authoritarians limited (crony-capitalists, fascists, socialists, communists, dictators, etc). There may be the "useful idiots" among them, but they are just that, idiots.

    7. Re:Clearly by fyngyrz · · Score: 1

      I said they were "supposed" to be the good guys. And they are.

      --
      I've fallen off your lawn, and I can't get up.
    8. Re:Clearly by fyngyrz · · Score: 1
      • Where does Java execute?
      • Where does javascript execute?
      --
      I've fallen off your lawn, and I can't get up.
    9. Re:Clearly by K.+S.+Kyosuke · · Score: 1

      Both get executed wherever you run them. Most web sites today don't have the bargaining power to convince users to run client-site java, though, even though many of them run it server-side.

      --
      Ezekiel 23:20
  27. Re:chroot is for cross-compiling, not security by SigmundFloyd · · Score: 1

    getting out [of chroot] basically consists of making a symlink and doing cd.

    OK, but - unless I'm missing something - you can't do that while chrooted. A browser running chrooted can't execute code that will make links to "out of chroot".

    --
    Knowledge is power; knowledge shared is power lost.
  28. file handles aren't chrooted by raymorris · · Score: 1

    There are several ways. Some use the fact that file handles aren't chrooted. You can, for example, call fchdir() with handle inside the chroot, then chdir(..) several times. If the wrapper changed the working directory of the process before chroot, the escape code needs to fchdir to a directory other than the chroot root, so it'll mkdir first.

    There IS some level of inconvenience to escaping chroot, so there is a degree of security against an unsophisticated attack. I guess it could be compared to locking a window - that'll make the window less convenient to open, but simply throwing a rock at it will do the trick.

  29. Wait by DarkOx · · Score: 1

    many otherwise well-informed people think they have to do something wrong, or stupid, or insecure

    Wait how does executing code delivered over a clear text channel without some other strong attribution and integrity controls in place not count as stupid or insecure.

    Then we have slashdot here were we shove our session cookies back and forth in clear text. Not ideal but I don't execute code from slashdot (noscript) and I don't reuse my user name ore password elsewhere. So that lowers my exposure somewhat.

    The browser makes need to at this point:
    Disable the execution of any script or content of any script tag that was not transferred securely or loaded from local media; by default. Perhaps provide a white-list function to accommodate legacy intranets and stuff. They should similarly deny embedded objects like flash, sliverlight, acrobat, etc in those situations.

    This would do a lot to protect people from both inject attacks and various forms of phishing. It would also really push site operators and web hosts to make sure SSL is available everywhere.

    --
    Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
  30. Fools! by Anonymous Coward · · Score: 0

    1. The algorithm that is used to create the certs was backdoored by the gov actors inside the standards body or company that created it.
    2. Google would not revoke a root cert if a company was issuing the government bogus certs, because google is 100% part of the evil cabal running the west.
    3.They don’t even care about backdooring most software, because they have backdoored most hardware now.

    Intel systems from sandy bride forward are impossible to secure. The next move is infiltrate open source organizations and projects to inject malicious code for people running hardware that isn’t compromised. They will also use these agents to sabotage, because the gov and the big companies like IBM are scared that they are losing control.

    Any reasonably intelligent person should have already figured this out.
    Keep being naive, and keep getting pwned.

    Now “send in, the TROLLS”, “we’ve got one that can see”!

  31. A dedicated IP costs 60 bucks more a year by tepples · · Score: 1

    Web admins in particular should turn on https by default since there's no reason not to unless you're intentionally being shady.

    I agree that hosting providers ideally ought to offer HTTPS. But IE and IE wrappers on Windows XP doesn't support Server Name Indication (SNI), a TLS extension that allows the use of name-based virtual hosting. Nor do Android Browser and Android Browser wrappers on Android 2.x. Both of these SNI-ignorant browsers have reached their end of support, but until they actually pass out of use, hosts still need to accommodate them. This means most shared hosts will continue to require customers to upgrade to a VPS (or at least pay extra per month for a dedicated IPv4 address) to avoid support issues associated with SNI-ignorant browsers. WebFaction is one exception that I've found that supports SNI.

  32. Perspectives by tepples · · Score: 1

    The Perspectives extension works alongside the CA system to help the browser trust a certificate from an unrecognized CA. If multiple "notary" machines in different parts of the Internet see the same certificate, it's unlikely that the same entity is MITMing them all.

  33. Console games by tepples · · Score: 1

    Try running most AAA games under Linux. A few will come with ports, and a few more will deliver a port 2-3 years later when nobody cares anymore. The vast majority are either Windows-only or Windows+Mac.

    A lot don't even run under Windows because they're made for consoles. This is especially true of "party" games whose draw is offline multiplayer with two to four gamepads and a single TV.

    Look how long its taking IPv6 to get off the ground and its got built-in support by every major OS and network equipment provider!

    I guess a lot of that is because cities make it too hard to start a competing ISP.

  34. Worms exist by tepples · · Score: 1

    client computers are such unique devices

    If significant subsets of PCs aren't monocultures with the same vulnerability, then how do worms like Blaster and Slammer spread and leave behind hooks to form botnets?

  35. Ads are mixed content by tepples · · Score: 1

    Everybody else is using HTTPS except Slashdot.

    Does this include "everybody else" that uses the major ad networks? Using an HTTP-only ad network in an HTTPS site won't work because of mixed content policy.

  36. Because most ad networks are HTTP by tepples · · Score: 1

    Until very recently, major advertising networks were available only through HTTP, not HTTPS. Only in September of last year did AdSense announce HTTPS support.

  37. YouTube videos with ads require Flash by tepples · · Score: 1

    Many YouTube videos with advertisements require Flash. If you try to view them on a PC without Flash, you get a notice that Flash is required. If you try to view them on a platform to which Flash is not ported, such as iOS or Android 4.1+, you get "The content owner has not made this video available on mobile. Besides, what's the alternative to Flash game sites like Newgrounds and Kongregate?

  38. Allow only HTTPS active content by Giorgio+Maone · · Score: 1

    NoScript Options>Advanced>HTTPS> Forbid Active Content unless it comes from a secure (HTTPS) connection .

    Painful, yes, but it should take care of this kind of attacks, as long as you can trust HTTPS (e.g. with Convergence).

    Furthermore, NoScript 2.6.8.37rc2 introduce an experimental "Allow HTTPS scripts globally on HTTPS documents" mode (in Advanced>HTTPS>Permissions) if you value convenience over finer grained security.

    --
    There's a browser safer than Firefox, it is Firefox, with NoScript
  39. Do any virus scanners detect the malware? by ayesnymous · · Score: 1

    Do any virus scanners detect the malware installed from this exploit?

  40. Identity providers by tepples · · Score: 1

    That's true of Slashdot because Slashdot isn't an ID provider. But some other sites, such as Facebook, Twitter, Google, and webmail, are identity providers. If you compromise a user's Twitter account, you compromise the user's account at any service that uses "Login with Twitter". If you compromise a user's webmail account, you compromise the user's account at every service that lets the user recover his password through e-mail. That's why the major identity providers have gone all HTTPS all the time.