I've been exploring adding the ability to encrypt / decrypt the SQLite
database file in ooSQLite. Unfortunately I didn't at first consider the
U.S. restrictions on exporting encryption related software. The encryption
software itself is from the Botan library, details on Botan are at:
I concur. That's exactly what my research has uncovered to date too.
Rick
On Tue, Oct 23, 2012 at 11:51 AM, Mark Miesfeld miesf...@gmail.com wrote:
I've been exploring adding the ability to encrypt / decrypt the SQLite
database file in ooSQLite. Unfortunately I didn't at first consider the
On Tue, Oct 23, 2012 at 10:33 AM, Rick McGuire object.r...@gmail.comwrote:
I concur. That's exactly what my research has uncovered to date too.
Okay good. I'll wait awhile for David's input and then probably go about
taking care of this next week.
--
Mark Miesfeld
Linking to a crypto library is not a problem. But including the crypto
code in our distribution library is a major hassle. It requires that
declarations be filed with the US government for exporting the code to
other countries and we are responsible for ensuring that it does not
fall into the
David Ashley w.david.ash...@gmail.com wrote:
...we are responsible for ensuring that it does not fall into the wrong
hands (a banned country).
What stops anyone from downloading pretty much any code they want to use, in
the UK or USA or wherever, then putting it on a USB stick and sending it
The bottom line is that enforcement is almost non-existent for this type
of software for just the reasons you mention (as well as others). But it
is still against the law to export it without the proper declarations
and has severe penalties which I will not take chances with. If you are
caught
On Tue, Oct 23, 2012 at 11:51 AM, David Ashley w.david.ash...@gmail.comwrote:
Linking to a crypto library is not a problem. But including the crypto
code in our distribution library is a major hassle. It requires that
declarations be filed with the US government
This is no longer true for
