Hi MySQL Community,
Greetings !
I have a query regarding encryption-at-rest feature in MySQL Community Edition -
What i understand is that Encryption-at-rest is supported from MySQL-5.7.11
community edition and only on file-per-table basis which means encryption at
table-level can be implement
On Sun, Mar 21, 2010 at 9:49 PM, mos wrote:
> At 03:21 PM 3/21/2010, John Daisley wrote:
>
>> Mike,
>>
>> Encrypted filesystems can seriously impact performance of MySQL.
>>
>> Its an entirely different issue to MySQL encryption but one would hope
>&g
At 03:21 PM 3/21/2010, John Daisley wrote:
Mike,
Encrypted filesystems can seriously impact performance of MySQL.
Its an entirely different issue to MySQL encryption but one would hope
that, if you are going to go to all the trouble of using two part keys and
the strongest encryption
Mike,
Encrypted filesystems can seriously impact performance of MySQL.
Its an entirely different issue to MySQL encryption but one would hope that, if
you are going to go to all the trouble of using two part keys and the strongest
encryption available in your database, you would also take as
to a few people in
your company. Never trust the internet service provider to be your only
means to protect your data or your drives.
Mike
-Original Message-
From: Jim
Sent: Friday, March 19, 2010 4:22 PM
To: John Daisley ; mysql@lists.mysql.com
Subject: Re: MySQL Encryption
T
-Original Message-
From: Jim
Sent: Friday, March 19, 2010 4:22 PM
To: John Daisley ; mysql@lists.mysql.com
Subject: Re: MySQL Encryption
Thanks for the reply, John.
What you are describing seems to be the approach I've seen on the few
places I've seen this topic discusse
Hi Neil.
Information (in most cases a string < 100 chars, but that's probably not
important) that actually needs to be decrypted, so a hash won't do.
Jim
On 3/20/2010 5:09 PM, Tompkins Neil wrote:
Hi
What sort of information are you looking to encrypt ? If it is for user
passwords I'd reco
Hi
What sort of information are you looking to encrypt ? If it is for user
passwords I'd recommend SHA256 which is one way encryption. Or are you
looking to encrypt more sensitive information like card holder data ?
Regards
Neil
On Fri, Mar 19, 2010 at 4:22 PM, Jim wrote:
> Thanks for the re
Thanks for the reply, John.
What you are describing seems to be the approach I've seen on the few
places I've seen this topic discussed.
I've been considering something along those lines, essentially a two
part key.
Part one of the key is made from some data that is in the record I want
to
Jim,
I tend to derive a key based on a separate character string and the contents
of the data in the same or a related table. This means each row has a unique
encryption key and you never have to have the whole key stored somewhere
(you don't even know it :p ). Biggest advantage to this is should
In terms of encryption functions AES_DECRYPT and AES_ENCRYPT, can anyone
point to any good links or offer any suggestions in terms of best
practices on storage of the associated symmetric key? I've found very
little information on this when searching.
Does MySQL offer any asymmetric encryption
uk]
> Sent: Tuesday, August 25, 2009 2:08 AM
> To: Mike Scully
> Cc: mysql@lists.mysql.com
> Subject: Re: MySQL Encryption - Third-party tools
>
> On Mon, 24 Aug 2009, Mike Scully wrote:
>
> > Hello, all.
> > =20
> > Can any of you share with me the names o
On Mon, 24 Aug 2009, Mike Scully wrote:
> Hello, all.
> =20
> Can any of you share with me the names of any third-party tools or
> appliances that you are using to encrypt your MySQL databases? I am
> doing a search and would like to narrow down the initial search list.
> Thanks!
> =20
> Mike
I
Hello, all.
Can any of you share with me the names of any third-party tools or
appliances that you are using to encrypt your MySQL databases? I am
doing a search and would like to narrow down the initial search list.
Thanks!
Mike
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am interested in feedback, advice from anyone who has changed the
AES_BLOCK_SIZE (default 16 bytes, for 128 bit) to 32 bytes, or 256 bit
encryption as mentioned on:
http://dev.mysql.com/doc/mysql/en/Encryption_functions.html
I am only attempting to p
On Fri, Nov 22, 2002 at 10:32:59AM +0100, Roger Baklund wrote:
> > How would MySQL react to having some of its data files stored on
> > encrypted loop-back devices that aren't available all the time, but are
> > always available when a certain user logs in?
>
> I'm sorry, I don't understand the qu
* Fraser Stuart
> Here are my two main security issues.
>
> 1) (valid) user does a sudo to root and runs "strings .MYD" - out
> drops all the sensitive text
> 2) (clever) user gets hold of the application user/password for
> MySQL (it's
> in the app config somewhere) - they run "mysql --user=foo --
-Original Message-
| From: Roger Baklund [mailto:[EMAIL PROTECTED]]
| Sent: Tuesday, 19 November 2002 1:15 AM
| To: [EMAIL PROTECTED]
| Cc: Alexandre Aguiar; Fraser Stuart
| Subject: Re: Mysql & Encryption
|
|
| * Alexandre Aguiar
| > On 14 Nov 2002 Fraser Stuart shaped the elec
: Mike Hillyer [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 18, 2002 2:24 PM
> To: Muir, Michael (OTS-EDH); 'Andy Eastham'; Mysql@Lists. Mysql. Com
> Subject: RE: Mysql & Encryption
>
>
> As far as I know you have to have a shell account to use ssh
> tunnel
Mysql. Com
Subject: RE: Mysql & Encryption
PuTTY is a nice freeware SSH client.
http://www.chiark.greenend.org.uk/~sgtatham/putty/
-mike
> -Original Message-
> From: Andy Eastham [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 18, 2002 8:39 AM
> To: Mysql@L
PuTTY is a nice freeware SSH client.
http://www.chiark.greenend.org.uk/~sgtatham/putty/
-mike
> -Original Message-
> From: Andy Eastham [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 18, 2002 8:39 AM
> To: Mysql@Lists. Mysql. Com
> Subject: RE: Mys
r
> > > On 14 Nov 2002 Fraser Stuart shaped the electrons to write something
> > > about [Mysql & Encryption]
> > >
> > > > We are about to embark on a project that requires data encryption -
> > > > mainly to stop sensitive information bei
At 08:15 AM 11/18/2002, you wrote:
* Alexandre Aguiar
> On 14 Nov 2002 Fraser Stuart shaped the electrons to write something
> about [Mysql & Encryption]
>
> > We are about to embark on a project that requires data encryption -
> > mainly to stop sensitive information
Sent: 18 November 2002 13:54
> To: Alexandre Aguiar; Fraser Stuart
> Cc: [EMAIL PROTECTED]
> Subject: RE: Mysql & Encryption
>
>
> A windows versionof Stunnel is available from the stunnel website
> (www.stunnel.org), I would reccomend using it for your needs.
>
> Mike
ComIT Solutions Inc.
www.comit.ca
- Original Message -
From: "Alexandre Aguiar" <[EMAIL PROTECTED]>
To: "Fraser Stuart" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 18, 2002 8:09 AM
Subject: Re: Mysql & Encryption
On 14 Nov 2
* Alexandre Aguiar
> On 14 Nov 2002 Fraser Stuart shaped the electrons to write something
> about [Mysql & Encryption]
>
> > We are about to embark on a project that requires data encryption -
> > mainly to stop sensitive information being viewed accidentally (ie
>
&
PROTECTED]
Subject: Re: Mysql & Encryption
On 14 Nov 2002 Fraser Stuart shaped the electrons to write something
about [Mysql & Encryption]
> We are about to embark on a project that requires data encryption -
> mainly to stop sensitive information being viewed accidentally (ie
Isn´t
On 14 Nov 2002 Fraser Stuart shaped the electrons to write something
about [Mysql & Encryption]
> We are about to embark on a project that requires data encryption -
> mainly to stop sensitive information being viewed accidentally (ie
Isn´t it possible to tunnel MySQL connections t
Roger Baklund wrote:
Wouldn't you be better of using GRANT? If you encrypt the content of the
database, any searching must be done on the encrypted value, and sorting
would be difficult...
How would MySQL react to having some of its data files stored on
encrypted loop-back devices that aren'
* Fraser Stuart
> We are about to embark on a project that requires data encryption - mainly
> to stop sensitive information being viewed accidentally (ie viewing tables
> directly through odbc connections or standard mysql clients). The server
> (solaris) will not be publicly accessible.
Wouldn't
Fraser Stuart wrote:
From this I'm leaning towards DES encryption - only because I can store the
key on the server.
Don't use DES for any secure information. If by "secure" you mean "I
don't care if they see it, but I'd prefer if they didn't", the go ahead.
If by "secure" you mean "No way!
Hi All,
We are about to embark on a project that requires data encryption - mainly
to stop sensitive information being viewed accidentally (ie viewing tables
directly through odbc connections or standard mysql clients). The server
(solaris) will not be publicly accessible. Mysql has a variety of
e
32 matches
Mail list logo
