Slashdot Mirror


User: Binary+Air

Binary+Air's activity in the archive.

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

Comments · 6

  1. Education on Britons Unconvinced on Evolution · · Score: 1

    Apparently the education system is faltering across the pond too. "...but we're all well educated athiests..."

  2. Not a big deal on Windows 2000 & Windows NT 4 Source Code Leaks · · Score: 1

    "Thor Larholm, senior security researcher at Newport Beach, Calif.-based PivX Solutions, said the Windows source code file being traded on the Internet appears to be roughly 660 megabytes in size, about the size of one CD-ROM's worth of data. That is far short of the estimated 40 gigabytes of data that makes up the entire 40 million lines of code in the Windows operating system." [WashingtonPost.com}

  3. Re:Bogus Bogus Bogus -- MS confirmed it's real on Windows 2000 & Windows NT 4 Source Code Leaks · · Score: 1

    I don't doubt that some source has been "outed", but the entire base...or even a critical part of the base. I don't think so. Cheers!

  4. Bogus Bogus Bogus on Windows 2000 & Windows NT 4 Source Code Leaks · · Score: 2, Funny

    It's amazing how the "informed" slashdot crowd falls for a story like this. I think Neowin wanted to test their infrastructure so they trolled /.

  5. Re:Backdoors in the brain on Do You Write Backdoors? · · Score: 1

    You assume perfection of the platform, tools and language; wich of course doesn't exist. Of course any designer of a given system can "break" the system. To believe otherwise is a matter of inexperience and possibly wishful thinking. Cheers, Binary Air

  6. Backdoors in the brain on Do You Write Backdoors? · · Score: 3, Insightful

    I have been developing software in some form or another ranging from ascii based games to multi-tier web applications, since I was 8. I'm now 30 and I can say without hesitation that even without explicitly coding a backdoor a "good" developer can get into and exploit a system of his/her own design and development simply as a result of an intimate understanding of the application and how it handles data. So the only way to really prevent this, if you were really that worried about it, would be to labotomize the developer or somehow wipe his/her memory. Cheers, Binary Air