| Summary: | ENHANCEMENT: Protect the *.odb-file by setting a password to the file | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Soon <soon_1900> |
| Component: | Base | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | avsharapov, ebenich, Harry_the_korean, iplaw67, m.weghorn, robert, soon_1900, ssliackus, vasosergiou |
| Priority: | medium | Keywords: | needsDevAdvice, topicDesign |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=56897 | ||
| Whiteboard: | BSA | ||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 108914, 120255 | ||
|
Description
Soon
2013-10-19 08:01:02 UTC
I set this to new. It has never been implemented. It's implemented for all documents except for databases. Could it be internal databases couldn't work with such a protected file? Adding self to CC if not already on I am missing this feature very much: it is needed to send and receive .odb-files containing sensitive data over the internet. Of course I would have to unlock the .odb-file before starting to work or registering it... In the meantime it would be nice to have a little macro-dialog to zip and unzip .odb-files with password protection. Until this exists in a one .odb file, one other possible workaround is to connect to the database (rather than use embedded), e.g. connect to MariaDB/MySQL, which has been set up with permissions, and also locate the database on a server that all parties can access. I think this is a very nice solution, and has a good track record for security, and data integrity, but clearly it's not as simple as a single encrypted .odb file. *** Bug 113613 has been marked as a duplicate of this bug. *** any update on this feature? *** Bug 117796 has been marked as a duplicate of this bug. *** *** Bug 145760 has been marked as a duplicate of this bug. *** thanks to put me into the loop here, Alex |