This is already reality. So called "red pills" allow malware to find out if its are running in an emulator or virtual machine.

Here's a paper that describes automatically generating such red pills:

"A fistful of red-pills: how to automatically generate procedures to detect cpu emulators" by R. Paleari, L. Martignoni, G. F. Roglia, and D. Bruschi
https://www.usenix.org/legacy/event/woot09/tech/full_papers/paleari.pdf

The authors found more than 23k red-pills to detect QEMU and/or BOCHS.

Let's look at what page 131 of the GAO report says about Table 8 (http://www.gao.gov/new.items/d11696.pdf).

First of all, these are loans, not bailouts.

Second, for at least half of the amount (the PDFC loans), the number is highly inflated: "For example, an overnight PDCF loan of $10 billion that was renewed daily at the same level for 30 business days would result in an aggregate amount borrowed of $300 billion although the institution, in effect, borrowed only $10 billion over 30 days."

A December 2010 paper, "Uncovering Spoken Phrases in Encrypted Voice over IP Conversations", takes a similar approach.

The article was published in ACM Transactions on Information and System Security, PDF version.

The paper details a gap in the security of VBR compressed encrypted VoIP streams. The authors had earlier found that it is possible to determine the language that is spoken on such a VoIP call, based on packet lengths. Now they have expanded their research and show that itâ(TM)s possible to detect entire spoken phrases during a VoIP call. On average, their method achieved recall of 50% and precision of 51% for a wide variety of phrases spoken by a diverse collection of speakers (some phrases are easier to detect than others; the recall various from 0% to 98%, depending on length of the phrase and the speaker). In other words: they can detect fairly well if a certain phrase is being used in a conversation, even though the VoIP conversation is encrypted.

You know that you can point your MS Access client to any supported back-end right? Just create an ODBC connection on your Windows machine to your PostgreSQL server and you can use Access with pretty much all the features that work for the Microsoft JetEngine (PostgreSQL has ODBC drivers here; http://www.postgresql.org/ftp/odbc/versions/)

Earlier this year we converted a huge Access application from MSSQL to PostgreSQL and the technical conversion, using ODBC to PostgreSQL instead of connecting to MSSQL, was a piece of cake.