- Jan 18, 2012
Firstly... I just want to point out some irony between this (and several of your posts) and this:The Cool Kid said:That link is just more shit.Phopojijo said:Yeah I was pointed to this thread by Leam (a friend of my girlfriend), so I created an account to correct you (note the 3 post count and 3 posts in this thread).
And you know little about SOPA/PIPA despite your crowing... the same sort of crowing you did about security when you were obviously way over your head. You vaguely claim to read the bill, yet you rarely ever actually state a direct problem -- exactly how you tackle the security issue.
If you're so serious, point out a *specific and detailed* issue with SOPA that has been misunderstood... and then likely someone will swing by and prove you wrong.
Until then, crowing does not equal knowledge.
Example, the issue with SOPA related to security is not with SSL or anything like that, it's with DNSSEC authentication.
Steve Gibson, GRC --> http://youtu.be/1y-YE0I0n9Y?t=15m00s
Steve: Lamar Smith, who is the Texas Republican representative who's one of the sponsors of this bill, the SOPA, Stop Online Privacy ((he meant Piracy)) Act bill, he said, "Well, you know, I'm not technical." Well, okay. And this is the problem, is that one of the many things this does is it breaks DNSSEC. That is, DNSSEC is all about preventing DNS spoofing, which is essentially what this is, is legislated, government-backed DNS spoofing. And so many of the people have been concerned because essentially it means we can't have DNS security if we're going to have a mandated, legislated, deliberate breakage of DNS.
So you're wrong.
They make a claim but never follow it with facts and I don't have the strength to listen to vacuous propaganda.
Here is an issue with SOPA that has been misunderstood; "It'll break the internet"
What a retarded statement. DNS blocking is flawed, but at least it is something. It will in no way break the internet. And let's not forget, if your server is on US soil, you can expect harsher legal action.
And how does it break DNS? You type in a torrent site, this is cross checked with a DNS blacklist and you are redirected to a blocking site.
How is that breaking DNS? That's like saying stopping people for speeding will ruin traffic. Everywhere. Forever.
Hollow claims, huh? Pot-kettle... only in this case the kettle's orange.The Cool Kid said:And I know nothing about SOPA why? Because you claim it? Want to back that up or just going to leave it as a hollow claim?
Secondly -- you don't know what you're talking about... don't worry though, I'll prove you don't. But you apparently think you know more than a professional security researcher who coined the word "Spyware" and discovered vulnerabilities in firewalls about a decade ago.
How about another security researcher? He puts it in specific albeit easy-to-understand terms.
Why does that break DNSSEC?"From an operational standpoint, a resolution failure from a nameserver subject to a court order and from a hacked nameserver would be indistinguishable. Users running secure applications have a need to distinguish between policy-based failures and failures caused, for example, by the presence of an attack or a hostile network, or else downgrade attacks would likely be prolific."
In other words: A lot of security flaws stem from spoofing DNS entries -- a man in the middle (such as someone on public wifi who gets your computer to believe his computer is your router) can interscept your DNS requests and send you a false one in return. You could send a request to http://www.facebook.com and he could send you back the IP address for http://iwilltotallystealyourfacebooklogin.com. With SOPA, the false censorship request is indistinguishable from a false fraudulent request.DNS Cache Poisoning: "DNS cache poisoning is a security or data integrity compromise in the Domain Name System (DNS). The compromise occurs when data is introduced into a DNS name server's cache database that did not originate from authoritative DNS sources. It may be a deliberate attempt of a maliciously crafted attack on a name server. It may also be an unintended result of a misconfiguration of a DNS cache or from improper software design of DNS applications.
Secure DNS (DNSSEC) uses cryptographic electronic signatures signed with a trusted public key certificate to determine the authenticity of data. DNSSEC can counter cache poisoning attacks, but as of 2008 was not yet widely deployed. In 2010 DNSSEC was implemented in the Internet root zone servers."
Seriously, we're not joking. Just because you don't understand it doesn't mean it doesn't exist. It's like the mythical Ostrich who thinks "If I can't see him, he can't see me!"