Re: Encryption newbie - Same length encrypted result
From: Luc The Perverse (sll_noSpamlicious_z_XXX_m_at_cc.usu.edu)
Date: 10/22/05
- Next message: David Eather: "Re: TDES crypto accelerator coprocessor 192bit"
- Previous message: Lapo Luchini: "Re: Snake oil cryptography"
- In reply to: TC: "Re: Encryption newbie - Same length encrypted result"
- Next in thread: TC: "Re: Encryption newbie - Same length encrypted result"
- Reply: TC: "Re: Encryption newbie - Same length encrypted result"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 22 Oct 2005 07:29:23 -0600
"TC" <aatcbbtccctc@yahoo.com> wrote in message
news:1129958381.934318.134840@f14g2000cwb.googlegroups.com...
> I'm a software guy with an amateur interest in encryption. One thing I
> can tell you is, you are very likely to make serious implementation
> mistakes, unless you really know what you are doing. It sounds to me,
> as if you just don't have enough knowledge of the subject, yet, to do
> it confidently. Crypto is unlike normal software problems. You can
> /think/ that it is working properly, whereas in fact, you have made a
> huge error (of some kind) that an experienced person could exploit in
> seconds flat.
>
> If you're storing millions of CC numbers, you'd better be /prettey damn
> sure/ that your implementation is up to professional crypto levels.
> IMHO, for something as important as CC numbers, you should hire an
> expert to do, or oversee, this part, for you.
>
> HTH,
> TC
It seems to me the limitation of output length being the same as input
length is some kind of a restriction that has been invented to try to allow
some amateur programming inadequacies to continue.
Your encrypted database, should not be the same as you unencrypted database,
with the exception that the numbers are just scramble
What is the threat you are trying to prevent? Someone stealing the server?
A computer user looking at the DB? Virus?
The problem with the setup is this. Any virus smart enough to penetrate
your system and export the credit card database, is going to be taylor-made
and smart enough to also grab your encryption key while it is in there ;)
-- "It's better to have rocked and lost than never to have rocked at all." -John Flansburgh
- Next message: David Eather: "Re: TDES crypto accelerator coprocessor 192bit"
- Previous message: Lapo Luchini: "Re: Snake oil cryptography"
- In reply to: TC: "Re: Encryption newbie - Same length encrypted result"
- Next in thread: TC: "Re: Encryption newbie - Same length encrypted result"
- Reply: TC: "Re: Encryption newbie - Same length encrypted result"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|