Slashdot Mirror


Intel Discloses Three More Chip Flaws (reuters.com)

Intel on Tuesday disclosed three more possible flaws in some of its microprocessors that can be exploited to gain access to certain data from computer memory. From a report: Its commonly used Core and Xeon processors were among the products that were affected, the company said. "We are not aware of reports that any of these methods have been used in real-world exploits, but this further underscores the need for everyone to adhere to security best practices," the company said in a blog post. Intel also released updates to address the issue and said new updates coupled those released earlier in the year will reduce the risk for users, including personal computer clients and data centres. In January, the company came under scrutiny after security researchers disclosed flaws that they said could let hackers steal sensitive information from nearly every modern computing device containing chips from Intel, Advanced Micro Devices and ARM.

126 comments

  1. Intel realy needs to start cutting prices to amd by Joe_Dragon · · Score: 1, Insightful

    Intel realy needs to start cutting prices to keep up with amd.

    And on the high end desktop line all cpu needs to max out pci-e lanes. Going as low as 16 is just an joke there.

  2. Sigh. I'm trying to look on the bright side... by skids · · Score: 1

    ... at least nobody is bidding for "exclusives" on the firmware patches.

  3. What percentage drop? by Anonymous Coward · · Score: 0

    What percentage drop can we expect to see with the new patches?

  4. Re: Intel realy needs to start cutting prices to a by Anonymous Coward · · Score: 1

    what does this have to do with the article except intel is in both?? You IDIOT, you buffoon

  5. Techniques for faster also have security implicati by Anonymous Coward · · Score: 0

    Techniques for faster CPUs also have security implications. Who'd a thunk it?

    Soon we'll discover that lower power run modes also have security implications.

  6. *That's* the bad news. The good news? by Anonymous Coward · · Score: 0

    Brad and Jen, on the cover of a magazine -- together.
     
    Oh, by the way, the world ends tomorrow; details at 11, but do you care?

    1. Re: *That's* the bad news. The good news? by Anonymous Coward · · Score: 0

      AM or PM? I like to sleep in.

  7. Follow their advice! by Anonymous Coward · · Score: 5, Insightful

    The Reuters article quote Intel's blog: "...this further underscores the need for everyone to adhere to security best practices," the company said in a blog post.

    That first best practice would be not buying Intel chips. Glad there's an alternative.

    1. Re:Follow their advice! by Aristos+Mazer · · Score: 1

      Or ARM. Or AMD. Really, with advice like that, perhaps you should just not use a computer.

    2. Re:Follow their advice! by Anonymous Coward · · Score: 0

      ARM is good enough. It's the speculative execution that's the root of all of these various issues and since most ARM processors are in-order you can just go with them. ARM is rather high on the performance per watt ratio with most GPUs taking the major lead. So, in server/virtualization environments where most of these attacks are so critical, being able to use ARM Linux really could undercut the growth of Intel (and AMD) in that sphere. I imagine the key part is just how well ARM moves towards supporting virtualization in a fashion that doesn't open itself to the same sorts of attacks. Given, however, the various attacks on TrustZone, I'm a bit wary of that.

    3. Re:Follow their advice! by Anonymous Coward · · Score: 0

      Right now the alternative doesn't work for me. I've been experiencing complete lockups on Freebsd systems using Ryzen 1600, 1600X and 2600 chips that don't occur with the few Intel chips (i5-4670K, i5-4590 and i5-8250u) that I've tried using. The system appears to be completely dead, keyboard frozen and network frozen. This is a far bigger problem for me than the various Spectre and related issues.

    4. Re:Follow their advice! by Anonymous Coward · · Score: 1

      All the recent ARM stuff is out-of-order. The only high-performance (for its time) core I know about recently is the POWER6, which worked by having extraordinarily high clock speeds. Some of the ARM CPUs were even susceptible to Meltdown because they made the same bad optimization choices as Intel.

      That said, while *some* ARM, AMD, POWER, etc. chips have had *some* of these flaws, Intel has had *all* of them because they seem to have embraced this particular strategy of in-parallel permissions checking as a general design principle. So even though not every one of these problems has been Intel-specific, Intel processors have had, by far, the worst time of it in terms of number of bugs, severity of bugs, and difficulty/performance impact of mitigation.

    5. Re:Follow their advice! by Anonymous Coward · · Score: 0

      Better make sure that it is the regular FreeBSD code that freezes your system. Sometimes it's just the backdoors and malware that doesn't work on all architectures.

    6. Re:Follow their advice! by Anonymous Coward · · Score: 0

      Check your BIOS settings. I had lockups on my new Linux system with a Ryzen 5 1600. That got fixed by setting the CPU idle current to 'typical' in the BIOS of my board (ASUS Prime X370 Pro), since then the system has been running rock solid. Check your board manual for details.

    7. Re: Follow their advice! by Anonymous Coward · · Score: 0

      I have had no problems. My 2600x runs like a top. Sounds like user error or BS to me.

    8. Re:Follow their advice! by Anonymous Coward · · Score: 0

      Worse, if I remember correctly, the POWER6's successors are indeed vulnerable to Meltdown, which seems to be regarded as one of the more severe flaws.

      I'm legitimately curious as to why there are so many such vulnerabilities, when it would have been trivial to design some of them right the first time. For example, there is the Intel vulnerability (Meltdown) which doesn't check the access permission of a page until well after speculatively executing instructions that operate on supervisor-only data. My question is: why? Isn't it easy to check the S-bit of a cache line while reading it using the load-store unit?

      According to wikipedia, an illegal load of a supervisor-only cache line is cancelled, but remains in cache. Then malicious code could execute a timing attack, which depends on the fact that the privilege of the cache line isn't checked until well after the load has taken place. But it makes no sense that Intel even has this vulnerability. It would be very easy to have each cache line carry the U-bit specifying the permission needed to access that specific line, and the load-store unit can trivially check this bit at the exact same time it is fetching that line from the cache.

      Is there something I'm missing here?

    9. Re: Follow their advice! by Anonymous Coward · · Score: 0

      That's because you're using a toy OS.

    10. Re:Follow their advice! by Anonymous Coward · · Score: 0

      ARM Cortex A53 is immune to Spectre and Meltdown AFAIK. Meanwhile, virtually all of AMD, POWER, etc are vulnerable to Spectre. You're definitely right that most the modern ARM stuff is vulnerable, but it's actually possible to use at least decently modern designs that are safe. The closest comparable from other makers tends to be of the same speed as ARM A53 but much greater power usage.

      ARM's greatest strength is there's so much diversity in design because there's so many different companies licensing out different needs. Intel, AMD, and POWER all committed some time ago to the clock multiplier race that basically demands speculative execution. ARM was going down that path, but they're not totally down it. I'd say that puts them at quite an advantage.

  8. Cue the Intel apologists by drinkypoo · · Score: 5, Insightful

    No doubt Intel found out that someone else was going to disclose these flaws, so they got out ahead of it. They're pulling a Rudy here; try to beat the scandal, but then create one with their attempt to deflect responsibility to someone else:

    "We are not aware of reports that any of these methods have been used in real-world exploits, but this further underscores the need for everyone to adhere to security best practices,"

    Yeah, Intel. Everyone. Including the folks who have done the worst job of adhering to security best practices... Intel. You guys skipped security checks until after they were necessary to gain a performance advantage over AMD, and now you're trying to deflect attention from that by suggesting that security is someone else's responsibility. But the CPU is the heart of the machine, and you're responsible for deliberately compromising its security for a business advantage.

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    1. Re:Cue the Intel apologists by Anonymous Coward · · Score: 5, Informative

      Today's Wired article says the details of the Foreshadow attack would be presented tomorrow. Somebody is coordinating all this.

    2. Re:Cue the Intel apologists by sexconker · · Score: 1

      Wired foreshadows the disclosure of the Foreshadow attack.

    3. Re:Cue the Intel apologists by Anonymous Coward · · Score: 0

      In regards to AMD... they either haven't been targeted because of few people use it, or they're bracing for the wave, but there's no way AMD with it's resources can produce something more secure than Intel, when intel owns the market. Saying AMD is secure is like saying Linux is secure because nobody targets it.

    4. Re:Cue the Intel apologists by thegarbz · · Score: 2, Insightful

      Yeah, Intel. Everyone. Including the folks who have done the worst job of adhering to security best practices... Intel.

      Wow, hyperbole much? I've yet to see an Intel flaw expose millions of online accounts, spread credit cards and social security numbers, bring down industry through crippling bugs that were exploited.

      Perspective man, you desperately need some.

    5. Re:Cue the Intel apologists by Anonymous Coward · · Score: 1

      Intel's extra security flaws come directly from the things they have done to increase the instructions per clock cycle beyond AMD's level. In this case, simpler is better.

      We should make use of all the extra cores we have today and disallow speculative execution for processes that aren't speed critical. Maybe even make asymmetric processors with only a couple of cores optimized with speculative execution with their own cache. If you do that and then move all secure processes to the non-optimized cores (there is no great need for speed in password processing), you could create a gap that can't be bridged.

    6. Re:Cue the Intel apologists by Anonymous Coward · · Score: 1

      You've got it bass-ackwards. The microarchitecture performance tweaks Intel implemented caused the meltdown security defect. It's not because Intel were specifically targetted. AMD didn't make those same errors, hence AMD chips aren't vulnerable to meltdown. While spectre style attacks are feasible on many superscalar implementations, there's been a consistent roll of serious security flaws for Intel processors. AMD processors contain some features that make spectre style attacks more difficult to execute against them, although they are not entirely immune.

      You sort of need to look at the big-picture. A couple of years back, Intel cut resources related to verification. Nobody will ever know how many of these defects would have been caught if they hadn't reduced their verification process, but we are all paying the piper.

      The best thing Intel can do at this point is to accurately disclose flaws in a timely manner and stop the FUD campaign being run by their marketing folks. The FUD campaign harms users of their products, it makes it harder to find out the actual details of how to mitigate these serious security flaws.

    7. Re:Cue the Intel apologists by HiThere · · Score: 1

      That's true with Meltdown, and with one or two of the Spectre attacks, but I think some of them are shared equally with all extant CPUs that do speculative execution. Of course, those are a bit more difficult to use. And Inverse Spectre seems to have a very low speed of penetration.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    8. Re:Cue the Intel apologists by Anonymous Coward · · Score: 0

      No doubt Intel found out that someone else was going to disclose these flaws, so they got out ahead of it.

      Maybe, but getting companies to behave is a lot like getting children to behave.
      If telling the truth when they did a bad thing gives the same punishment as being caught lying when they did a bad then then you only teach them to lie.
      You have to create a situation where it is better to come clean early than hope that you won't get caught.
      You also have to make sure that the best scenario is to not misbehave at all.

      Different grades of outrage is needed, you can't go on full tilt all the time.

      Same thing with the "hard on crime" crowd.
      You might not like crime, but some crime is a lot better than a situation where it is better to get away with murder than getting caught shoplifting.

    9. Re:Cue the Intel apologists by Anonymous Coward · · Score: 0

      We should make use of all the extra cores we have today and disallow speculative execution for processes that aren't speed critical.

      Seems to be a bit paradoxical.

      Processes that are speed critical will typically do their job fast and then exit or wait for something, leading to task switching.
      Processes that aren't speed critical are typically long term tasks that could use a core exclusively for a longer time.

      But yes, having speculative execution turned off and only enable it for tasks that are able to hog a core for a long time might be the way to go.

    10. Re:Cue the Intel apologists by Anonymous Coward · · Score: 0

      Why do people call it inverse spectre?
      It's just spectre.
      It works on the exact same principle. Not the inverse. Just a different instruction.

    11. Re:Cue the Intel apologists by AmiMoJo · · Score: 1

      That's only because the response to it was relatively well coordinated and patches became available fairly quickly after the slightly premature announcement.

      The damage done is quite real and measurable though. 60% performance loss for some server tasks, meaning a massive cost increase or degradation of service.

      I'd love to see some stats on how many people sued Intel over this. They paid for my new workstation but I'd love to know how many more.

      --
      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:Cue the Intel apologists by thegarbz · · Score: 1

      That's only because the response to it was relatively well coordinated and patches became available fairly quickly after the slightly premature announcement.

      HOLY FUCKING SHIT. No man. No. Not remotely. Not even slightly. Mass machines still not patched. Holes still everywhere. Daily security issues still being discovered.

      There was NOTHING AT ALL good to say about the response to this from any party at all, not from Intel, not from MS, not from the open source community. It was a textbook example of a horrid clusterfuck of a response.

      The damage done is quite real and measurable though. 60% performance loss for some server tasks, meaning a massive cost increase or degradation of service.

      Again hyperbole. The actual performance loss for many server tasks is about equal to the performance gains that have occurred thanks to the wonderful kernel teams. What Linus giveth (10%) Intel taketh away (5-20%). Outside of lab based examples to bring out the worst in the patches the real world workload tests have shown anywhere from 5-25% in the absolute worst case. The wonderful thing about those worst case scenarios is they are quite often systems where speculative execution attacks aren't actually relevant (i.e. I/O heavy backend). Real world most people will see less than a 10% change if they have a processor with PCID capability and that includes server workloads.

      Compared to damage from software bugs ultimately the impact of Spectre and Meltdown including security and performance issues will be forgotten in history as a rounding error in the cost impact to people and companies due to actual proper security issues that arise from the incredible mass of poorly written and even more poorly configured software.

      I'd love to see some stats on how many people sued Intel over this.

      Not relevant. I'd love to see stats on how many people *won*.

    13. Re:Cue the Intel apologists by HiThere · · Score: 1

      I call it "Inverse Spectre" because that's the name it was given when I read about it. Think of it as a name rather than a description. ("Spectre" is very good as a description anyway.) The first time I read about Spectre it was divided into three sub-classes. This is an new sub-class with a new name. I don't know why they named this variant "Inverse", but then I don't know why they named the entire group "Spectre", though I guess it's partially because they use British spelling.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  9. Re:Fuck you you stalking little cunt... apk by Anonymous Coward · · Score: 0

    Sure.
    call 202-456-1414 and ask for Donald.

    1600 Pennsylvania Avenue NW
    Washington, DC 20500

  10. Time to see you SQUIRM "lil' JOWIE" (lol) by Anonymous Coward · · Score: 0

    See my subject & letting you f yourself dumbass https://it.slashdot.org/commen... you inferior moron.

    * Don't try "patronize" me BOY when I can show you are less than ZERO fucker... easily.

    APK

    P.S.=> Your DIM brains are blatantly inferior evidenced by your FAKE NAMES online for FAKE lives of being "ne'er-do-well" scum having the AUDACITY to even TRY "F" w/ me & ones like you you INFERIOR swine as I cast PEARLS before SWINE like you... apk

    1. Re:Time to see you SQUIRM "lil' JOWIE" (lol) by Anonymous Coward · · Score: 0

      LOL. You sad, sad little man.

  11. Never Forgetti by Tsolias · · Score: 1

    https://img.purch.com/amd2-png...
    "Robust h/w and s/w ecosystem"
    "Robust h/w"
    "Robust"

    Intel was too cocky about their "robust" ecosystem.
    This is not just a backfire... this is a 2 years hw and sw security breach spree.

  12. Intel Down, AMD Up by The+New+Guy+2.0 · · Score: 3, Informative

    Intel seems to be having problems again, while AMD is rolling out 2nd Gen Ryzen Threadrippers this week. AMD's got the high-end processor market all to itself, while Intel is revealing that they were never that good as they advertised.

    Intel could have had a monopoly if they didn't make the Pentium bug math error. Computers are supposed to be "perfect" at computations, but the Intel bug threw some court cases in the wrong direction. I'm not sure they can be trusted anymore.

    Now AMD is rolling out processor changes that were discussed here on Slashdot years ago, and they're off in the speed races and higher core limits. (Intel maxes out at about 6, new Threadripers offer 32 hyperthreaded cores that simulate 64 processors.)

    Intel better go back to the drawing boards... they're behind in a game they used to always win.

    1. Re:Intel Down, AMD Up by drinkypoo · · Score: 1

      Intel better go back to the drawing boards... they're behind in a game they used to always win.

      Used to almost always win. The Athlon absolutely pounded Intel's chips at the time it came out, when it had superior processing power and power consumption. And let's not forget that Intel was forced to implement the amd64 ISA to maintain compatibility with AMD's superior processors again. Intel's primary advantage all along has been volume; what's changed is that now that's their only advantage.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Intel Down, AMD Up by Anonymous Coward · · Score: 1


      Intel could have had a monopoly if they didn't make the Pentium bug math error.

      What? That was in 1994, and consumers might have read about it in a newspaper, and not cared. It was basically a non-event, except among some scientists and mathematicians who rely on accuracy.

      Computers are supposed to be "perfect" at computations

      No, computers are supposed to be very, very good at computations and rarely make mistakes. They were never supposed to be perfect. Bits get flipped from cosmic rays, rowhammer, or just by design of the electronics, which always has noise in it. The real world of electronics is NOT perfect. This is why serious scientific computing efforts require a calculation to be performed twice and the same results obtained both times. Errors don't happen very often, but they aren't so rare they never happen.

    3. Re:Intel Down, AMD Up by Anonymous Coward · · Score: 0

      amd has their own issues and bugs in their chips; some of those are shared with intel... so blindly suggesting amd is 'better' than intel isn't entirely accurate... for performance or security.

      what we are seeing here now with this recent 'rash' of flaws in processors can be traced all the way back to late 2005 and early 2006, when amd was at its strongest vs intel, and their marketshare showed it.. being within 4% of intel's and closing-in on perhaps taking the lead. back then, it was athlon vs netburst, and intel was falling, hard and fast.

      intel was in a panic, they had to do something and the next evolution of their chips (scrapping netburst entirely and building off the older pentium iii mobile as a new starting point) completely restored intel's dominance, literally overnight. but at a price. they started cheating (so-to-speak) on performance to get a leg up on amd processors. it worked. intel 'core' architecture chips were so much faster than amd's, and that lead has persisted to this day (peaking ~ 10 years later at 82/18 marketshare advantage)... but their cheating on performance back then has created flaws baked into every single chip they have produced since. amd started using some of the same performance tricks, and so amd chips share some of the same flaws as intel's.

    4. Re:Intel Down, AMD Up by Anonymous Coward · · Score: 0

      How old are you, Grandpa? The Pentium math error is from 25 years ago and was a step away from a non-event. It has nothing to do with Intel's currently being a monopoly or not.

    5. Re:Intel Down, AMD Up by thegarbz · · Score: 1

      Intel could have had a monopoly

      I don't understand. Are you saying the only thing that prevented a monopoly was the math bug? Or better still are you suggesting that Intel hasn't been in an absurdly dominant position over the past decade?

    6. Re:Intel Down, AMD Up by Anonymous Coward · · Score: 0

      In the case of the Pentium floating point bug, Intel eventually replaced the affected chips for free. They handled it much better. Sadly Intel has resorted to FUD in addressing the recent pile of security issues. Meltdown is an extremely serious flaw, and Intel handled it extremely unprofessionally. The same can be said for the many spectre variants and how Intel has handled the security disclosures.

      I don't expect Intel to be happy about these critical security flaws, but I do expect them to behave in a way which shows professional integrity. Like many, I was directly impacted by these security flaws and I don't appreciate the FUD at all, it just made my job harder. Many other engineers feel the same way.

    7. Re:Intel Down, AMD Up by Anonymous Coward · · Score: 0

      remember about 10 years ago when Intel said they'd be releasing 100-core processors in the next 2-3 years? Whatever happened to that? They're even putting out new dual cores. *dual cores*. In 2018.

    8. Re:Intel Down, AMD Up by The+New+Guy+2.0 · · Score: 1

      AMD was almost out of business in the late 1990s... they were paying Intel for design patent rights, and couldn't compete on price or quality, until Intel stumbled with the Pentium math error. It was expected that AMD would merge with Intel, who would have basically shut the company down completely. Digital Equipment Corp. was trying the break into the WIndows game, but never got off the ground, and their processor line was shut down with the Compaq/HP mergers.

      Mr. Ryzen was with AMD in early 2000s, and laid out the course the Ryzen processor series would take here on Slashdot once the patents were in their hands, with new ideas such as the pin-less connectors, continuing to hyperthread (something Intel has given up on) and cramming more cores per chip.

      A 32-core Generation 2 Threadripper is due out this month, while Intel is limited to 6 cores per chip. Intel is still selling fast Penitums and Celerons, there's hardly any innovation there.

      AMD moved up in the past 20 years, but was almost down for the count in 1999.

    9. Re:Intel Down, AMD Up by Anonymous Coward · · Score: 0

      Yes, I'm sure that every household will need one of those 32-core Threadrippers. Actually no, that is not true. What most people do on their computers can be achieved with a cheap and power efficient Celeron or Pentium G that also comes with integrated graphics. And as far as gaming goes, a $200 i5 outperforms a $300 R7 in most popular games, not to mention Threadrippers.

      AMD has made considerable strides in the recent past, that should not be overlooked. It's good that they have such a 32 core product. There are people who can benefit from it. But otherwise these are niche products. And that's something a lot of the ultra-nerds here on this site do not want to realize, but rather live in their own fantasy world.

    10. Re:Intel Down, AMD Up by thegarbz · · Score: 1

      Yeah but I think you have a causality issue there. AMD was on life support before the Pentium bug, and they were on life support long after the Pentium bug. The only thing that gave them a boost was Intel's seemingly cyclic phase of resting on the laurels long enough to let competitors actually do some innovation. Even after the FDIV bug in the previous generation the P6 dominated the industry. It wasn't until Netburst that Intel gave AMD a chance to do anything to claim back some market share.

    11. Re:Intel Down, AMD Up by lsatenstein · · Score: 1

      Intel seems to be having problems again, while AMD is rolling out 2nd Gen Ryzen Threadrippers this week. AMD's got the high-end processor market all to itself, while Intel is revealing that they were never that good as they advertised.

      Intel could have had a monopoly if they didn't make the Pentium bug math error. Computers are supposed to be "perfect" at computations, but the Intel bug threw some court cases in the wrong direction. I'm not sure they can be trusted anymore.

      Now AMD is rolling out processor changes that were discussed here on Slashdot years ago, and they're off in the speed races and higher core limits. (Intel maxes out at about 6, new Threadripers offer 32 hyperthreaded cores that simulate 64 processors.)

      Intel better go back to the drawing boards... they're behind in a game they used to always win.

      For gaining access to the cpu, you need to have access to the VM that boots that CPU. And if you have that, then what is the fuss about?
      I at home or with my small business server, I don't give a shit about the security flaw. I don't run a bank and frankly, I do most of my financial transactions via my cellphone. Why are we not concentrating on reality to see if someone next to me can read my cellphone contents.

      For the security breach would you need to be running software that somehow got installed and is surreptitiously running and sending information out via some new opened port on your router.

      --
      Leslie Satenstein Montreal Quebec Canada
  13. Everyone[else] should by Anonymous Coward · · Score: 0

    Did the Microsoft security PR drone contract with Intel for this gem? What heros they will be when they fix the security problem they created! #MAGA

  14. Re:Techniques for faster also have security implic by The+New+Guy+2.0 · · Score: 1

    Seems like everybody's leaving a hacker hole in their products these days... are we really safe?

  15. Re:Intel realy needs to start cutting prices to am by Anonymous Coward · · Score: 1

    I know that a lot of people want that to happen whether they favour Intel or AMD. If Intel were to cut their prices AMD would probably follow suit and most consumers would be better off.
    But does Intel need to do that from their own perspective though?
    If you look at their market share the majority of people still appears to go for Intel despite the higher prices.
    If my overpriced shit would sell that well, why should I reduce my prices? The same logic seems to apply to nVidia graphics cards.
    Things may change in the future as AMDs get more popular across all users. Maybe software developers will optimize better for the quirks that Ryzens have with certain software. Quirks like latency issues, that can weigh down the performance gain from a lot of threads in memory intensive or highly dynamic applications.
    But until then Intel can ask for their premium prices and there will be enough people who are willing to pay for that.

  16. Launching New Marketing by Anonymous Coward · · Score: 0

    Bing Bong Bung. Piece of Shit Inside.

    What's in YOUR PC?

  17. Exactly, all timing attacks against optimizations by raymorris · · Score: 1

    And that's why these general types of attacks won't be going away any time, except on specialty processors.

    These attacks are based on the fact that some operations are faster than others. To get rid of them, you need to make everything equally slow. Addressing one specific case may make the CPU 10% slower, but there are a hundred timing attacks. 10% slower a hundred times equals ...

  18. AMD fans should remember... by SeaFox · · Score: 2, Insightful

    The lack of disclosed vulnerabilities does not mean vulnerabilities do not exist.
    To think "no news is good news" is not that far from "Security through Obscurity".

    1. Re:AMD fans should remember... by Anonymous Coward · · Score: 0

      I could be wrong but I'm pretty sure Intel will be spending just a little bit of effort to try to turn up vulnerabilities in AMD chips at the moment.

    2. Re:AMD fans should remember... by Anonymous Coward · · Score: 0

      Intel has demonstrated how NOT to handle security disclosures. Intel's behaviour has been extremely unprofessional. As a user of Intel products, I expect better. The way Intel obfuscated the news made the job of those of us who had to assess and mitigate the security impacts harder.

    3. Re:AMD fans should remember... by Anonymous Coward · · Score: 2, Interesting

      The lack of disclosed vulnerabilities does not mean vulnerabilities do not exist. To think "no news is good news" is not that far from "Security through Obscurity".

      I'll take "potentially has problems" over "definitely has problems"

      And with hindsight being 20/20:

      I've been on AMD for the past 10 years. When the Meltdown flaw was revealed I was not affected by it.

      It makes sense to continue using AMD, especially with Intel announcing even more flaws.

    4. Re:AMD fans should remember... by Anonymous Coward · · Score: 0

      I don't know about security vulnerabilities, but the AMD Ryzen CPU's have issues that render them largely useless to me (completely locking up under heavy loads).

    5. Re:AMD fans should remember... by Anonymous Coward · · Score: 0

      The lack of disclosed vulnerabilities does not mean vulnerabilities do not exist.

      But also, a disclosure of a vulnerability in an Intel chip does not mean that it is present in an AMD chip.

      That's true regardless of how much Intel has tried to gaslight us this year.

    6. Re:AMD fans should remember... by AmiMoJo · · Score: 1

      What we do know is that because AMD correctly handles these kinds of situations they are not affected by most of these bugs. So the probability of there being similar flaws in AMD processors is much lower, even if we can't say that it is zero.

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

      LUL. Citation needed.

  19. Re:Bad ages ... by Anonymous Coward · · Score: 0

    A majority of people uses an office suite or a web browser. They don't need many cores nor hyperthreading.

    Tell that to the bloated OS that is more interested in keeping itself up to date with eye candy rather than staying out of the way. (prefetch, indexing service, makecab.exe). Tell that to the bloated Office suite where most features are not used yet installed anyway. Most importantly, tell that to the websites that assume more and more processing power just to run scripts that are of no benifit to site visitors. The applications that use the most memory/processing power on every PC I see are the browsers and it doesn't matter which one is used.

  20. Re:Techniques for faster also have security implic by Anonymous Coward · · Score: 0

    Of course one can be really safe. If you hate Intel enough and make it thoroughly clear by rants here in the comments one will be delivered from these evils.

  21. I give up by AndyKron · · Score: 1

    Nobody can get it fucking right. I give up thinking anything will get any better.

    1. Re: I give up by Anonymous Coward · · Score: 1

      Security is not a top priority.

      It takes too long to do right and sacrifices performance and is not a selling point.

      So, I agree with you.

  22. Re:Intel realy needs to start cutting prices to am by LifesABeach · · Score: 1

    Another thing observed in the wild is the lack of i11 n-core chip sets and cpu chips. I think Intel could definitely show some urgency in all these under powered tablet, and phone solutions.

  23. Leave Intel alone! by Anonymous Coward · · Score: 0

    Look at all the unlocked doors! It doesn't matter that the innermost workings of the locks are insecure! #MAGA

  24. Shut up you lying sack of shit by Anonymous Coward · · Score: 0

    I don't threaten vs. a NOBODY

    Shut your fucking pie hole you lying sack of shit.
    You threaten people all the time and when called on it you hide in the fucking corner and piss yourself.
    So come on pussycake post your fucking address

    1. Re:Shut up you lying sack of shit by Anonymous Coward · · Score: 0

      You do realize that's already out there, right?

  25. This is an INTEL ONLY problem by Anonymous Coward · · Score: 5, Insightful

    A brief history...

    Intel followed the very successful Pentium 3 design with Netburst, a radical new architecture that used a VERY long pipeline in the chase for a 10GHz (eventually) clock. It was terrible, but Intel paid outlets at the time, like Slashdot, to promote it as the second coming of chr-st.

    Meanwhile AMD was using its newly aquired team of CPU architects to build the world's first 64-bit compatible x86 chip, and the world's first true dual core x64 chip. And it was fantastic.

    No matter how much lies Slashdot et al were paid to say about Netburst, its hopelessness was obvious from day one (who would have guessed an ultra-long-pipeline stunk for this type of application). So after a few generations, Intel went back to the Pentium 3 design, crossed it with AMD's best patents (legal cos of a croos patent agreement between Intel and AMD), and made the Core 2 which today continues as the improved 'core' architecture in Intel's Slylake etc.

    What we did not know at the time was that Intel removed hardware memory access tests that a multi-core and or multi-threaded architecture that shares memory resourses must use. These tests are supposed to take the form of "lock and key" where a thread has a 'key' (id number) that must be tested in a 'lock' for any shared memory access. No lock and key means MUCH faster memory access and higher clocks/lower power- curiously EXACTLY those benefits seen over AMD til the release of AMD's Zen (but even then Intel keeps the clock advantage).

    Yes today's Intel parts, at best get 5Ghz while AMD's Zen+ is at 4.3 GHz cos of that 'illegal' (in computer science terms) Intel CHEATING. And that cheating is why Intel suffers from the terrible unstoppable exploits that Zen does not.

    Buy Intel and you are buying broken by design. Buy AMD's Ryzen and you are getting 'best of class' unless that buggy 0.7 GHz really matters to you.

    Tiday Intel compounds its cheating with buying the review methodology used to benchmark AMD products. So AMD just launched a 32-core 64-thread processor and Intel paid the usual suspects to bench only using programs known to use 8-cores or less. Whereas you or I would then run FOUR instances of the benchmark at the same time to actually stress the 32-cores, not one of the review sites even attempted this.

    Actually the Linux reviews were different since so many key Linux apps scale to any number of threads. They, of course, showed AMD's new threadripper to be a monster. But the bought and paid for Windows 10 reviews sites all 'wondered' who would want a 32-core part, given that "no windows user ever does more than one thing at a time on their computer". This is Intel's dirty money in play.

    PS I use the AMD 8-core 1700 in windows. It is jaw-droppingly awesome. Unlike Intel, you can just have everything working at the same time (and I came from Intel systems where one heavy app means you must close down other heavy apps first). Evey bad word currently said about AMD is financially sponsored by Intel's gigantic PR fund.

    1. Re:This is an INTEL ONLY problem by Anonymous Coward · · Score: 0

      Not wrong. If you want to have a look at the real benchmarking results, head over to Phoronix. It's completely insane the beatdown delivered by the 2990wx over any Intel consumer processor , and quite remarkable the difference in apps selected for the testing compared to the usual suspects. The 2950x beats Intels' 7980xe too, despite having 2 less cores, due to a better SMT implementation. Only thing hampering AMD right now is production capacity.

  26. I was there Gandalf by epine · · Score: 4, Informative

    Intel could have had a monopoly if they didn't make the Pentium bug math error.

    Computers are supposed to be "perfect" at computations, but the Intel bug threw some court cases in the wrong direction. I'm not sure they can be trusted anymore.

    Good lord, you can't be serious. The road to silicon nirvana is paved with errata sheets. (And always has been.)

    Furthermore, the division bug is a terrible example to bolster your cause, because the algorithm was correct in the first place, and the implementation of the algorithm in digital logic was correct in the first place, and then they dropped a very small stitch in the transfer to silicon layout. Had the stitch been any larger, they would have easily caught it during silicon validation. Hint: on randomized inputs, the bug is only triggered about once in 9 billion cases.

    Achieving 100% test coverage for all 3.1 million transistors is non-trivial, especially given the processing power available in 1990 three years before the Pentium was first released (what with cheap-ass PC memory costing $60,000/GB in 1990 dollars; double that for server-grade ECC).

    The only shitty thing Intel did in this chapter was try to sweep it under the run after the horse bolted the barn.

    And the truth of this is that back then, not a lot of software used the FP unit (most people had previously saved a few bucks by purchasing the 486SX castrato, which lacked the hardware floating point unit altogether, and most development shops pretty much assumed this was the defacto situation on the ground, so integer math was almost always preferred).

    It really was true that 90% of the people purchasing these chips were at low risk of any real consequence (the two-frame bump in the night right as you're closing in for the money shot in Falcon 3.0 possibly excepted—Falcon 3.0 was legendary for actually using the hardware floating point unit to actually compute a (mildly degraded) military-calibre flight model back in the 486 era (when nothing else did). The accurate inertial momentum effects when rolling hard simply blew everyone's mind. It was so good, you almost felt it through your feet (if you had been wise enough to invest in the 486DX).

    Poof! VERTIGO! VERTIGO! as the conspicuous fourth wall universally present in every kinetic 3-space simulator up until then suddenly vanished without a trace.

    There was just no way to point this recall at only those who needed it (proof of a previous 486DX purchase order would have been a not-bad fence; hard to believe if you had previously purchased the 486SX that just now you suddenly gave a shit, though wankers are gonna wank).

    So it's either pay to recall 9 processors causing a problem for every 1 processor that really needs to be replaced (at an enormous, globally unproductive expense), or panic and do a fatally stupid PR snow job. Intel picked door #2.

    "Daddy, daddy, where does CO2 come from?"

    "Well, son, it comes from flushing $500 million worth of almost perfectly good CPUs down the crapper practically unused, and then baking up a fresh set."

    Guess what? I'm old as fuck, and still sharp as a tack. So if your asbestos underpants are in any kind of mild disrepair, I'd stick to spinning mythical stories about the 1970s or the 1960s, if I were you.

    (Hint: I was already reading the 8008 data sheet to pass the time in my grade eight literature classroom. I would have had to mow my weekends to smithereens to actual own one at the price back in the day—not the very first version from 1972—but right around the time they came up with a simplified version reducing the number of mandatory voltage supplies from -12, +12, +5 to just +5. So even the mid-seventies are not quite free and clear for mythical reconstruction, wherever my lawn is found.)

    1. Re:I was there Gandalf by The+New+Guy+2.0 · · Score: 1

      The 11/17 division bug was in nearly every Intel Pentium processor on the Syracuse University campus in 1999, and showed up in my statistics textbook as well. Intel had to replace every chip it sold during that era.

      Computer/Calculator math is perfect in nearly every true implementation these days. Network transmission errors have gone away by error corrections. The problems of the 1970s are no longer a factor, the new set of problems is mainly the generation of heat in computers, time consumed, and compression of video.

    2. Re:I was there Gandalf by segedunum · · Score: 1

      Good lord, you can't be serious. The road to silicon nirvana is paved with errata sheets. (And always has been.)

      I think you might want to wake up, smell the coffee and work out what this 'errata sheet' actually means and why it's happening.

    3. Re:I was there Gandalf by List+Lurker · · Score: 1

      oh wize Wizard - LOVED your post. and when, at the end, you had Sherman set the WAYBAC machine to 1972 ... my mind wandered back to my APL and Fortran classes. Saruman, out!

  27. Re:Intel realy needs to start cutting prices to am by HiThere · · Score: 1

    Nonsense. All they need to do is ensure that all stories in the press blame all CPU chips equally, even when that isn't true.

    --

    I think we've pushed this "anyone can grow up to be president" thing too far.
  28. best practices by Anonymous Coward · · Score: 1

    ..."but this further underscores the need for everyone to adhere to security best practices,"

    I.e. Don't use Intel

  29. Well... by Anonymous Coward · · Score: 0

    At least, they don't explo

  30. Rip it out by Anonymous Coward · · Score: 0

    I'm gonna rip this fuckin' Intel CPU out and install AMD.

    1. Re:Rip it out by ebvwfbw · · Score: 1

      If it were only that easy.

  31. I've got a theory about this by Anonymous Coward · · Score: 0

    I am willing to bet that the NSA planted personnel in Intel. ASIC Engineers that actually were NSA agents. Let's face it, a microprocessor is a powerful device.
    If you put purposely design a backdoor, you have access to data...

    I believe there are many security flaws that originated by design.

  32. Re: Intel realy needs to start cutting prices to a by Anonymous Coward · · Score: 1

    what does this have to do with the article except intel is in both?? You IDIOT, you buffoon

    It has everything to do with a consumer faced with a choice between Intel and AMD.

    Intel processors are disproportionately susceptible to security problems.

    16 lanes is woefully inadequate. Single graphics card by itself would consume all of them.

    Lack of ECC.

    AMD is a no brainer at this point.

  33. Re:Intel realy needs to start cutting prices to am by Anonymous Coward · · Score: 0

    Nah! they will be fine, they have the power to do anything, they keep selling faulty products as top-notch, seriously, all those cores and speeds and they all end running the same windows at the same slow speed, they even managed to make the whole world to swallow windows 10 with their lack of drivers for Windows 7 and 8.

    In my workplace everything is Intel, but personally I use AMD because is the same but at least is cheaper.

  34. Re: Intel realy needs to start cutting prices to a by Archtech · · Score: 1

    Does AMD support ECC? Or any other manufacturer? I thought the prevailing view was that it is far better to suffer the occasional catastrophic crash or data corruption, rather than pay a few dollars more for reliable RAM.

    --
    I am sure that there are many other solipsists out there.
  35. Re:Intel realy needs to start cutting prices to am by Anonymous Coward · · Score: 0

    It (whataboutismish red herrings) appears to be the most powerful information warfare tool there is in these times and also works wonders here in political slashdot articles. You can see it as a mirror of the mental capabilities of your average slashdot commenter. Don't expect it to work any different in articles about science and technology.

  36. I am APK the LORD of HOSTS by Anonymous Coward · · Score: 0

    I am APK the great "LORD of HOSTS", a.k.a. AlecStaar from ArsTechnica or Alexander Peter Kowalski.

    See subject & APK Hosts File Engine 2.0++ 64-bit for Linux h t t p : / / I . a m . a . f u c k i n g / a s s h o l e . r e t a r d . z i p (remove spaces between characters & download).

    I am the godlike creator of various GUI front-ends for other people's configuration files.

    I think only one person stalks me as I shitpost and I dusted them on another site but in reality I am widely hated all.

    When people state the truth about me I get really mad and accuse them of projecting which is something I do all the time.

    Don't call me out on anything as I will state that you are a webmaster and that I cut off your revenue stream.

    You must be conspiring with the Jews and Soros if you disagree with me.

    Mistaking mockery and parody for impersonation is how I think people flatter me because I can't possibly understand that they detest me.

    See me lash out at one person for 2 weeks straight and claim everyone who mocks my retarded ass is actually them.

    Bask in my greatness as I post my advertisements in discussions where they don't belong, by the way this is every discussion I post in.

    I demand your age sex and location so that I can threaten to show up and kick your ass and will call you a pussycake but am actually too scared to actually do anything but be a keyboard warrior.

    Watch as I claim I am world class and a winner but in reality I am a fucking loser.

    Witness my descent into madness

    APK

  37. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  38. Re:Chip Vulnerabilities by jittles · · Score: 1

    I do not recall seeing this many security problems cropping up over the last 30 years when it came to processors. Is this new or is Intel now having to deal with all the corners they have been cutting to gain an advantage?

    Most likely a combination of the two. With cloud computing being all the rage and with more sophisticated OS security (at least for mainstream desktop use) researchers and government agencies have started to focus more on exploiting issues in hardware, whether it be with the physical design of the hardware or the firmware that runs directly from flash.

  39. Re: Intel realy needs to start cutting prices to a by Anonymous Coward · · Score: 0

    AMD is a no brainer at this point.

    I totally agree... intel is nose diving fast! I would love to see AMD succeed so I have no problem with intel dropping the ball, again and again and..

    Does anyone even have COUNT of the current number of intel flaws at this point?

  40. Re:Chip Vulnerabilities by Anonymous Coward · · Score: 0

    Adding all those back doors for the various governments had to cost something, didn't it ? A few are now being found; I'm sure others are waiting in the wings. I suspect not all of these "mistakes" really are. For instance, why do we need another processor running an entirely different instruction set embedded inside a cpu ?

  41. IMPERSONATING ME AGAIN? Please... apk by Anonymous Coward · · Score: 0

    IMPERSONATING ME AGAIN? Please - GROW UP, get on topic & get a life! Trying to make me "look bad" since you know you're a piece of do-nothing "ne'er-do-well" SHIT isn't helping your cause dumbass. You're playing BITCH games.

    * You're a loser - no help exist for YOU or "your kind"...

    (... & you KNOW it).

    APK

    P.S.=> You keep proving that to all reading in fact... apk

  42. Too big: That's not possible... apk by Anonymous Coward · · Score: 0

    See subject: You're going to start w/ an approximately 16mb hosts file off the data my program initally gets you & grow from there.

    HOWEVER: Some of the coding I do DOES help on that account e.g. using small/short int var size (hosts lines don't exceed 255 length) so it runs FASTER processing hosts file blocking (or speedup in favorite sites @ TOP of hosts avoiding DNS & its security issues + slower resolution speeds) keeping the data processing OUT of slower cache levels + global heap ram (slower vs. L1/L2/L3/L4 caches) while it's working.

    A secondary check I do vs. merged files NOT being processed 1st by my program's false positives & illegal tld/gtld data helps too (program actually finishes in ~7 min otherwise) vs. garbage bloat in hosts AND vs. "bushwhacking" by an interloper using an attack like this.

    APK

    P.S.=> That takes up to 20++ minutes more on that secondary check - but worth it - I will take ACCURACY over SPEED anytime... apk

    1. Re: Too big: That's not possible... apk by Anonymous Coward · · Score: 0

      7 minutes? 20 minutes? What the fuck are you doing? The rest of us crunch our DNS white listing and black listing in seconds, automatically. No wonder you need to keep looking for ways to shave microseconds all the time, it's fucking slow and bloated.

  43. Addendum & small correction... apk by Anonymous Coward · · Score: 0

    ShortString use = another thing that helps in this area too (per the 255 length hosts data use vs. std. larger STRING type) for the same reasons (along w/ using smallint/shortint vs. integer data types in code), for speed/efficiency.

    APK

    P.S.=> Sorry - still having a.m. coffee folks - minus it, I just don't function as accurately, lol... apk

  44. Wake me up when you can remote-root OpenSSH by Seven+Spirals · · Score: 1

    Until then, *shrug*. These vulnerabilities are coming too fast with too little context to understand how they will impact security operations. I see a flood of articles crowing about the dangers of these issues, yet honestly, I haven't seen much real world impact. Maybe it's because I don't interact with desktop users or run untrusted javascript, I dunno. However, I just wish every security advisory had a nutritional information section where they had to admit "No, we still can't figure out how to make this into a remote root vulnerability for OpenSSH." and if it actually was weaponized at all or even had the potential for that. If you watched the torrent of speculative execution and SIMD bugs come out lately, you'd think the only secure IT device was a mechanical typewriter. Also, AMD hasn't been immune, they've just had fewer issues than Intel. That's not saying a whole lot and I agree with others who speculate they just haven't all been found, yet.

  45. Alex McQuown/Khyber, STFU you loser by Anonymous Coward · · Score: 0

    Khyber STALKS me by AC again & ALWAYS SAYS "Lying Sack of Shit" (not to me always either ala e.g.) https://slashdot.org/comments.... https://slashdot.org/comments.... https://slashdot.org/comments....

    YOU MADE A HUGE MISTAKE THREATENING ME HERE Khyber https://slashdot.org/comments....

    &

    ANYONE I merely addressed in TURN when DIRECTED @ me 1st in violence by UNIDENTIFIABLE anonymous you use STALKING ME? Isn't threatening ANYONE real, period.

    (That is, UNLESS your name is "Anonymous Coward" on your birth certificate stupid & it isn't...)

    APK

    P.S.=> Khyber CAUGHT RED-HANDED "defending himself" by ANONYMOUS COWARD here too https://slashdot.org/comments.... ? Please, lol... apk

  46. Impersonating me STILL AGAIN? Lol... apk by Anonymous Coward · · Score: 0

    See subject: IF you're trying to make ME "look bad" you're only doing it to yourself & PROVING you wish you were me (imitation = sincerest form of flattery but YOU = POOR IMITATION).

    APK

    P.S.=> Grow up you psycho loser... apk

  47. Impersonating me PROVES u wish u were me by Anonymous Coward · · Score: 0

    1st: You're NOT me (but wish you were) & I'm NOT here to win a "popularity contest": I'm here to WIN so EVERYONE DOES & be faster/safer/more reliably connected online.

    Your CRAP's what I PUT UP W/ if one's "World-Class" (like ME): STALKERS stalking u by UNIDENTIFIABLE ac (everyone sees it happening & I suspect it's INFERIOR competitors, webmasters & advertisers (mostly) & malware makers (as my hosts engine affects 'em adversely & gives users of it more SPEED/SECURITY/RELIABILITY & more anonymity online)).

    Plus, since you say so? My "portrait" https://365songsblog.files.wor... (lol) so

    * Satan GET THEE BEHIND ME!

    APK

    P.S.=> 3 things show I do it right:

    1st = User praise my hosts engine https://tech.slashdot.org/comm...

    2nd "ATTACKS" I GET (from UNIDENTIFIABLE ac as Elon Musk got https://tech.slashdot.org/stor... )

    3rd BEING IMITATED = "Imitation = sincerest form of flattery" https://linux.slashdot.org/com... ... apk

  48. You might be right... apk by Anonymous Coward · · Score: 0

    1 thing my code does to protect itself? Is check it's size (what loads into RAM to run) vs. alteration in all procs/functions (~80 in total iirc) so in a way, you MAY be right!

    * I haven't read the FULL problem here - but from this quote âoeThe main promise of SGX is that you can write code, and ship it to someone you do not fully trust. That person will run the code inside SGX on their machine, and you can see that whatever they run there is protected, because you know they haven't modified your code, they haven't accessed the data that your code used.â Seems I already MAY protect against it PER ABOVE from ME @ START OF MY POST (SOURCE https://www.theregister.co.uk/... )

    APK

    P.S.=> In addition to this (for speed/efficiency) in my code https://it.slashdot.org/commen... also... apk

  49. More stupidity from APK by Anonymous Coward · · Score: 0

    That has to be one of the dumbest security measures ever. Then again it is from one of the dumbest "security experts" ever so we should have expected as much. Maybe you can tell us about how hosts provides port filtering capabilities, or about the stupid idea you submitted to ultra defrag that they rejected.

  50. Re: Fuck you you stalking little cunt... apk by Anonymous Coward · · Score: 0

    I've thought about giving you my name and address, just so when you come and find me, the authorities can make sure you're being monitored and on the appropriate sex offenders list and what not.

  51. Re: Did well per our /. peers... apk by Anonymous Coward · · Score: 0

    I find it so hard to understand your ramblings, I think you'd fail a Turing test as not being detected as a real person.

  52. DNS redirect poisoning & being down by Anonymous Coward · · Score: 0

    See subject: It's what 99% of ISP DNS can have happen to 'em as they're not patched vs. kaminsky redirect flaw & 7-20 min. I take keeps me safe from HOURS of malware removal too!

    (As well as TIME I SAVE by resolving FASTER than DNS can via local system RAM caching hosts in my 100 fav. sites I keep @ TOP of hosts for fastest possible resolves + ad blocking time savings (as well as infection savings (again, malware removal takes time & money (your money))).

    APK

    P.S.=> Even China agreed & copied me http://theregister.co.uk/2017/04/26/boffins_supercharge_the_hosts_file_to_save_users_plagued_by_dns_outages/ & "IMITATION's SINCEREST form of FLATTERY" ... apk

  53. You understood it perfectly... apk by Anonymous Coward · · Score: 0

    See subject as I SHUT YOU DOWN by using my code's self-verification of itself vs. infection/alteration by 'hacking' etc. https://it.slashdot.org/commen... & YOU certainly haven't done BETTER yourself either, lol (which I already knew about you & "your kind").

    APK

    P.S.=> EAT YOUR WORDS & tell us: How did they taste? Like your FOOT IN YOUR MOUTH ramming them back down your chicken-neck throat washed down by the bitter taste of SELF-defeat?? Yes... apk

  54. You proved 2 things then, lol... apk by Anonymous Coward · · Score: 0

    You proved 2 things then: The power of THOUGHT is beyond your limited mental capacity (lol) & that you're a skulking worm HIDING from me by your UNIDENTIFIABLE anonymous weezil posts!

    APK

    P.S.=> ... & you KNOW it (constantly proving it) + I'm no sex offender (is THAT the "best ya got"? It's not worth squat, like you, hahahaha)... apk

  55. Security pros say opposite of you #1/2 by Anonymous Coward · · Score: 0

    SANS ("A related approach to the DNS issue is to create a hosts file on each system that sends requests for spyware to some place else. Both Ramu and an anonymous reader have suggested this" hosts by myself & RAMU right @ START of "malware explosion" mid 2005 on) https://isc.sans.edu/forums/di...

    SANS (lists using hosts blocks) https://isc.sans.edu/forums/diary/Botnet+malware+defense/4138/

    BLOCKING (What hosts do) BEFORE SCANNING @ SANS https://isc.sans.edu/forums/di...

    Aryeh Goretsky/ESET/NOD32: hosts = good security http://it.slashdot.org/comments.pl?sid=7442373&cid=49747129/

    ZD NET http://www.zdnet.com/article/how-to-use-a-hosts-file-to-improve-your-internet-experience/ "Hosts files really shine by letting you block ads, spyware sites, malware sites, & tracking sites"

    Steve Gibson on hosts https://www.grc.com/sn/sn-045.htm/

    * MORE COMING IN PART #2...

    APK

    P.S.=> Sorry, but hosts DO do port filtering as I showed stupid... apk

    1. Re:Security pros say opposite of you #1/2 by Anonymous Coward · · Score: 0

      P.S.=> Sorry, but hosts DO do port filtering as I showed stupid... apk

      Where, you retarded fuck? You wrote a host line that includes a port, that isn't proof and you failed to refute anything I said. Nothing in any of the official documentation says that the line you wrote will behave as you specify, so please provide a link to some actual official OS documentation that backs up your retarded claim. Until you can do so your assertion is considered null and void and any restatement of it is an outright lie. It isn't my job to support your claims, especially since you can't seem to do so. I tried but the OS documentation I found and provided links to says you are lying. Apparently you also feel the need to change the subject and spam more your your previously disproved support. Don't worry I will tear them apart later because you are a fucking retard and must like having people prove it.

      * YOU LOSE as always vs. me, lol...

      Only in your mind. Truth is that when you change the subject and fail to refute other people's claims it means you lost.

  56. Hosts + netsh/IIS/fiddler etc. do portredir by Anonymous Coward · · Score: 0

    See subject & I see you RAN from the rest of my CRUSHING you easily via SECURITY PROS shutting your DUMBASS DOWN easily, lol!

    APK

    P.S.=> You LOSE fool - especially vs. TONS of security pros SHUTTING YOUR DUMBASS DOWN you dumbfuck DO-NOTHING loser that HIDES from me by UNIDENTIFIABLE anonymous... apk

  57. God, you are a fucking retard by Anonymous Coward · · Score: 0

    God, you are fucking retarded. You posted links to your previous 2 comments that I tore to pieces because apparently you think that supports your claim instead of just making you look dumb. You fail to refute anything I said anywhere and instead double down on your stupidity. After reading the links you provided it becomes apparent that you haven't read them, probably because you can't but then we knew you were illiterate since you fail to read and parse simple comments. They don't say what you think they say as I pointed out and you didn't contest or even attempt to rebut my statements thus conceding them. Yet you still claim you won, so you must by trying to convince yourself with that one as it isn't working on anyone else. It must be a difficult life being as retarded as you are, but you do lead a life full of failure.

  58. Retard APK loses again by Anonymous Coward · · Score: 0

    To your first one the answer is only some and only from those that are well known long after they became a threat, but there are many solutions that do a better job of stopping that. The other options allow better options for block as one can block all machines in a domain at once instead of having to create an entry for each one. Also hosts can only ever stop outbound connections instead other tools can stop connections in both directions. So looks like you've been out done here.

    To your second question no it doesn't' speed you up, especially when you are dealing with a file the size of yours, even if it does run in kernel mode. A linear search is all that can be done because it can't be assumed that hosts is sorted. Given that, it means that anything else that operates off of a sorted list will be faster. Add in the huge file you deal with and you really start seeing slow performance because string comparisons are expensive so the goal should be to reduce the number done, not maximize it like you seem to want to do. Also there are plenty of other tools that do a better job of stopping crap, like NoScript for example that stops all scripts thus providing more of a speedup than your work ever could. NoScript also manages to stop an entire broad category of attacks always instead of your work which can only stop attacks from well known sources that happen to be dependent on the client machine doing a DNS lookup. If I were worried about DNS outages or poisoning I would run something like dnsmasq either locally or on my network. This would handle all that, operates faster, and provide more security than your silly toy solutions.

    We've been over this before about the Chinese but you can't seem to understand that it is more likely that they came up with the same stupid simplistic obvious idea independently. You keep asserting that they copied you but can provide no evidence beyond your own uninformed speculations.

    You are right that I haven't done work that is as ineffective as your hosts file engine stupidity. This is because I actually have never created something as defective and then claimed it provides security. The software I work on and create actually requires that I be able to prove it provides security and the code goes through a formal verification and validation process. This process isn't a code review, but instead a team gets together and validates everything for correctness starting with the assertions that were made before coding began, and works their way up from there. This requires doing mathematical proofs and then validating that the code correctly implements the math which is something you don't comprehend. This is an expensive and time consuming process that none of your work has gone through and never will.

    The problem you have is that you started with the false premise that hosts provides good security. The truth is that hosts is a black list and black lists are the worst way of doing that. They are better than nothing but when it comes to provable security they provide none. Black lists can never enumerate all possible entries, are always out of date, are easily circumvented, and require constant maintenance. You are a failure and no one should listen to your advise.

  59. I'm still not buying new chips/PCs by Joshs922 · · Score: 1

    This is just more planned obsolescence PR--another nudge to go buy new chips. I'm still not buying new chips.