Comment Re:Compression could do this (Score 1) 106
Sounds to me this is more of an approach rather than a specific implementation. TFA talks about specific data types, such as credit card numbers and passwords. Reading between the lines, it seems like something that would be set up with input from a knowledgeable system administrator or hard-coded for a specific purpose; password manager is specifically mentioned.
So you write this program such that the data type information is not part of the encrypted data but explicitly provided as (for instance) a map that corresponds to valid password characters. After the algorithm is run on the encrypted data, you simply write the computed output to an integer value, and convert to ASCII using the aforementioned map (or, as you've mentioned, compression scheme). Similar methods are used to scale certain random number generating functions to any particular number range. This way, any binary dataset can be converted to text, but whether it's the real data or not is impossible to guess because it's by definition valid ASCII text. You're then free (as the user) to XOR the raw binary with whatever key your algorithm produces based on the master password typed by the user in order to produce the stored value.
Since I am not an expert in this field, the fact that it seems pretty trivial to me probably means either it's not new, and therefore not newsworthy, or there's some detail here that makes it special in some arcane way or niche application.