On 12 August 2010 02:07, Josh Kehn 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 securit
On Wed, 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
On 12 August 2010 09:48, Adam Richardson wrote:
> On Wed, Aug 11, 2010 at 6:50 PM, tedd 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
> 128 bit output MD5 produces. A
At 5:30 PM -0700 8/11/10, Daevid Vincent wrote:
> -Original Message-
2. Were told it was a social security number
(i.e., in the form of 123-45-6789).
Stop.
Why are you even contemplating storing SS# ??
Daevid et al:
Why? Because my client wants to store SS numbers on their on
On Thu, 2010-08-12 at 09:45 -0400, tedd wrote:
> At 5:30 PM -0700 8/11/10, Daevid Vincent wrote:
> > > -Original Message-
> >> 2. Were told it was a social security number
> >> (i.e., in the form of 123-45-6789).
> >
> >Stop.
> >
> >Why are you even contemplating storing SS# ??
>
>
On 12 August 2010 14:45, tedd wrote:
> At 5:30 PM -0700 8/11/10, Daevid Vincent wrote:
>>
>> > -Original Message-
>>>
>>> 2. Were told it was a social security number
>>> (i.e., in the form of 123-45-6789).
>>
>> Stop.
>>
>> Why are you even contemplating storing SS# ??
Why hold 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 dash
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
At 2:59 PM +0100 8/12/10, Richard Quadling wrote:
On 12 August 2010 14:45, tedd wrote:
At 5:30 PM -0700 8/11/10, Daevid Vincent wrote:
> -Original Message-
2. Were told it was a social security number
(i.e., in the form of 123-45-6789).
Stop.
Why are you even contempla
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 schem
At 2:51 PM +0100 8/12/10, Ashley Sheridan wrote:
If you are storing the data in a DB, then I'd consider using
different levels of access to that via different DB users, which
should offer an extra layer of security in protecting the data.
Of course, the routines I'm writing provide several lev
I'm trying to draw text at a 90 degree angle, reading from bottom to top. For
some reason, all of the letters are aligning to the top (i.e. the left side) of
the text. It looks really odd! Has anyone else experienced this before?
Thanks!
Floyd
--
PHP General Mailing List (http://www.php.net/
On Thu, 2010-08-12 at 10:40 -0400, Floyd Resler wrote:
> I'm trying to draw text at a 90 degree angle, reading from bottom to top.
> For some reason, all of the letters are aligning to the top (i.e. the left
> side) of the text. It looks really odd! Has anyone else experienced this
> before?
On Aug 12, 2010, at 10:42 AM, Ashley Sheridan wrote:
> On Thu, 2010-08-12 at 10:40 -0400, Floyd Resler wrote:
>
>> I'm trying to draw text at a 90 degree angle, reading from bottom to top.
>> For some reason, all of the letters are aligning to the top (i.e. the left
>> side) of the text. It
On Thu, Aug 12, 2010 at 10:30 AM, tedd wrote:
> At 2:51 PM +0100 8/12/10, Ashley Sheridan wrote:
>>
>> If you are storing the data in a DB, then I'd consider using different
>> levels of access to that via different DB users, which should offer an extra
>> layer of security in protecting the data.
On Thu, Aug 12, 2010 at 10:00 AM, tedd 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 with a pair
At 10:56 AM -0400 8/12/10, Bastien Koert wrote:
However, the data must be stored in an encrypted format and it must be
transmitted via SSL. We do it that way (taking both a hash for
searching for the ssn and the encrypted form) and haven't had any
issues as yet.
The data will be encrypted and o
On Aug 12, 2010, at 11:32 AM, tedd wrote:
> At 10:56 AM -0400 8/12/10, Bastien Koert wrote:
>> However, the data must be stored in an encrypted format and it must be
>> transmitted via SSL. We do it that way (taking both a hash for
>> searching for the ssn and the encrypted form) and haven't had a
On Thu, 2010-08-12 at 10:40 -0400, Floyd Resler wrote:
I'm trying to draw text at a 90 degree angle, reading from bottom
to top. For some reason, all of the letters are aligning to the
top (i.e. the left side) of the text. It looks really odd! Has
anyone else experienced this before?
T
At 11:39 AM -0400 8/12/10, Joshua Kehn wrote:
Would one option be to have a table of unencrypted SSN's with an
encrypted id for the user. So you could search the SSN's and then
connect them, however if the table was dumped you wouldn't be able
to link it directly to the person (as it would just
On Aug 12, 2010, at 11:55 AM, tedd wrote:
> At 11:39 AM -0400 8/12/10, Joshua Kehn wrote:
>> Would one option be to have a table of unencrypted SSN's with an encrypted
>> id for the user. So you could search the SSN's and then connect them,
>> however if the table was dumped you wouldn't be able
On Aug 12, 2010, at 11:50 AM, tedd wrote:
>> On Thu, 2010-08-12 at 10:40 -0400, Floyd Resler wrote:
>>
>>> I'm trying to draw text at a 90 degree angle, reading from bottom to top.
>>> For some reason, all of the letters are aligning to the top (i.e. the left
>>> side) of the text. It looks
On Thu, 2010-08-12 at 12:14 -0400, Floyd Resler wrote:
> On Aug 12, 2010, at 11:50 AM, tedd wrote:
>
> >> On Thu, 2010-08-12 at 10:40 -0400, Floyd Resler wrote:
> >>
> >>> I'm trying to draw text at a 90 degree angle, reading from bottom to top.
> >>> For some reason, all of the letters are al
On Aug 12, 2010, at 12:17 PM, Ashley Sheridan wrote:
> On Thu, 2010-08-12 at 12:14 -0400, Floyd Resler wrote:
>
>> On Aug 12, 2010, at 11:50 AM, tedd wrote:
>>
On Thu, 2010-08-12 at 10:40 -0400, Floyd Resler wrote:
> I'm trying to draw text at a 90 degree angle, reading from bott
On Thu, Aug 12, 2010 at 11:32 AM, tedd wrote:
> At 10:56 AM -0400 8/12/10, Bastien Koert wrote:
>>
>> However, the data must be stored in an encrypted format and it must be
>> transmitted via SSL. We do it that way (taking both a hash for
>> searching for the ssn and the encrypted form) and haven'
Well, whatever the problem is it is definitely related only to my
system. I tried your code and had the same results
(https://adexfulfillment.com/adex/tests/test.php). I tried
different fonts as well. The fonts I'm using were exported from
FontBook on my Mac. I wonder if that might have s
> -Original Message-
> From: tedd [mailto:t...@sperling.com]
> Sent: Thursday, August 12, 2010 7:30 AM
> To: a...@ashleysheridan.co.uk
> Cc: php-general@lists.php.net
> Subject: RE: [PHP] Storing Social Security Number WAS:
> Encryption/Decryption Question
>
> At 2:51 PM +0100 8/12/10, Ash
> -Original Message-
> From: tedd [mailto:t...@sperling.com]
> Sent: Thursday, August 12, 2010 8:32 AM
> To: Bastien Koert
> Cc: php-general@lists.php.net
> Subject: Re: [PHP] Storing Social Security Number WAS:
> Encryption/Decryption Question
>
> For searching standard fields, it's
I have an idea.
First create a master key that the ssn ar encrypted with.
Store the master key encrypted with a key accessible by users (mksk).
Every user stores the key (mksk) to decrypt the (master key) and the mksk
should be ecrypted with there password as key.
And when a new user is created t
29 matches
Mail list logo
