Hi,
I agree with you. If we want to know, what Google has developed as encryption
feature, we will have to wait for your source code to be published.
In the meantime, you can find our concept for the encryption on our website:
http://bit.ly/1slJyuI
Feedback (negative and positive) from all of yo
Thank you for your feedback -
What we want to achieve is, that the encryption key is stored outside the
database. But you are right – if an attacker has access to the key and the
encrypted value, he is able to decrypt the content.
That means you have to store the key file in a place, where the
Hi,
by "interfaces" I was looking for the Maria DB place/ function / hook... where
you are enhancing the MariaDB Code.
This would help me to understand what you are trying to do.
Elmar
> Am 17.06.2014 um 07:02 schrieb Jonas Oreland :
>
> Hi again,
>
> > What is the type of license of your code
well, for a first version, i think it's nice :)
maybe more information about the key server should be nice
about key file... if the attacker know the file and contents, he/she could
decrypt the table/column?
2014-06-17 13:40 GMT-03:00 Elmar Eperiesi-Beck :
> Hi,
> I agree with you. If we want t
humm, now i'm thinking as a data warehouse
think about installing a server (server 1) in somewhere (maybe saara
desert) i connect the "server 1" to internet, and configure the server
uri to point to my central server (server central), maybe at moon
when the mysqld/mariadbd start, it will cont
2014-06-17 14:03 GMT-03:00 Jonas Oreland :
> Hi again,
>
> 1) we have not done column level encryption at all.
>
nice, did you check that have an idea at mariadb atlassian mdevs, maybe
this could help?
https://mariadb.atlassian.net/browse/MDEV-4912
>
> 2) keys are managed in a separate module (w
At startup the keys will be read once and kept in memory. Normaly you are not
going to encrypt 1000 tables, because you just encrypt the content that is
confidential. But yes- each key has to be in the memory. Or you use an external
encryption/key server that handels the encryption and the key-m
nice, check what i'm thinking about...
1)
i start mariadb without keys
i start my app
here i must check that all tables are 'unlocked' and read to use,
we will have a method to this? at mysql_connect i will check if keys
are loaded, maybe a SHOW STATUS like 'encryption_keys_loaded' = 1 or 0
2)
1) thats a good point, we will extend our coding to mysql_connect
2) yes, we want to do this with an INSERT statement - a bit more complex, but
yes….
We will update the concept paper and come back to you beginning of next week.
Am 20.06.2014 um 16:28 schrieb Roberto Spadim :
> nice, check wh
:) very nice
I will wait :)
Em sexta-feira, 20 de junho de 2014, Elmar Eperiesi-Beck <
el...@eperiesi-beck.de> escreveu:
> 1) thats a good point, we will extend our coding to mysql_connect
>
> 2) yes, we want to do this with an INSERT statement - a bit more complex,
> but yes….
>
> We will update
=] any news?
2014-06-20 13:47 GMT-03:00 Roberto Spadim :
> :) very nice
> I will wait :)
>
> Em sexta-feira, 20 de junho de 2014, Elmar Eperiesi-Beck <
> el...@eperiesi-beck.de> escreveu:
>
> 1) thats a good point, we will extend our coding to mysql_connect
>>
>> 2) yes, we want to do this with a
Of course - we are working with high pressure on this topic.
Unfortunately, we had more problems than expected to get the code up and
running - BUT we made it!
Currently we have managed to implement a primitive xor encryption on the page
level. We have solved some issues with checksums mainly by
Very nice :) working only with innodb or any engine?
Em quinta-feira, 18 de setembro de 2014, Elmar Eperiesi-Beck <
el...@eperiesi-beck.de> escreveu:
> Of course - we are working with high pressure on this topic.
> Unfortunately, we had more problems than expected to get the code up and
> running
We work with XtraDB in the first run and will extend it to others later on.
Am 19.09.2014 um 15:04 schrieb Roberto Spadim :
> Very nice :) working only with innodb or any engine?
>
> Em quinta-feira, 18 de setembro de 2014, Elmar Eperiesi-Beck
> escreveu:
> Of course - we are working with high
very nice, good work :)
2014-09-19 10:17 GMT-03:00 Elmar Eperiesi-Beck :
> We work with XtraDB in the first run and will extend it to others later on.
>
> Am 19.09.2014 um 15:04 schrieb Roberto Spadim :
>
> Very nice :) working only with innodb or any engine?
>
> Em quinta-feira, 18 de setembro d
Hi there,
our implementation is in production :)
but has not yet been open sourced due to other tasks consuming time :(
it has solved all problems enumerated above...and I think it would be much
better to have one crypt implementation than two!
i'll ask the pavel that does the open-sourcing for
Very good news
Em terça-feira, 23 de setembro de 2014, Jonas Oreland
escreveu:
> Hi there,
>
> our implementation is in production :)
> but has not yet been open sourced due to other tasks consuming time :(
>
> it has solved all problems enumerated above...and I think it would be much
> better
Hi there,
we just managed to get the problems solved much faster as assumed. Thanks to
the community!
Perhaps it makes sense to have just one crypto implementation to do not confuse
users.
You can find our Source Code under: https://github.com/eperi-GmbH/server . As
fork of the actual 10.1 Code
=] nice, i will try soon
2014-09-23 15:50 GMT-03:00 Elmar Eperiesi-Beck :
> Hi there,
> we just managed to get the problems solved much faster as assumed. Thanks
> to the community!
>
> Perhaps it makes sense to have just one crypto implementation to do not
> confuse users.
> You can find our Sou
19 matches
Mail list logo
