Slashdot Mirror


HTTP/2.0 Opens Every New Connection It Makes With the Word 'PRISM' (jgc.org)

An anonymous reader writes: British programmer and writer John Graham-Cumming has spotted what appears to be a 'code-protest' in the next generation of the hypertext protocol. Each new connection forged by the HTTP/2.0 protocol spells out the word 'PRISM' obliquely, though the word itself is obscured to the casual observer by coded returns and line-breaks. Work on the hidden message in HTTP/2.0 seems to date back to nine days after the Snowden revelations broke, with the final commit completed by July of 2013. In July 2013 one of the protocol's architects appealed to the development group to reconsider design principles in the light of the revelations about the NSA's worldwide surveillance program.

83 of 200 comments (clear)

  1. HTTP/2.0 support. by Anonymous Coward · · Score: 5, Funny

    HTTP/2.0 also supports the Bitcoin protocol which allows underpaid female STEM workers to drive 3D printed Uber cars or get a job (powered by DICE) delivering Arduinos via drones to Elon Musks new IoT manufacturing Chinese death factory.

    1. Re:HTTP/2.0 support. by mystik · · Score: 1

      Linux crypto hackers open-sourced the BSD Microsoft monopoly.

      --
      Why aren't you encrypting your e-mail?
    2. Re:HTTP/2.0 support. by thegarbz · · Score: 1

      Wow I got Bingo on the first post.

    3. Re:HTTP/2.0 support. by flink · · Score: 1

      You should at least cite your sources :P

    4. Re: HTTP/2.0 support. by Coren22 · · Score: 1

      SystemD started on Windows, it is just a svchost backport.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    5. Re:HTTP/2.0 support. by Coren22 · · Score: 1

      Second post, the first post is someone posting AC claiming to be APK and insulting him pretty profoundly.

      http://yro.slashdot.org/commen...

      Always read at -1, it is the most interesting side of Slashdot.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    6. Re:HTTP/2.0 support. by thegarbz · · Score: 1

      Always read at -1, it is the most interesting side of Slashdot.

      Now there's good advice. Right up there with you don't need condoms. Sex is far more interesting without protection :-)

    7. Re:HTTP/2.0 support. by Coren22 · · Score: 1

      Hey, if I didn't read at -1, I never would have seen the treasure that is an APK post.

      --
      APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
    8. Re:HTTP/2.0 support. by Avarist · · Score: 1

      You forgot the rasperry pi hacker competition.

      --
      In Capitalist US, the commerce controls the Government.
  2. no, without linefeeds it says PRI*HTTP/2.0SM by raymorris · · Score: 1

    If you remove the line feeds, you get PRI*HTTP/2.0SM.

    1. Re:no, without linefeeds it says PRI*HTTP/2.0SM by dcollins117 · · Score: 5, Insightful

      So someone added cruft to a communications protocol just to make a political statement? Seems to me that is a very poor reason to make a technical decision. It's not needed, it should be removed.

    2. Re:no, without linefeeds it says PRI*HTTP/2.0SM by Anonymous Coward · · Score: 1

      There needed to be a magic sting to help reject non-http2 at http2 endpoints. It isn't cruft. And it is sent exactly once on a new connection.

    3. Re:no, without linefeeds it says PRI*HTTP/2.0SM by BitterOak · · Score: 2

      Isn't that what the characters "HTTP/2.0" do? How does that not identify it as http2?

      --
      If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
    4. Re:no, without linefeeds it says PRI*HTTP/2.0SM by tepples · · Score: 1

      The use of a new request method (PRI) makes HTTP/1.x servers more likely to (correctly) reject the connection attempt so that the client can cleanly fall back to 1.1.

    5. Re:no, without linefeeds it says PRI*HTTP/2.0SM by dcollins117 · · Score: 1

      The use of a new request method (PRI) makes HTTP/1.x servers more likely to (correctly) reject the connection attempt so that the client can cleanly fall back to 1.1.

      That is not how computers work. They match bits, that's it. To anthropomorphize them because that's the way your brain works is a serious error.

    6. Re:no, without linefeeds it says PRI*HTTP/2.0SM by Jesus_666 · · Score: 3, Insightful

      // HTTP 1.1 is essentially 1.0 so any future version of HTTP will work with our code.
      var weSupportThis = new Regex("^HTTP/\d+\.\d+").IsMatch(header);

      There are many coders out there and many broken ways of detecting protocols. Only changing the version number might run into trouble if one side of the conversation assumes that everything starting with "HTTP" is going to be pretty much equivalent to HTTP/1.0. So at least the "PRI" part makes sense.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    7. Re:no, without linefeeds it says PRI*HTTP/2.0SM by Anonymous Coward · · Score: 1

      And that habit will continue since it works.
      As a result we end up with protocols with more overhead than necessary.

      Wouldn't it be better that those who use broken code suffer instead of everyone else?

    8. Re:no, without linefeeds it says PRI*HTTP/2.0SM by Anonymous Coward · · Score: 1

      > [...] poor reason to make a technical decision.

      Sigh. Yet another "technical ideologist". Thing is, most of those have no clue about technology itself, but tout an ideal in which each and every decision is taken on "technical grounds". Which end up, for the above reason, by being just disguised gut feelings.

      Know what? To do a good job, you should start by differentiating between your gut feelings and technical things (*both* are necessary and useful, but by all means, know which is which). If you can't muster that, you should steer clear of science and engineering.

    9. Re:no, without linefeeds it says PRI*HTTP/2.0SM by dcollins117 · · Score: 1, Funny

      Thank you , Jesus. I see the light. It's way off in the distance, because I am surrounded by imbeciles, by I can see the light. One day, I believe, people will be smart. That's all I can hope for.

    10. Re:no, without linefeeds it says PRI*HTTP/2.0SM by Anonymous Coward · · Score: 1

      It used to be FOO BA\r actually, wouldn't want that shitty pun to go unnoticed;

    11. Re:no, without linefeeds it says PRI*HTTP/2.0SM by AmiMoJo · · Score: 1

      It was originally going to be START, but they found that people were using the START method for various things so changed it to something that hopefully would be less common. At first it was FOOBA, but after Snowden it was changed to PRISM in protest.

      --
      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:no, without linefeeds it says PRI*HTTP/2.0SM by Zontar+The+Mindless · · Score: 1

      > [...] poor reason to make a technical decision.

      Sigh. Yet another "technical ideologist". Thing is, most of those have no clue about technology itself, but tout an ideal in which each and every decision is taken on "technical grounds". Which end up, for the above reason, by being just disguised gut feelings.

      Know what? To do a good job, you should start by differentiating between your gut feelings and technical things (*both* are necessary and useful, but by all means, know which is which). If you can't muster that, you should steer clear of science and engineering.

      Thank you!

      --
      Il n'y a pas de Planet B.
    13. Re:no, without linefeeds it says PRI*HTTP/2.0SM by DarkOx · · Score: 1

      No computers do what they are programmed to do. I would count on the fact there are a lot of 'simplified' HTTP clients and servers out there that look for the string 'HTTP' and not much more. After all if you were implementing something that just needed to exchange a little information over the course of a handful of strait forward GETs or something and wanted to make it HTTP like enough to traverse firewalls be proxied if needed etc, a cut down HTTP implementation is/was a good way to go.

      When it comes to something like that you don't care if its HTTP/1.0 or HTTP/1.1 the differences in the protocol won't impact your use case at all. Given how long HTTP/1.1 has been the standard a lot of stuff probably just assumes that.

      Personally HTTP/2.0 being so radically different and binary to boot is probably a mistake. HTTP is Hyper TEXT transfer protocol, it makes sense that it is text. Future development of HTTP should have been more negotiable human readable text protocols not binary. Which is not to say the modern Internet application could not benefit from a binary protocol there are advantages. I just wish we could have called it WATP web application transport protocol, or something so it was clearly something radically different that won't work with existing proxies etc.

      --
      Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
    14. Re:no, without linefeeds it says PRI*HTTP/2.0SM by LiENUS · · Score: 1

      HTTP is Hyper TEXT transfer protocol, it makes sense that it is text.

      Yes its for transmitting hypertext, ie text documents that contains links to other text documents. IE exactly what HTTP/2.0 is doing. Hypertext refers to the content not the protocol.

    15. Re:no, without linefeeds it says PRI*HTTP/2.0SM by fisted · · Score: 1

      TFcommit says it used to be STA RT, not FOO BA

  3. it took 2 1/2 years... by Anonymous Coward · · Score: 1

    for this to get "noticed"?

    so much for open standards and open source software... 'its safe. you can look at the code yourself"... it took two and a half fucking years for someone to do just that.. and just to find an easter egg, not an embedded and obscured vulnerability.

    1. Re:it took 2 1/2 years... by viperidaenz · · Score: 5, Insightful

      took 2 1/2 years for someone to care

    2. Re:it took 2 1/2 years... by Atmchicago · · Score: 2

      How long would it take for someone to spot something similar in a closed project? Forever?

      --

      You can lead a horse to water, but you can't make it dissolve.

    3. Re:it took 2 1/2 years... by vel-ex-tech · · Score: 1

      Do you have a working Geiger counter?

    4. Re:it took 2 1/2 years... by harperska · · Score: 2

      Forever? Quite probably. Considering the developer who last touched any given source file in a large closed project has probably long since been laid off years before the poor contractor at some Bangalore outsourcing firm tasked with fixing a bug in the aforementioned source file was ever hired.

    5. Re:it took 2 1/2 years... by KGIII · · Score: 1

      Nah, I'm not that smart. It's also not nearly so insightful. Well, maybe, but then I'd have to give you a hint. It is a topical message and there is, indeed, a very open message in there and it's not even remotely hidden if you know what to look for. Given Slashdot user's typical traits, I'd think it'd be obvious but only in hindsight.

      Should I remember (or get a notification on here) then I'll share the "hidden" message or at least some hint. *nods*

      --
      "So long and thanks for all the fish."
    6. Re:it took 2 1/2 years... by Anonymous Coward · · Score: 1

      Your mother's legs are always open and every man can find that.

    7. Re:it took 2 1/2 years... by BradleyUffner · · Score: 1

      How long would it take for someone to spot something similar in a closed project? Forever?

      Considering that this is a communication protocol spec, there is no way something similar could be "closed" in a way that would obscure it.

    8. Re:it took 2 1/2 years... by BronsCon · · Score: 1

      Mine is in the shop.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    9. Re:it took 2 1/2 years... by thegarbz · · Score: 4, Insightful

      No. It took this long for someone to post it to Slashdot.

      People still don't care.

    10. Re:it took 2 1/2 years... by Sique · · Score: 1

      Considering that there are enough proprietary communication protocols around, whose specs are never disclosed at all, or where you have to pay money and sign a non disclosure agreement prior to getting a look at them, there are enough ways for them to be closed.

      --
      .sig: Sique *sigh*
    11. Re:it took 2 1/2 years... by jellomizer · · Score: 1

      That is probably more like it. The real down side I see it being connected to such a thing is if some techy guy who isn't awair of the protocol standard port sniffs the code and he thinks that he is being targeted by the NSA.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    12. Re:it took 2 1/2 years... by Stewie241 · · Score: 1

      Except that there are things like Wireshark and other tools that let you sniff packets and see what is inside them. If it's widely used enough somebody is going to have tried.

    13. Re:it took 2 1/2 years... by tsqr · · Score: 1

      The hidden message? It's right there - between "spot " and ". It's"

    14. Re:it took 2 1/2 years... by swillden · · Score: 1

      for this to get "noticed"?

      so much for open standards and open source software... 'its safe. you can look at the code yourself"... it took two and a half fucking years for someone to do just that.. and just to find an easter egg, not an embedded and obscured vulnerability.

      No, it didn't take 2.5 years to get noticed. Look at the comments on the final commit, it was noticed and commented on by another team member the same day it went in. https://github.com/http2/http2...

      The public didn't notice, but I'm sure many people involved in the project did... the commit wasn't in any way obscured. It just wasn't interesting enough for anyone else to notice.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    15. Re:it took 2 1/2 years... by allo · · Score: 1

      when it's so obvious, the NSA must be really stupid.

  4. So who did it? by 140Mandak262Jamuna · · Score: 5, Interesting
    It should be possible to find out who did the code chage, who approved the change and who merged it.

    One of our coders used a limerick, yes it was the man from Nantucket, as a static string. He used it to test some of the string utility functions he was developing. Forgot to remove it. Eventually a nosy customer found it by running strings on our executable and made a stink about it. (Never explained why they were poking around our executable with strings) It is out of our builds now, but if you do a blame on stingutils.cpp you can still see it and see how long it stayed in production.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    1. Re:So who did it? by dcollins117 · · Score: 1

      It should be possible to find out who did the code chage, who approved the change and who merged it.

      There is a link to the commit in TFS. It is worth looking at if only to see the first (and at this time, only) comment to the commit.

    2. Re:So who did it? by epyT-R · · Score: 1

      (Never explained why they were poking around our executable with strings)

      It's on his computer. That gives him the right.

    3. Re:So who did it? by Anonymous Coward · · Score: 1

      (Never explained why they were poking around our executable with strings)

      It's on his computer. That gives him the right.

      A person with code in his possession does not automatically give him the right to do whatever he wants with it, anymore than having windows on his computer allows him allows him to disasseble it and reuse it's code, or having a video on his computer gives him the right to edit and republish it.

      That said, there is nothing to stop him from doing whatever he wants with what he has in his possession. Whatever he chooses to do, he may not have the right to do so, and there may be repercussions.

    4. Re:So who did it? by dotancohen · · Score: 1

      A friend of mine who worked for PDI (creators of Antz, Shrek, etc, later bought by Dreamworks) said one of his coworkers grepped their source code for "fuck" and there were so many comments using it, he turned it into a poem...

      Go grep around the Linux source code. It would make a sailer blush.

      --
      It is dangerous to be right when the government is wrong.
    5. Re:So who did it? by stoborrobots · · Score: 1

      Agreed - they have the right.

      However, the question was "why were they doing it?", not "were they doing something wrong?"

    6. Re:So who did it? by Anonymous Coward · · Score: 1

      Disassembling Windows is perfectly legal (at least in my country) and I consider it ludicrous to think otherwise. Code is text. If it's in front of me, I can read it.

    7. Re:So who did it? by Dog-Cow · · Score: 2

      The GP never implied the customer didn't have the right.

    8. Re:So who did it? by 140Mandak262Jamuna · · Score: 1

      Well, you remember the limerick well, sadly the mods don't seem to.

      --
      sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
    9. Re:So who did it? by allo · · Score: 1

      It does. But it does not give you the right to redistribute the result (as long as its not fair use) and no right to demand change from the vendor.

  5. Taco left four years ago by tepples · · Score: 1

    There haven't been tacos on Slashdot since Mr. Malda left four years ago.

  6. Re:Hello by Anonymous Coward · · Score: 1

    Is this was slashdot has come to?

  7. Re:Isn't it how Enigma was broken? by KGIII · · Score: 1

    If that's true then, AFAIK, headers have always had some form of constant and, if not, there's consistent content in the individual packets that identify things like what stream they belong to.

    --
    "So long and thanks for all the fish."
  8. 2.5 years... by Anonymous Coward · · Score: 1

    and suddenly now we give a fuck?

  9. Re:Isn't it how Enigma was broken? by gumbi+west · · Score: 1

    Right, but not all headers can be encrypted. e.g. your letter still needs an unencrypted address or it can't be delivered.

  10. Re:Sucks to see the Republucans... by ganjadude · · Score: 1

    its the same person posting like 8 times, he does this in everythread these days. i guess he likes talking to himself

    --
    have you seen my sig? there are many others like it but none that are the same
  11. Poor word choice by sootman · · Score: 1

    "Each new connection forged by the HTTP/2.0 protocol..."
     
    So is that...
    * forge (verb) 2. To form or create with concerted effort.
    or
    * forge (verb) 4. To create a forgery of; to make a counterfeit item of; to copy or imitate unlawfully.
    ?
     
    https://en.wiktionary.org/wiki/forge

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
  12. uaggressions by tepples · · Score: 1, Troll

    microaggressive behavior

    What, as in it'd take a million of them to cause even one real problem?

  13. No, they did not. by Anonymous Coward · · Score: 1

    They needed a magic value to recognize HTTP/2.0 servers that would reliably fail on existing ones. As magic values are arbitrary, this one was good enough (i.e. actually fails on almost all servers), they simply picked something and moved on.

    This is NOT something extra or unnecessary added to HTTP/2.0, it's just something arbitrary that they happened to pick as a "magic" value, not unlike those commonly found in most file formats.

  14. Re:Wasting time on "cute" things? by GrandCow · · Score: 1

    Yes... all 30 seconds or so were wasted.

    --
    "Well kids, you tried your best, and you failed. The lesson is, never try." -Homer Simpson
  15. Re:Martin Thomson by dave420 · · Score: 1

    Please be quiet - adults are trying to talk.

  16. Re:Isn't it how Enigma was broken? by KGIII · · Score: 1

    That's kind of what I was thinking - I wasn't sure that their comment was even salient but I'm not a crypto-geek and I knew that headers have pretty much always contained repeatable data and that it's not made a difference (AFAIK) so far. I probably should have phrased it better. I do know, by grace of having to learn a bunch, some basic networking but not a lot of crypto - enough to implement it if needed. I understand things like SYN and ACK, UDP, etc... I did not have the budget to hire a network admin (lots of years ago) and spent lots of time learning about it. I think the important thing I learned was to drop Cisco and go Juniper. *nods* But, I digress.

    --
    "So long and thanks for all the fish."
  17. Summary should be clearer by dabadab · · Score: 1

    Does this apply only to forged connections or also to legit ones?

    --
    Real life is overrated.
  18. Re:Martin Thomson by gweihir · · Score: 1

    Slander term used by people that think normal is somehow icky. (The variety of fuckups in the human race is both endless and astonishing....)

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  19. Your allergy to anthropomorphism by tepples · · Score: 1

    To anthropomorphize them because that's the way your brain works is a serious error.

    It's called "colloquial language", and it appears to have got the point across to most other readers. But if you insist on discussing the process more formally in terms of "matching bits":

    The PRI request method matches none of the methods in a pre-HTTP/2.0 server's list of acceptable methods. This causes the server to write a response that does not match the HTTP/2.0 upgrade pattern, even if the server's matching of the protocol version bits is incorrect. When the response fails to match at the client, the client switches to HTTP/1.1.

  20. Re:The bitchslapping of Dave420 #2/2... apk by Coren22 · · Score: 1

    Are you sure Tepples supports you?

    For those of us who are logged in, here is what your link points to:

    APK agrees that hosts files are only one component in a layered security strategy [slashdot.org]. Eight years ago, he wrote a detailed article about the other layers [neowin.net].

    --
    Hosts file disadvantages: No wildcards, no NXDOMAIN, slow linear search, no per-user, no whole-LAN protection

    I don't see him agreeing with you anywhere. He in fact strictly disagrees with you in part of that message. You really should use your account, it will change your world to see all those signatures you hate so much.

    No complaints from me, I like APK's spam. Reminds me to use a host file. Also, his stuff is free.

    Arg (don't feel like counting the a's, sorry) doesn't actually say he uses your software, just that he uses hosts files.

    And that KGIII post you link to has nothing to do with hosts files, he is saying that you likely aren't the GNAA troll, what does that have to do with your software?

    Perhaps if you are trying to post links to people supporting you, you should actually post links to people supporting you?

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  21. Re:Hello by Coren22 · · Score: 1

    You are funny, you wish you could even get things right once, but yet still fail utterly to prove your way out of a paper bag.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  22. Re:The bitchslapping of Dave420 #2/2... apk by Coren22 · · Score: 1

    If you could read, you wouldn't still be arguing. It has been proven out that you cannot read repeatedly, including right here, as you didn't read any of the posts you linked to.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  23. Re:Unprofessional by Coren22 · · Score: 1

    A CIA Bug.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  24. Re:Martin Thomson by gweihir · · Score: 1

    I already did by identifying you as a "fuckup". Which you clearly are.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  25. Re:Martin Thomson by ganjadude · · Score: 1

    not sure how this is troll when it is scientifically correct. this is not a knock at anyone, simply the scientific truth

    --
    have you seen my sig? there are many others like it but none that are the same
  26. Re:The treasures that broke you in 1/2 by Coren22 · · Score: 1

    Wow, you really are special.

    When you try to compare hosts to remote DNS, you are missing the point. You should be comparing hosts to local DNS, and DNS is faster on every count.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  27. Re:*SNAP* goes Coren22's leg... apk by Coren22 · · Score: 1

    It would be hilarious if you actually got something right for once, but sadly no, I will now proceed to tear your argument apart.

    "except on the hard coded favorites, and even then if they make calls to non hard coded sites, they will take forever" - by Coren22 (1625475) on Tuesday December 01, 2015 @10:02AM (#51033517)

    See subject: 1st of all you stupid fuck, ads I block alone buys that speed back on the RARE sub 4% times I need DNS - get it? Good!

    You CANNOT compare hosts to local DNS with the same records. Yet you continue to try. The ads you block are also on the DNS side, so how can you count the time you save there? If the DNS has the exact same records as your hosts file, every site will load faster. You don't make up the time with the ads you aren't loading, as they also are not loaded with the DNS example. How can you live with such a low IQ?

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  28. Re:I am special: You're ESPECIALLY stupid! by Coren22 · · Score: 1

    Compared to your horribly inefficient Hosts file, even remote DNS comes out so far ahead it isn't even funny. But keep trying to claim your hosts file outperforms local DNS, when it flatly does not.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  29. Re:No "moving the goalposts" Coren22 by Coren22 · · Score: 1

    So, how is it a fuckup that you decide to ignore the ad blocking the local DNS server is doing in your figuring? I see a fuckup, but not on my side.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  30. Re:Learn to READ: DNS = security issues AND? by Coren22 · · Score: 1

    No it isn't.

    DNS running locally is kept up to date in patches, it is not a security issue. DNS uses less resources and speeds your browsing, leading to more power savings. Why would you setup a separate system? https://www.isc.org/downloads/ The need for the locally setup DNS is the exact same need as the need for your terrible hosts file, so that argument is silly. Keep reaching and moving the goal posts.

    due to your LIMITED MENTALLY DAMAGED GOOD ASSBURGERS BRAIN being only able to hold 1 of MANY variable factors in play @ a time

    Stay classy.

    (sub 4% of the time ONLY for me due to hardcoded favorites in hosts @ the TOP of it cached in RAM locally)? Adblocking gains me back lookup speeds if a total miss & I have to hit DNS remotely.

    You mean the same ad blocking you gain with a local dns setup with the same entries? Or did your ability to hold onto only one variable catch you again?

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  31. Re:Coren22's "engineering" = Bolt on 'MoAr', lol by Coren22 · · Score: 1

    Less is more, I totally agree! This is why I suggest running BIND with the entries, as it is more efficient on power, and faster in processing. It uses way less power and time, and speeds up your browsing many fold over your 2 million plus record hosts file!

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  32. Re:Coren22 is this you quoted? Yes by barbariccow · · Score: 1

    This is garbage. Literally this entire thread is APK spewing foam and cohen22 shooting him with a nerf gun.

  33. Re:Windows desktop editions = most used by Coren22 · · Score: 1

    You know what they call people like you? Zealots. You can't see that you have already lost your argument, so you keep making the same points over and over, despite them already being proved wrong. Keep up the crusade!

    BIND can run on any computer, including desktops. It therefore uses less power/resources than your hosts file, as your name resolution is sped up many fold, so you don't wait on your queries as long. It also can be setup to block the very same records, so it is still faster than your ad blocking, as it is doing that as well. So, when you have an actual argument against BIND, let me know, until then, you have lost, go home and cry into your pillow.

    --
    APK likes to ask for responses to the same things over and over. Maybe he just likes the responses?
  34. Re:Read Coren22's impersonation "APKolypse" by Zontar+The+Mindless · · Score: 1

    Absolutely not me.

    Almost wish it was, though.

    --
    Il n'y a pas de Planet B.
  35. Re:Read Coren22's impersonation "APKolypse" by Zontar+The+Mindless · · Score: 1

    Darn, I was just starting to enjoy your work, seemed to shaping up nicely.

    --
    Il n'y a pas de Planet B.
  36. Re:Martin Thomson by Zontar+The+Mindless · · Score: 1

    Wow, a -1, Informative. First time for everything, heh.

    --
    Il n'y a pas de Planet B.