Ok, so the article itself left out that word (on purpose? clickbait? bad journalism?).

But slashdot editors should notice that and call it out with an editorial fix/comment.

FTFY

Slashdot, stop trying to confuse us by leaving out words.

Yes and no.

What she found was one reader that in one spot will interpret and display values that exceed the maximum mentioned in the spec for MediaBox. (But it's not like it's actually using those values elsewhere; e.g., File -> Print just shows Page 1 of 1.)

What she didn't find was any reader that supports a UserUnit larger than the 75,000 maximum allowed by Acrobat 7.0.

However, it is true that UserUnit has no limit per the spec "The range of supported values shall be implementation-dependent.".

The "myth of a 381 km x 381 km maximum PDF size" is debunked by that line in the spec, not by the fact that she found a reader that in one spot exceeds the max specified in a different part of the spec.

Clarification:
The 5.25-inch floppy was 360K and 1.2MB.
The 3.25-inch floppy was 720K and 1.44MB.

CMake is easy too.

An old open-source tool called hypermail may be what you're looking for. It parses mbox files and produces HTML pages with the emails sorted by thread, author, subject, date, etc. http://hypermail-project.org/

The expert colleague actually got the *wrong* answer for xy_common. To me, that is the most interesting part of this experiment! What does that tell us? Maybe the "experts" could learn a thing or two from the novices, e.g., slow down a bit and verify results :)

It is pretty sad though how many of the apps don't encrypt the user data at all, or it's encrypted but the master password is stored in plaintext or is encrypted with a hard-coded key. Then there's many of them using strong crypto algs but not properly (e.g., what is the point of using PBKDF2 but with only 3 iterations?)

Mod parent up. The NT hash is essentially just a single MD4 of the Unicode password. (In the SAM file the hash is also obfuscated with the RID and encrypted with the syskey, but RID obfuscation is easily removed and the syskey by default is just stored in the registry and can be easily extracted.) MS should have deprecated the NT hash like they did the LM hash, and replaced it with a salted iterative hash like PBKDF2.

Do I really want my CPU to overload while navigating the web?

Yeah, but we're talking about digital displays not camera lenses. The term resolution has always been used to mean pixel dimensions.

If you just need debugging, try cgdb. It's very lightweight.

The OST file format is pretty much identical to PST.

Exactly. I worked around it and if I hadn't been able to I probably would have quit. The vpn client for windows enforced the company policy, but the vpn client for linux let me set up split tunelling the way I wanted. So I set up a linux router/firewall and never looked back.

I blogged about it last year: http://hellewell.homeip.net/phillip/blogs/index.php?entry=entry080509-170319

Ok, my curioisty got the best of me. I altered the program to do 100 tests with a random stopping point each time. My results are:

Begins with 1: 20.57%
Begins with 2: 17.69%
Begins with 3: 15.35%
Begins with 4: 13.26%
Begins with 5: 10.86%
Begins with 6: 8.0%
Begins with 7: 6.14%
Begins with 8: 5.1%
Begins with 9: 3.7%

I'm still not seeing the 30% mentioned in the article, but it is a lot closer. Perhaps if I modified it to test a random # of primes instead of test up to a random # that would make a difference, but it doesn't seem like it would.