Windows flaw...

[ibneko]

http://searchsecurity.techtarget.com/originalContent/0,289142,sid14_gci949830,00.html?track=NL-102

Supposed to be a really big one. Again, I rejoice in using a mac~

--
...I just found out about Kagan. -.-;;; Test tomorrow, just got packet today. Curse the stupid schedule conflicts. I guess we got them on the first full day back, eh? :P ::sighs:: Now to read all 52[edit | I can't count. that should be:] 27 pages... sucksucksucks. And Mr. Hines tells me that I got a 0 on the first CNQ...

--
Oh, yeah, and Time talked about shoujo manga and pointed out Fruits Basket. The summary sucked.

[ edit | Time, not Times ]

Comments

Re:

[ibneko.livejournal.com]

::nods:: I agree... 200 days is a bit extreme. I'd say 1/4 of that delay would be the max people should have to wait for such a critical patch.
they were afraid of making the problem worse?
Well, with big chunks of code modified and patched so many times, and with many versions out there, testing for bugs spawned by the patch would be needed... It would look even worse to release a patch that broke other things. It shouldn't take them that long though.

Yes, employment is good. hehe, chief hacking officer.

Someone needs to write a program (or shell or emulator that would run multiple programs within it in a "sandbox") that would simulate a human so it can test for problems and bugs... For example, if you load, say, microsoft office, it would test all clickable, user accessable parts of the program by simulating mouseclicks and keyboard input, testing for speed, bugs, etc. as well as network related and OS related things... It would take quite a bit of time to run, I suppose, but if you distribute it over a network of computers and have each of them test an area of the program, it should run fairly quickly...