http://qs321.pair.com?node_id=834122


in reply to Re: Creating a rainbow table for a ten-digit number: Advice?
in thread Creating a rainbow table for a ten-digit number: Advice?

Regarding the first observation, the real threat is the appearance of not taking the collection and retention of the data seriously.

Regarding the second observation, I would love to know how to incorporate public key crypto into a database front-end - specifically one made in MS Access. That would be the preferred option to a hash+rainbow table by a long chalk.

  • Comment on Re^2: Creating a rainbow table for a ten-digit number: Advice?

Replies are listed 'Best First'.
Re^3: Creating a rainbow table for a ten-digit number: Advice?
by rowdog (Curate) on Apr 11, 2010 at 20:34 UTC

    If all you want is the appearance of security, why not use XOR? Better yet, use something like Crypt::Rijndael so you can claim to be using the Advanced Encryption Standard.

    As far as the database goes, you can encrypt your data (with padding, Xilman++) before you do your INSERT and decrypt after you do your SELECT.

      With respect, XOR only provides the appearance of security to the naive or ignorant. Ethics committees are, for the most part, neither.

        Indeed, I was being a bit silly about using XOR, which is why I included the bit about AES.