On Fri, Oct 26, 2012 at 3:13 PM, Staffan Tylen <firstname.lastname@example.org>
Mark, I just tried compiling ooSQLite again as I found there was an update to the makefile, but only to discover the same problem that I reported before (see below) which we never discussed. However I searched the web and found this:
So it seems like this issue was introduced with VC11 because VC11 corrects an old problem in the earlier compilers. As this affects botan only, will this be reported to them or will you fix this locally?
Probably neither. The Botan people are aware of this I'm sure. The 1.10 version I snatched is guaranteed to compile with VC++ 10. The next version, 1.11 requires a C++ 11 compliant compiler.
Including encryption in ooSQLite is stalled at this point. We have discussed this on the developers list. Making encryption software available is tightly regulated and controlled by Export Administration Regulations. While my research leads me to believe that the recent changes in government policy make it ok if the source code is publically available, one of the other developers feels we would still need to register with the EAR and that it is too hard to do.
Until we resolve this among the developers, ooSQLite won't be including encryption.
I was hoping to get a reply back from the U. S. Bureau of Industry and Security whom I asked for clarification. But, I haven't received an answer yet.