On 12 August 2010 02:07, Josh Kehn josh.k...@gmail.com wrote:
On Aug 11, 2010, at 6:50 PM, tedd wrote:
Hi gang:
Okay, a question to the Encryption/Decryption gurus out there.
If you were given:
1. This encrypted string:
p3IVhDBT26i+p4vd7J4fAw==
2. Were told it was a social security
On Wed, Aug 11, 2010 at 6:50 PM, tedd t...@sperling.com wrote:
Hi gang:
Okay, a question to the Encryption/Decryption gurus out there.
If you were given:
1. This encrypted string:
p3IVhDBT26i+p4vd7J4fAw==
2. Were told it was a social security number (i.e., in the form of
123-45-6789).
On 12 August 2010 09:48, Adam Richardson simples...@gmail.com wrote:
On Wed, Aug 11, 2010 at 6:50 PM, tedd t...@sperling.com wrote:
*snip*
1. MD5 - Use of this old algorithm to produce your keys limits your key
space due to collisions AND the fact that 3DES accepts keys longer than the
At 8:09 PM -0400 8/11/10, Bastien Koert wrote:
From my experience, I'd have to say that it would be a real tough go
to crack that. If there was a weak point in the scheme is that your
end result pattern ( the ssn ) is defined with a pair of constants,
the hyphens. In our scheme we remove the
At 3:48 AM -0400 8/12/10, Adam Richardson wrote:
-- snip excellent points --
Of note, SS#'s are a special piece of data, not only because of their power,
but because of their lifetime (normally as long as the individual lives.)
This is very different from a credit card which gets updated every
From: tedd
At 8:09 PM -0400 8/11/10, Bastien Koert wrote:
From my experience, I'd have to say that it would be a real tough go
to crack that. If there was a weak point in the scheme is that your
end result pattern ( the ssn ) is defined with a pair of constants,
the hyphens. In our scheme we
On Thu, Aug 12, 2010 at 10:00 AM, tedd t...@sperling.com wrote:
At 8:09 PM -0400 8/11/10, Bastien Koert wrote:
From my experience, I'd have to say that it would be a real tough go
to crack that. If there was a weak point in the scheme is that your
end result pattern ( the ssn ) is defined
On Aug 11, 2010, at 6:50 PM, tedd wrote:
Hi gang:
Okay, a question to the Encryption/Decryption gurus out there.
If you were given:
1. This encrypted string:
p3IVhDBT26i+p4vd7J4fAw==
2. Were told it was a social security number (i.e., in the form of
123-45-6789).
3. And it
From my experience, I'd have to say that it would be a real tough go
to crack that. If there was a weak point in the scheme is that your
end result pattern ( the ssn ) is defined with a pair of constants,
the hyphens. In our scheme we remove the dashes and just provide a
mask for display. We also
9 matches
Mail list logo
