Column Encryption in Informix - SQL -26040: Encrypt VP initialization failed - encryption

We are using Informix as DB for our application.
We have a new requirement to encrypt one column (ID) alone. The encryption should not be external and should be in DB itself.
IBM explains the encryption procedure in http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.sqls.doc/sqls1024.htm
The steps are as follows:
SET ENCRYPTION PASSWORD 'credit card number is encrypted'
WITH HINT 'Why is this difficult to read?';
INSERT INTO customer VALUES ('Alice',
encrypt_tdes('1234567890123456'));
INSERT INTO customer VALUES ('Bob',
encrypt_tdes('2345678901234567'));
SELECT id, DECRYPT_CHAR(creditcard,
'credit card number is encrypted') FROM customer;
But when I follow the same step, DB is throwing the error in the first step itself (at set encryption password).
"SQL -26040: Encrypt VP initialization failed."
I am not sure what is the actual issue, as I couldn't find a satisfying solution.
Could someone help us to solve this?

The issue was with Encrypt VP server not present for Informix. We have installed Encrypt VP server and then the encryption was successful.
Thanks,

Related

Why is my managed instance database encryption is not being disabled?

I am trying to disable encryption on a database which is hosted inside Azure managed instance. I am not able to disable the encryption for it. Any help would be highly appreciated.
I have tried this alter database query:
ALTER DATABASE "DATABASE-NAME" SET ENCRYPTION OFF
I had checked encryption on each database as:
SELECT name, is encrypted
FROM sys.databases;
ALTER DATABASE "DATABASE-NAME" SET ENCRYPTION OFF
The query I used to alter the database turns out run successfully but the encryption is not disabled.
It may take some time to complete. On databases of less than 100 GB you may find it takes 20-25 minutes to complete.
You can monitor de progress using below query:
SELECT DB.NAME, DEK.ENCRYPTION_STATE, DEK.PERCENT_COMPLETE
FROM SYS.DM_DATABASE_ENCRYPTION_KEYS AS DEK
FULL JOIN SYS.DATABASES AS DB
ON DB.DATABASE_ID = DEK.DATABASE_ID
ORDER BY DB.NAME

How encrypt SQLite database with FireDAC?

I'm create SQLite databse with DB Browser for SQLite (non encrypted) and open with FireDAC in delphi.(Can retrive data Eg. Select * from abc).
How encrypt this SQLite database with FireDAC? When enter username, password and encrypt get message "Cipher DB is not encrypdet"
Note:
When create SQLite database from Delphi FireDac I can use encryption!
To encrypt a database, use a TFDSQLiteSecurity Component. You'll also need a TFDSQLitePhysSQLiteDriverLink component to go along with it.
If a database is unencrypted, then its password is ''. So use '' as the OldPassword and create the new password in that case. Passwords are formatted as algorithm:PassPhrase. See documentation on the choices, I use aes-256. Also, the database needs to be closed when you do this.
...
//Change password
FDSQLiteSecurity1.Password := OldPassword;
FDSQLiteSecurity1.ToPassword := NewPassword; // example: 'aes-256:mypassword123'
FDSQLiteSecurity1.ChangePassword;
...
//Remove Password
FDSQLiteSecurity1.Password := OldPassword;
FDSQLiteSecurity1.ToPassword := '';
FDSQLiteSecurity1.RemovePassword;
...
From the Documentation
SQLite Encrypted Database
Approach
One of the distinctive SQLite
features is the high-speed strong database encryption. It allows you
to make database file content confidential and enforce integrity
control on the database file. The encrypted database format is not
compatible with other similar SQLite encryption extensions. This means
that you cannot use an encrypted database, encrypted with non-FireDAC
libraries. If you need to do this, then you have to decrypt a database
with an original tool and encrypt it with FireDAC.
Recent Delphi versions come with an example project for working with encryption on Sqlite databases, see this documentation. I have not used this myself, btw.
It includes this section
Encrypt DB
Encrypt: Encrypts the database according to the Encryption mode and the password provided.
The sampe uses TFDSQLiteSecurity.SetPassword to encrypt the database with the password provided.
The database password is the combination of <encryption algorythm>:<password>.
I have faced several challenges when first time tried to encrypt SQLite database for use with Embarcadero FireDAC. Also all information is published by Embarcadero question pops up again and again on different forums. My case was solved based on community support, but when time has permitted simple Delphi application was assembled and available on Sourceforge. Hope it will make encryption/decryption slightly easier particularly for the newbie
https://sourceforge.net/projects/sqlite-sequrity-for-delphi/

SQL Server 2016 TDE: Database encryption scan for 'DB_name' was aborted

When I executed Alter database <DB_Name> set encryption on;, the error message such the subject was appeared in Error.log, and encryption_state has been kept 2 (Encryption in progress).
The DB has only few records because it is just test purpose.
Before execution encryption, DMK, Server certificate, DEK was created with no error.
Besides, I executed Select * from msdb.dbo.suspect_pages; to check if some data is corrupted, but no data was corrupted.
How should I do to complete database encryption?
I appreciate if you give some hint.
Thanks,
[Self solved]
1. Delete all certificate and master key
2. Restart the instans
3. Create Key set newly.
4. Encryption again
...then succeeded to encryption.
[TIPS] When TDE is enabled, compatibility should be '130'. Otherwise, encryption scan will be aborted...

Verifying MariaDB 10.1 encryption

I have set up table-level InnoDB database encryption on MariaDB.
I'd like to know if there is any way to confirm that the data is truly encrypted. I've tried searching /var/lib/mysql/ibdata1 for sample data in the tables, but I don't know if that's a reliable test or not.
I posted this question on mariadb.com, and the suggestion there was to perfom a grep for some known data.
A DBA at Rackspace suggested using the strings command instead, to better handle the binary data, for example:
strings /var/lib/mysql/sample_table/user.ibd | grep "knownuser"
This approach returns no results on an encrypted table and does return results on an unencrypted table (assuming both have "knownuser" loaded into them).
You can query information_schema.innodb_tablespaces_encryption. When innodb tablespace is encrypted it is present in the table.
SELECT * FROM information_schema.INNODB_TABLESPACES_ENCRYPTION
WHERE NAME LIKE 'db_encrypt%';
source
My advice for testing is to copy the full dataset to another node without the encryption keys in place and try to start MySQL and query the encrypted tables. I'm making an (big) assumption that they will not be readable since the valid encryption keys are missing.
To parse the files on disk as they lay may prove difficult unless you have a special tool to do this. Maybe something like Jeremy Cole's innodb_ruby would be another litmus test https://github.com/jeremycole/innodb_ruby.
[probably don't works if you change the key which encrypts the log.]
Stop the database server.
BACKUP the keyfile
Change a key in the keyfile. (don't delte - it still has to remain a valid key otherwiese the server can't restart)
Start MariaDB again.
Try to read the table (e.g. with phpMyAdmin).
If encrypted correctly there is an answer: "The table is encrypted..." when trying to read the encryted table.
Stop Maria
Restore the backup
Restart Maria

How to encrypt data in sql server 2012 or sql server 2008 r2?

I want to encrypt the username and password both in sql tables . is it useful(if any method for data encryption in Sql Server) or i should apply for the Encryption and Decryption keys from front end.
till now i m using encryption and decryption from the front end using HttpUtility and base 64 method .
Column-level encryption (aka cell-level encryption) was introduced in SQL Server 2005 and is available in all editions of SQL Server, including the free SQL Server Express edition. To use cell-level encryption, the schema must be changed to varbinary, then reconverted to the desired data type. This means the application must be changed to support the encryption-decryption operation; in addition, it can affect performance. Encryption of the database occurs at the page level, but when those pages are read to buffer pool, they're decrypted. Data can be encrypted using a passphrase, an asymmetric key, a symmetric key, or a certificate. The supported algorithms for column-level encryption are AES with 128,196,256 bit keys and 3DES. To learn more about column-level encryption
For Information Please Read This article http://technet.microsoft.com/en-us/library/ms179331.aspx
You can use the PWDENCRYPT and PWDCOMPARE like # Paresh J in his comment during new user Insertion use PWDENCRYPT like
Declare #Uname Varchar(250)='User2'
Declare #Pwd Varchar(250)='password'
Declare #UserTbl Table
(
id int identity(1,1),
Uname Varbinary(250),
Pwd Varbinary(250)
)
Insert Into #UserTbl(Uname,Pwd)
select PWDENCRYPT(#Uname),PWDENCRYPT(#Pwd)
and during the login of that user use PWDCOMPARE like
Declare #UnameEncr Varbinary(max)
Declare #PwdEncrypt Varbinary(max)
Select #UnameEncr=Uname,#PwdEncrypt=Pwd from #UserTbl where id=1
Select LoginMessage=Case When PWDCOMPARE(#Uname,#UnameEncr)=1
and PWDCOMPARE(#Pwd,#PwdEncrypt)=1
Then 'Correct Username / Password'
else 'Incorrect Username / Password' end

Resources