Skip to content
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 revisited [CORE1913] #2346

Closed
firebird-automations opened this issue May 26, 2008 · 5 comments
Closed

Database encryption revisited [CORE1913] #2346

firebird-automations opened this issue May 26, 2008 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: John Perryn (johnperryn)

Is related to CORE657

Votes: 6

I'm evaluating firebird as a replacement for MS Access/Jet being used to publish genealogical databases on CD/DVD.

The missing feature in firebird which works so well in Jet is simple low level encryption that will discourage the casual user from browsing for keywords in our databases. What we require is more obfustication than encryption. This can be achieved by simple and efficient XORing at the block level down in the drivers. A database password would be the key, perhaps with some salt and a hash. The database user or the program which uses the data would supply the key. I understand that the security here is poor but high security is NOT a requirement.

Changes would be needed to the drivers of course and to the interfaces when creating and opening the database. The encryption would apply to all data in a database. A new metadata element needs to be provided so that a password supplied for opening a database can be confirmed as correct. This could be a hash of the original key.

The topic has been previously discussed (CORE657) and is mentioned in passing in the documentation. See http://www.firebirdsql.org/manual/fbmetasecur-low.html

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is related to CORE657 [ CORE657 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: danielrail (danielrail)

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.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

Closed as a duplicate for CORE657.

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Duplicate [ 3 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant