Hi,
how do i use encryption key on sqlite that run on the cubesql server???
on xojo, i use “app.datDataS.EncryptionKey=gEncryptionKey” for sqlite for single user.
i move the data file to the cubesql , i have a line like this “app.datDataM.Encryption=1” but don’t know what to do next.
Encryption of the SQLite databases are managed by cubeSQL at the server level. You only need to make sure you are enabling AES encryption for your data traffic between your Xojo app and cubeSQL server.
how do i enabling the AES encryption?
got a email from marco bambini
[b]from the Admin manual:
"If the database that you uploaded is encrypted and the server does not know its encryption key, then it cannot serve it. For that reason, it appears in gray in the Databases panel. You need to set its encryption key (either using the Admin application or via the proper custom command).
In the Admin application, select the database in the list and choose Server ? Set Database Key. A dialog will appear in which you can enter the databases encryption key."[/b]
I understand how to encrypt a SQLite file that is overseen by cubeSQLServer, using the the cubeSQLServer Admin app. But how do I enable AES encryption for the data traffic between my Xojo app and the cubeSQL server?
If you look at Xojo Plugin.pdf included with the CubeSQL download you will find a little information.
try:
db.Encryption = CubeSQLPlugin.kAES256I think the options are:
kAESNONE (Integer Constant)
kAES128 (Integer Constant)
kAES192 (Integer Constant)
kAES256 (Integer Constant)
Sounds promising, Johnny. Thanks.
I also notice that I can’t encrypt an unencrypted file with the cubeSQL Admin app. I must do that before uploading it. SQLiteManager lets me do that with AES128, which it says is the only one of the options it offers that will work with both Xojo cubeSQLServer.
Look at page 64 of the ‘Commands Reference.pdf’ file. There are commands you can execute from the CubeSQL Admin console to Encrypt/Decrypt a database on the server. I would try these commands on a non-production database for testing.
ENCRYPT DATABASE myDB WITH KEY abc;[quote=342167:@Johnny Harris]Look at page 64 of the ‘Commands Reference.pdf’ file. There are commands you can execute from the CubeSQL Admin console to Encrypt/Decrypt a database on the server. I would try these commands on a non-production database for testing.
ENCRYPT DATABASE myDB WITH KEY abc;
[/quote]
That works, Johnny. Thanks.
More testing shows this method of encrypting an existing database fails to work most of the time for me. I find that I have to download the database, encrypt it with SQLite Manager, and then upload it again. Not sure why it worked for me once, but never again.
Hmmm… kind of strange. I tried to set the encryption key for a database with the extension .db (chinook.db) and it failed every time. I renamed the extension to .sqlite (chinook.sqlite) and it works just fine.
Could this possibly be the issue you’re having?
I used the .sqlite extension.
Most of the time I was stopped out with a message saying the database is in use (the client hitting it was just the cubeSQL Admin app). Other times, when it looked like the attempt to encrypt the file worked, I later found I couldn’t open it with the password I used to encrypt it.
Downloading, encrypting, and then uploading works, of course.
I think there are several different methods that can be used to encrypt/decrypt an SQLite database. Others on the forum would know more about this than I do. The method you’re using to decrypt may not be compatible with the method used to encrypt.
According to the CubeSQL documentation:
ENCRYPT DATABASE encrypts a non encrypted (clear) database using AES128 OFB algorithm.You could always email Marco about the issues you’re having.
I emailed Marco this morning.
[quote=342153:@Johnny Harris]If you look at Xojo Plugin.pdf included with the CubeSQL download you will find a little information.
try:
db.Encryption = CubeSQLPlugin.kAES256I think the options are:
kAESNONE (Integer Constant)
kAES128 (Integer Constant)
kAES192 (Integer Constant)
kAES256 (Integer Constant)[/quote]
Turns out that we don’t need to add anything at all to existing Xojo code, assuming your code works fine with an existing cubeSQLServer-hosted unencrypted file. Just encrypt the existing cubeSQLServer-hosted file, and tell cubeSQLServer what the password is for that file, and you’re done. As long as you encrypt the file with SQLite/SEE encryption, you’re good to go. You can do that with SQLiteManager, from the author of cubeSQLServer, or Xojo itself.