Since no one has answered my question yet, I just would like to know whether my question is unclear or no one knows the answer is.
AIR doesn't support extensions to its built-in SQLite database engine, so there isn't a way that you could create a database file in another tool using an extension and have it work in AIR. You have to use the encryption built in to AIR.
Thx for the reply.
Here's an interesting thing that I found from the SQLite author:
1) He says that Adobe AIR team is a licensee for SEE.
2) He doesn't know which of the 4 SEE encryption algorithms ADOBE is using.
You can see what encryption algorithm that SQLite supports over here http://www.hwaci.com/sw/sqlite/see.html
With those 2 facts, I think that it would make sense for AIR to be able to open the encrypted DB, which was done by SQLite command line tool.
I just need to know what encryption algorithm that ADOBE AIR supports.
I spoke to the AIR developer who implemented the encryption. But first, you should be aware that what you are doing isn't a supported scenario so if it doesn't work, or we make changes that break your application in the future, you are probably out of luck. With that said, AIR uses AES-128 with CCM mode.
Thx for the reply.
Hmmm...that's going to be an issue with my AIR app because my AIR app needs to download encrypted DBs from the server.
The only way that I know to encrypt the DBs on the server is using the sqlite3 command line tool.
Does ADOBE AIR sdk has command line tool for doing this?
The SDK does not have tools for this. You could write such a tool using AIR itself, but could run into issues running AIR on a "headless" server. See http://groups.google.com/group/fluint-discussions/browse_thread/thread/b4be801162a00dfc for one solution to that problem.
Thx for your prompt reply.
This is certainly a big issue. Not sure on how I could utilize the AIR encryption on the server side.
And regarding what you said:
"I spoke to the AIR developer who implemented the encryption. But first, you should be aware that what you are doing isn't a supported scenario so if it doesn't work, or we make changes that break your application in the future, you are probably out of luck. With that said, AIR uses AES-128 with CCM mode."
What were the reasons that it's not supported?
Even though it seems that I am currently the only one who is nagging about this but I would think a desktop application that uses a 3rd-party engine would be compatible with the 3rd-party engine tool, at least the CLI.
I might not explaining it too well but from our conversation on this thread, you get the idea.
If there's a way to help this as a feature request, I would be glad to help out.