pwnt.be

If you’ve ever made multiple credit card payments on the same web site, you may very well have been shocked to learn that your browser had remembered your credit card information. This means that, if you send your machine in for repairs, the technician can easily use it for evil—and don’t even get me started on public computers.

Accepted Here by roujo
Some rights reserved

The reason is that there are a lot of otherwise respectable web sites which neglect to use the autocomplete attribute. Since every modern-day browser comes with form autocompletion, this is the sort of thing that’ll affect a lot of users. And while most payment gateways take all sorts of precautions to prevent abuse, having your credit card information in the wild is obviously still something you’ll want to avoid.

Luckily, most of those same modern web browsers also come with some implementation of private browsing these days. Not only are private browsing sessions great for looking at porn, but they are also invaluable if you’re going to be entering any sort of sensitive information. In Google Chrome, for instance, just hit Ctrl-Shift-N and you’re all set. Users of Mozilla Firefox can use Ctrl-Shift-P instead.

Of course, after reading this, your first instinct will probably be to clear your browser’s autocomplete data. However, if you’re using Chrome or Firefox, you don’t need to take such a drastic approach.

You see, both these web browsers store most of your data in SQLite databases, which are ordinary relational databases, each contained in a single file. The files I’m talking about are located in your Chrome user data directory or your Firefox profile folder. The former contains a database called Web Data; the latter calls it formhistory.sqlite.

Now, if you grab the free command line SQLite client, you can freely play around with those databases. First, make sure you close all open browser windows, or the files will be locked. Then, fire up a Command Prompt window, navigate to your user data directory or profile folder, and enter either of these commands, depending on your browser:

sqlite3 "Web Data"

sqlite3 formhistory.sqlite

That should bring up an SQLite prompt, where you can now search for any table rows pertaining to sensitive information. For instance, if the first four digits of your card number were 5678, you would check for any values starting with that sequence using the following query:

SELECT * FROM autofill WHERE value LIKE "5678%";

SELECT * FROM moz_autocomplete WHERE value LIKE "5678%";

If that doesn’t return anything, then rejoice, for your credit card number probably isn’t stored in the file. Got some matches? Fear not, you can easily remove them. Just alter the query so it drops matching rows:

DELETE FROM autofill WHERE value LIKE "5678%";

DELETE FROM moz_autocomplete WHERE value LIKE "5678%";

Finally, type .quit to get out of the SQLite client, restart your browser, and you’ll be good to go. Next time, remember to use porn mode!

ohjo maat, checkt da
moet zien, ’t is wa zwaar de max
nen ’aiku en al

If you came here expecting a list of interesting facts about prophylactics, you’ll probably want to be moseying along. This post is, in fact, my opinion on the LaTeX typesetting system. Prepare for heavy bias.

GoodTimeHadByAll by brutal
Some rights reserved

1. WYSIWYM—What You See Is What You Mean

   Many people argue that LaTeX is intuitive. It isn’t. Sure, if you stick to a document with a couple of headings, some plain old paragraphs, and maybe some bold text, it’ll look okay. But the moment you dive into figures, tables, or pretty much anything supported by packages, WYSIWYM becomes WYSIWLWYTM—What You See Is What LaTeX Wants You To Mean.

2. LaTeX is easy to learn

   No, it looks as though it’s easy to learn. In reality, you’ll spend countless hours googling for answers to questions no one has seemingly ever asked before, copy-pasting code you can’t make sense of, wondering why a table ended up on the wrong page or why space was added which you didn’t think you’d requested, and asking yourself why you didn’t just use a proper word processor. Also, if you’re going to be writing TeX code, don’t expect to get very far without content assistance from an advanced editor or IDE.

3. Compilation errors are easy to trace

   Everyone makes mistakes, right? So you’d expect LaTeX to spit out error messages which more or less tell you what’s wrong: the package where stuff went haywire, the line on which the error occurred, maybe even a hint towards a fix? Yeah … Most of the time, it’s better not to expect any of that.

4. Computer Modern is an excellent all-purpose font

   Seriously? At most, it’s a good font for testing your stuff out, because if even the default font doesn’t like your document, you might as well give up. Unless you want people to think you wrote the document decades ago, don’t use Computer Modern. Of course, the main reason for sticking with the poor bastard is that switching fonts is a pain in the ass—XeTeX or no XeTeX. For instance, if you include the times package, that’ll change your text font to Times, but it’ll also change your typewriter font to Courier, while keeping Computer Modern as the math font. Yeah, that makes sense. Of course, all you need to do to use Times for math is add the mathptmx package—which brings me to my next point …

5. It’s easy to find a package to meet your needs

   No matter how trivial whatever you’re trying to accomplish may seem, LaTeX probably won’t be able to do it by default. But packages solve that, right? Wrong. Even if the package you want exists, it’ll most likely have an obscure name and throw an absurdly extensive and complex manual at you, because sensible defaults and intuitive commands are unheard of in the LaTeX community.

6. Packages can be mixed indefinitely

   Think twice before you add a new package to your document. Not only will it affect the behavior of the other ones you already had, it might even break compilation altogether. And, once again, don’t expect to be able to make sense of the error messages it spits out. What’s more, each package has its own ideas about margins, fonts and whatnot. Good luck getting them to match.

7. LaTeX is the de facto standard for scientific documents

   No, boring layouts are the de facto standard. You can just as easily do those using a WYSIWYG editor. And by “easily”, I mean you’d better hope someone provides you with a template, because whether you’re using LaTeX or Word, it’s going to be a bitch. The fact of the matter is, no single typesetting system or word processor’s defaults will help you survive in the science community. Of course, any approach has its benefits. For example, if you need to use a lot of math, Word’s formula editor is going to be the root of many a headache, but then, there’s always OpenOffice.org Writer with its LaTeX-like math syntax.

8. Having multiple output formats is a blessing

   It is, but not for LaTeX. If you switch to a different driver, don’t expect your document to come out the same. Included figures will break, packages will complain even if you explicitly configure them to support the driver, and you’ll discover new quirks you didn’t even know your document had. And when you’ve finally managed to work around those, you’ll notice you’ve just created new ones.

9. BibTeX is a great way to manage references

   Give me a fucking break. Never mind the fact that you have to invoke latex three times before your BibTeX-backed document makes sense, but the whole system is retarded. It was a good idea, but like TeX itself, BibTeX has gotten so cluttered that any sense of structure is gone. Anyone who’s had to use a bibliography file with multiple LaTeX documents will agree: in reality, BibTeX’s portability is nonexistent and you end up reformatting your references manually for each document.

10. LaTeX is better than Microsoft Word

    I’m not going to claim Word—or OpenOffice.org Writer, for that matter—is better, but I think it’s seriously moronic to promote LaTeX just because it’s elitist and Free. By the way, that goes for any Open Source product. Anyway, in a real-world scenario, either solution is bound to give you trouble. What I will say, however, is that LaTeX is seriously fucked up and needs to die.