Cool, now Copernicus has an element named after him.
Cool, now Copernicus has an element named after him.
LZW isn't that bad. And mostly, I just needed to know what it did WRONG, not how to do it RIGHT. I'd already learned how LZSS worked the previous year...for an also ambitious project that never really saw the light of day. Reverse engineering a compression format through raw tinkering and seeing how outputs changed was a lot of fun^H^H^Htedium. It helped that I had a lead that it was probably some derivative of LZ77.
Okay yeah I might have spent a lot of time on nothing substantial during this, but it did yield a security patch, which is a good thing. And besides, I was on winter break from college. It's a good time for doing nothing substantial.
Actually, I personally found and patched the TIFF bug. In January. Of last year. http://bugzilla.maptools.org/show_bug.cgi?id=1985
Feeding random data (aka fuzzing) might work, but 99% of the time, I'd imagine it'd just give you a corrupted image and bail out. You have to be clever about how you search for it. I found a known vulnerability patch posted by, of all people, an Apple employee, and tried to reverse engineer what he'd fixed. I found that the patch hadn't been applied on old version of the PSP system software, which is what I was targeting. After messing with this specific attack vector, I noticed that I could still crash system software version that did have the patch. After reading up on LZW compression (which is what part of LibTIFF had the vulnerability) and the TIFF specification of how they implemented LZW, I realized that the Apple patch was incomplete--it only tested for one value you could give it that was erroneous. By simply changing the equality they used (in two places) to an inequality, I tested for all erroneous values. Meanwhile, I tried to exploit the new unpatched vector on the PSP so that I could inject code. Failing this, I decided the best course of action was to submit a bug report to LibTIFF. It might seem a tad unethical to try and exploit the bug before reporting it, but I wasn't trying to exploit in for malicious purposes, and not on a desktop operating system. Regardless, I failed to make it do more than crash the PSP. Surely the best course of action here would be to patch it upstream before anyone else found it. (Incidentally, this "arbitrary execution" this is blown out of proportion. In its current state, it is extremely unlikely that it could provide ANY code execution. Just crashing. Although I don't know if it's IMPOSSIBLE for it to execute code with this vulnerability, it would take a lot of work to get anything valuable out of this. Mostly it's a DoS. They usually just attach "arbitrary execution" when there's even the vaguest possibility for code to be executed, regardless of whether or not such an exploit has been demonstrated.)
It, um, took a while for anyone to notice the patch. In fact, the only reason anyone did notice was because someone found some of the fruit of my research into this bug and then posted a link to the research in a new bug report. Funnily, they created a different patch, which, instead of preventing the infinite loop caused by the erroneous data, just tested to see if the loop was writing out of bounds. Perhaps both approaches should be used together. Defensive programming and all that. Regardless, I noticed this new bug report shortly afterward it was posted and pointed them back to the inexplicably ignored old bug report. Most Linux vendors applied the patch shortly after the new bug report was filed, but Apple lagged by a number of months, until 10.6.2 came out. This update backports the fix into 10.5.x. However, I've found that some projects (such as Qt) are still using ancient versions of LibTIFF that have had numerous bug and security fixes since they were last updated in the projects' trees. While Qt does try to use the system's version of Qt if it can, it's still kind of scary to think about what could happen if it falls back on its own version, as I've seen it do before when I try my "corrupted" TIFF on things like Arora.
Incidentally, I am TAing a computer security course this semester. I guess previous experience helps.
I don't think you understand. If this is a 12, Disaster Area is somewhere hovering around a 400 or so.
Alright, alright! I'll admit it. One of them is a FreeBSD ISO. There, are you happy now?
DVD images are generally >1GB and always 9GB (for dual layer), so I'd imagine a lot of us of some of those.
They're Linux ISOs, of course.
Yeah, I use scroll-scroll with KVMs, but remember, this is a laptop. KVMs...are not typically used with laptops.
I never said it was right. They just did it. I'm on a Mac right now, and I switched it so that the F* keys are the F* keys again because the other way bothers me.
I also notice the Scroll Lock and Pause/Break keys are missing. I know you can use the Scroll Lock key in conjunction with Excel, but I'm not sure anyone else ever does. Although I have actually used it on the command line to, shock and awe, lock the screen from scrolling while it was booting up so I could see error messages before they disappeared into the dust.
Also, switching the F keys with the functionality usually relegated to Fn-F*, as mentioned in TFA, is nothing new. Apple has been doing that on their laptops for years.
For those of you who haven't figured out what the poll is asking yet, it's asking "How long until I consistently write 2010 in the date."
That's basically what the Wii's Virtual Console is. Only caveat is that you have to have a Wii to play them. And, well, you're not SUPPOSED to be able to copy them, but there are hacks that let you.
Disregard the "Copyright Shogmaster 2007" and you still get a hoax that doesn't look believable.
This is my point. Ridiculously minute is a relative thing here. Sure, 100 billion is a big number. Sure, Avogadro's number is a LOT bigger. However, I don't imagine they'd be needing quite that many particles for what they're doing. But really, I don't know. I'm not a physicist, I'm just speculating. 100 billion seems like a lot of particles to be smashing together in a linear accelerator, though.
If you call hundreds of billions ridiculously minute, then maybe.
With a username like "celibate for life", they don't really have to invent anything to tell you're a virgin.
The shortest distance between two points is under construction. -- Noelie Alito