Hi,
It would very interesting to have the ability to create new profile fields as well as new records fields and chose that those fields should be encrypted.
Encrypted custom profile fields and records fields
Moderators: hugo, alexandre, rmvanarkel
Encrypted custom profile fields and records fields
Thanks for your kind attention.
Best regards,
JAR
Best regards,
JAR
Re: Encrypted custom profile fields and records fields
Hi,
The best and easiest way would to encrypt the entire database. Postgress has various options: https://www.postgresql.org/docs/8.1/enc ... tions.html
The best and easiest way would to encrypt the entire database. Postgress has various options: https://www.postgresql.org/docs/8.1/enc ... tions.html
Re: Encrypted custom profile fields and records fields
Thank you very much.
Thanks for your kind attention.
Best regards,
JAR
Best regards,
JAR
Re: Encrypted custom profile fields and records fields
Hi,
If we encrypt a field of postgreSQL database, like username, that field is shown in cyclos frontend encrypted. This means that Cyclos cannot decrypt the field. Is there a way to show the field decrypted?
To encrypt the field username, we have used this query:
UPDATE users SET
username = PGP_SYM_ENCRYPT((select username from users where id=3001), 'password')
WHERE id=3001;
Ans to decrypt, we use the following query:
SELECT
PGP_SYM_DECRYPT(username::bytea, 'password') as username
FROM users WHERE id=3001;
Cyclos version: 4.12.3
If we encrypt a field of postgreSQL database, like username, that field is shown in cyclos frontend encrypted. This means that Cyclos cannot decrypt the field. Is there a way to show the field decrypted?
To encrypt the field username, we have used this query:
UPDATE users SET
username = PGP_SYM_ENCRYPT((select username from users where id=3001), 'password')
WHERE id=3001;
Ans to decrypt, we use the following query:
SELECT
PGP_SYM_DECRYPT(username::bytea, 'password') as username
FROM users WHERE id=3001;
Cyclos version: 4.12.3
Thanks for your kind attention.
Best regards,
JAR
Best regards,
JAR
Re: Encrypted custom profile fields and records fields
This is something that would require various structural changes, something we prefer not to do at this moment.
We still think that encrypting the entire database is really the way to go forward.
We still think that encrypting the entire database is really the way to go forward.