Slashdot Mirror


User: evilrip

evilrip's activity in the archive.

Stories
0
Comments
30
First seen
Last seen
Profile
(view on slashdot.org)

Comments · 30

  1. Re:censorship much? on High Court Orders UK ISPs To Block EBook Sites · · Score: 2

    Fascism, hypocrisy, etc :) when are we all going to start calling it what it really is? :) On the other hand, one tends to want security and control for the ones we love (or are responsible for, perhaps more for our sakes than theirs?), autonomy for ourselves. Maybe it is time to realize other people want autonomy too, so we can strike the correct balance?

  2. censorship much? on High Court Orders UK ISPs To Block EBook Sites · · Score: 1

    so, is the UK going to have any internet access left once everyone has gotten everything they do not like? welcome to the age of fascism. franco, mussolini, the stasi, etc. would all have huge boners if they were around for this, the surveillance age :)

  3. not hackers. on Stanford Researcher Finds Little To Love In Would-Be Hacker Marketplace · · Score: 1

    Can we stop calling common criminals for hackers? Some of us are starting to get really offended, to the point we wonder how anyone of you ever made it out of grade school. Maybe the word you were looking for was "cracker"? rtfm.

  4. I think mrs. reagan got this one on Security Researchers Wary of Wassenaar Rules · · Score: 1

    Just say no.

  5. Re:News? on How To Conduct Your Very Own Buffer Overflow · · Score: 3, Insightful

    Uhm , if all the hardening make the distros so secure, why are they still getting owned via one or another variant of the buffer overflow (stack or heap based, overflowed, underflowed, integer manipulation, etc). Although I agree that the point of entry often is via other types of attacks when the attack is happening from a remote location and not locally, say like php-code injection, sql-manipulation, perl fun, etc. The x86 especially has poor protection from attacks of the buffer overflow kind as most protection is software based, which is really a failed approach. That said, make no mistake and think that a cpu with a no-exec bit for writeable pages or similar will make you entirely safe either. The x86 isn't alone about this problem but it sure is amongst the most vulnerable to it. Thankfully, exploiting buffer overflows is becoming harder even on the x86(depending on OS, hardware, etc), but it's still far from immune. This was alotta text to waste just to say what others have said time and time again before me. And everyone knows about the legendary phrack(p49 article 14) article by alephone that beat this one by what, 9 years?