From: "Martin"
> For my tests I used the blob field (not varchar or anything else), but
> compared to your tests, I didn't use MySQL 5.0.6 (as it's still a beta)
but
> I used MySQL 4.1. Maybe that's part of the problem, although I'm not sure.
FWIW: I tested it on 4.0.23-standard, with the same re
ite strange, but so far I solved it by limiting the number
of characters by 256 in my application, but ofcourse that's not ideal...
Thanks,
Martin
-Oorspronkelijk bericht-
Van: Gleb Paharenko [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 15 juni 2005 14:31
Aan: mysql@lists.mysql.com
l> show create table test.a\G;
*** 1. row ***
Table: a
Create Table: CREATE TABLE `a` (
`a` blob
) ENGINE=MyISAM DEFAULT CHARSET=cp1251
COLLATE=cp1251_bi
mos wrote:
At 04:32 AM 6/15/2005, you wrote:
Hi,
I think of using AES Encryption for some time now, because it seems
to be
the most secure encryption method in MySQL at this moment
and table
encryption of some sort is not possible.
I really wish MySQL would support table wide
d which customer info is
being encrypted. And even with that said, laws are only good for those who
abide by them. :-)
-Cassj
-Original Message-
From: mos <[EMAIL PROTECTED]>
Sent: Jun 15, 2005 11:00 AM
To: mySQL list
Subject: Re: AES Encryption
At 04:32 AM 6/15/2005, you wrot
At 04:32 AM 6/15/2005, you wrote:
Hi,
I think of using AES Encryption for some time now, because it seems to be
the most secure encryption method in MySQL at this moment
and table
encryption of some sort is not possible.
I really wish MySQL would support table wide encryption because more
Hi,
I think of using AES Encryption for some time now, because it seems to be
the most secure encryption method in MySQL at this moment and table
encryption of some sort is not possible. In the documentation I read BLOB
fields are recommended for storage of data with AES_Encrypt, otherwise you
>
> Nevertheless you should be aware that the information is travelling
> unencrypted between the mysql client and server unless you're using SSL
> tunneling or similar techniques.
>
Sorry, since mysql 4.0, SSL is of course possible.
(I'm still using 3.23)
bh
pgp7GAhKO8td6.pgp
Description: PGP
On Friday 11 February 2005 11:52, love wrote:
> There is not some thing secret to be stored but the idea is to encrypt
> customer credit card information so it is not avilable to unauthorized
> users but key cannot be stored in source code as any body who can hack
> databases to pull out the inform
19:00, love wrote:
> Has any body implemented Aes encryption while storing critical data in
> mysql? I want to know the logic you are implementing to store your
> passwords to encrypt/decrypt data.
>
> Love Kumar
>
> Love Kumar wrote:
I think this question could not be an
;t have to store passwords in the source.
> What i think Aes encryption reduce the risk but does not make data 100%
> safe because of source code dependency.
Nobody gives you a 100% garanty.
love <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Aes Encryption requires
On Thursday 10 February 2005 19:00, love wrote:
> Has any body implemented Aes encryption while storing critical data in
> mysql? I want to know the logic you are implementing to store your
> passwords to encrypt/decrypt data.
>
> Love Kumar
>
> Love Kumar wrote:
I think th
Has any body implemented Aes encryption while storing critical data in
mysql? I want to know the logic you are implementing to store your
passwords to encrypt/decrypt data.
Love Kumar
Love Kumar wrote:
Hi,
Aes Encryption requires a password (key) to access data, now where do
we store this key
Hi,
Aes Encryption requires a password (key) to access data, now where do
we store this key? with the source code ? or in seperate database ?
because any body who has the access to souce code can view the critical
info or even if you store passwords in another database then it is not a
big
At 8:50 -0800 11/7/03, Herb Rubin wrote:
Paul,
TINYBLOB does seem to hold the value properly.
I can't use a TINYBLOB in a primary key. Is this not allowed?
The ALTER statement complains that I am using a column without a length
specified.
Specify a length, then. :-)
http://www.mysql.com/doc/en/I
At 10:49 -0800 11/7/03, William R. Mussatto wrote:
Paul DuBois said:
At 15:29 -0800 11/6/03, Herb Rubin wrote:
Paul,
I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT
NULL column.
The encrypted string seems to be equivalent to the NULL value even
though it visually looks like
Hi William,
- Original Message -
From: "William R. Mussatto"
Sent: Friday, November 07, 2003 12:49 PM
Subject: Re: aes encryption bug
> Paul DuBois said:
> >
> > Okay, I investigated this further and I believe I know the cause of
the
> > problem. The so
Hi Herb,
You should be able to specify 255 as the PRI KEY length... I think.
CREATE TABLE table (
col TINYBLOB NOT NULL,
PRIMARY KEY (col(255))
);
Hope that helps.
Matt
- Original Message -
From: "Herb Rubin"
Sent: Friday, November 07, 2003 10:50 AM
Subjec
Paul,
Is there a limitation on having a TINYBLOB as a primary key?
Herb
On Thu, 2003-11-06 at 19:24, Paul DuBois wrote:
> At 15:29 -0800 11/6/03, Herb Rubin wrote:
> >Paul,
> >
> >I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT NULL
> >column.
> >
> >The encrypted string see
Paul DuBois said:
> At 15:29 -0800 11/6/03, Herb Rubin wrote:
>>Paul,
>>
>>I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT
>> NULL column.
>>
>>The encrypted string seems to be equivalent to the NULL value even
>> though it visually looks like some kind of data.
>>
>>Herb
>
> Ok
Paul,
TINYBLOB does seem to hold the value properly.
I can't use a TINYBLOB in a primary key. Is this not allowed?
The ALTER statement complains that I am using a column without a length
specified.
Herb
On Thu, 2003-11-06 at 19:24, Paul DuBois wrote:
> At 15:29 -0800 11/6/03, Herb Rubin wrote:
At 15:29 -0800 11/6/03, Herb Rubin wrote:
Paul,
I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT NULL
column.
The encrypted string seems to be equivalent to the NULL value even though
it visually looks like some kind of data.
Herb
Okay, I investigated this further and I believe
Paul,
I did try VARCHAR(16) BINARY and it still failed to INSERT in a NOT NULL
column.
The encrypted string seems to be equivalent to the NULL value even though
it visually looks like some kind of data.
Herb
> Please reply to the list, not to me directly, so that others can
> follow this dis
Please reply to the list, not to me directly, so that others can
follow this discussion. Thanks.
At 14:54 -0800 11/6/03, Herb Rubin wrote:
Paul,
Yes, I get the same, now try and decrypt it, it will turn out to be NULL.
So, you cannot insert this into a NOT NULL column. It will reject it.
Your mes
At 14:03 -0800 11/6/03, Herb Rubin wrote:
Hi,
I am trying to use aes_encrypt and I get a NULL value with a specific
string:
INSERT INTO test SET
`id` = AES_ENCRYPT('551850040', '0bf251c9aaf007deaf1143ca1492b561');
my field 'id' is VARCHAR(16) NOT NULL
If I change the value or the encryption strin
Hi,
I am trying to use aes_encrypt and I get a NULL value with a specific
string:
INSERT INTO test SET
`id` = AES_ENCRYPT('551850040', '0bf251c9aaf007deaf1143ca1492b561');
my field 'id' is VARCHAR(16) NOT NULL
If I change the value or the encryption string it works. But this
combination turn
26 matches
Mail list logo
