On Thu, Jan 20, 2011 at 12:44 PM,
<[email protected]> wrote:
> So, there's an interesting problem I ran into:
>
> Suppose you need to obfuscate symbols in a symbol file, and to be able
> to look them up later to analyze crash dumps.
>
> Suppose further that the symbol file format is kinda weird, and so you
> can't re-create the symbol file from scratch.
>
> IOW, the obfuscated symbols have to be changed in-place.
>
> Since many symbols may be less than 160 bits, hashes are right out,
> and those anyway would be limited since the input space is small
> enough that one could easily guess all symbols, and hash them -
> classic dictionary attack.  Hardening against guessing might help
> some, but to store any salt would only make matters worse.
>
> One could assign ordinal numbers to them, but for other, procedural
> reasons one cannot do this - namely, the obfuscated value should not
> change from release to release, and propogating the old ordinal
> values with each release is a pain.
>
> The simple answer seems to be encryption, which can operate without
> adding any metadata, but there's a catch; the symbol file format
> expects the values to be symbols - not arbitrary octets.

Sounds to me like the simplist solution is just a one-time pad[1]. It
won't increase the size, and from the sounds of your environment, you
can just keep the keys locally, and use them only when you do the
debugging. But perhaps I'm misunderstanding your question.

[...]


> --
> Effing the ineffable since 1997. | http://www.subspacefield.org/~travis/
> My emails do not usually have attachments; it's a digital signature
> that your mail program doesn't understand.
> If you are a spammer, please email [email protected] to get blacklisted.

-- 
[1] http://en.wikipedia.org/wiki/One-time_pad

Noon Silk

http://dnoondt.wordpress.com/  (Noon Silk) | http://www.mirios.com.au:8081 >

"Every morning when I wake up, I experience an exquisite joy — the joy
of being this signature."
_______________________________________________
cryptography mailing list
[email protected]
http://lists.randombit.net/mailman/listinfo/cryptography

Reply via email to