New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Database encryption [CORE657] #1023
Comments
Commented by: Alice F. Bird (firebirds) Date: 2005-12-02 16:24 Hi, I recommend this too (and I need it). Steve Charon has said Some DB Admins have the access rights to DB but they don't May be it will be solved with a default UDF's. I want to for example ; (INSERT example) INSERT INTO MYTABLE (MYFIELD1, MYFIELD2, MYFIELD3) (SELECT example) SELECT MYFIELD1, DECRYPTNUMERICDATA(MYFIELD2, May be this way better than the whole database encryption. Best Regards |
Commented by: Alice F. Bird (firebirds) Date: 2004-08-23 00:36 This should be a mandatory and selectable feature for any |
Commented by: Alice F. Bird (firebirds) Date: 2004-05-05 10:59 I recommend this too as this is something a PRO DB should |
Modified by: @dyemanovComponent: Security [ 10071 ] assignee: Vlad Horsun [ hvlad ] SF_ID: 807965 => |
Commented by: Mercea Paul (m24paul) It's not clear for me if I could specify what 'objects' I want to encrypt. I think for demo database where I want users to see tables and data but I don't want to allow users to see any procedure. |
Commented by: Dejan Schild (schild) There should be two levels of encryption: data and structure. |
Modified by: @dyemanovFix Version: 3.0.0 [ 10048 ] => |
Modified by: @pcisarWorkflow: jira [ 10681 ] => Firebird [ 15055 ] |
Commented by: Yiannis Bourkelis (yiannis) I would like to choose a table or a column to be encrypted, not everything because of the performance penalty. The encryption key could be specified in the connectionstring. That way we will not have to change anything else in our applications except of the connectionstring, that is a global variable most of times. |
Commented by: @livius2 >>Dejan Schild |
Modified by: @dyemanovassignee: Vlad Khorsun [ hvlad ] => Alexander Peshkov [ alexpeshkoff ] status: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Commented by: Mike (fibitoll) as mentioned in a duplicate issue and imho VERY important, "In the U.S., the meaningful use rules(for the healthcare industry) now dictates that data encryption has to be an option that can be turned on. And, the encryption algorithm that is acceptable is AES. " So it should be clearly visible for future users that the DB has a important security issue and maybe should not be used without special considerations on these issues. In other words, i think its extremly important to have this encryption feature fore firebird. And yes, i would neet it too, urgendly. For making it faster, this could be in a 2-Level-fashion(maybe in next Version V4, after first |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @pcisar
Relate to CORE1913
Is duplicated by CORE3783
Is duplicated by CORE3861
Relate to CORE2405
Votes: 27
SFID: 807965#
Submitted By: pcisar
Allow for database to be encrypted -- user
defined/selectable library/parameters.
The text was updated successfully, but these errors were encountered: