Since AIDL is not for passing large data, a blob can be passed to APG by
a Uri. This Uri is opened as a file by APG and read/written to. Note the
file is overwritten by APG, so make sure it is a copy if you want to
keep the original.
With the ApgServiceBlobProvider, Apg has an own ContentProvider that can
be used like mentioned above. For now the data is stored in the dir
where APG stores other files and NOT DELETED after en/decryption. This
is tbd. It can only be accessed by an application with the permission
"org.thialfihar.android.apg.permission.STORE_BLOBS".
ApgCon has been updated accordingly and can handle blobs with `setBlob`
and `getBlobResult`. That is a really easy way to en/decrypt large data.
Note that encrypting by blob should only be used for large files (1MB+).
On all other cases, the data should be passed as as String through the
AIDl-Interface, so no temporary file must be created.
See ApgCon for a complete example of how to connect to the AIDL and use
it. Or use it in your own project!
This helps to add new function calls easily. Some of the new enums
could be exported to other files to be included by other projects later
on.
Next step is asymmetric encryption.
Using Bundles makes passing data easier and does not need to redefine
the interface if the internel functions change.
The helper class has been updated accordingly. In addition, it wrappes
completely around all input and output (if wanted).
Provides an AIDL-API for other apps to encrypt and decrypt a string
symmetrically with a passphrase. Function names and API is by no way
finalized and will change!
Support for asymetric encription will follow.
For reference and discussion see issue #71,
https://code.google.com/p/android-privacy-guard/issues/detail?id=71
