Feature #226
Share filestream across app boundary without leaking plaintext to disk
| Status: | New | Start date: | 07/31/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | 0.3.1 | |||
| Component: |
Description
Harlo wants: "read a file's datastream directly from IOCipher, without ever having to be burnt to a flat file somewhere on the flash drive."
Related issues
History
#1 Updated by abeluck over 5 years ago
Harlo, is the title correct? You want app B to be able to read a file from app A's IOCipher container, without having to write that data to disk?
Presumably this communication would take place over an Intent or something?
#2 Updated by hans over 5 years ago
It might make sense to use file permissions on the database file itself, then each app should be able to open the IOCipher VFS directly, since SQLite allows for multiple processes to access the same database file.
#3 Updated by abeluck over 5 years ago
In that case both apps will need IOCipher support, should it be possible for a non-IOCipher app to be able to access files in an IOcipher-enabled app's VFS?
#4 Updated by hans over 5 years ago
- Priority changed from Normal to Low
This is separate from Harlo's needs for Informacam. There she needs to be able to stream data between the GPG API and the IOCipher in the same app.
IMHO, doing this with Intents is out of the scope of IOCipher as I see it now. It provides the VFS and java.io APIs, and the app using it should provide anything else. That way the app can completely control the access to the VFS. But I could be convinced otherwise.
I switched the priority to low since we don't need this for anything now.
#5 Updated by abeluck over 4 years ago
- Assignee deleted (
abeluck)
#6 Updated by hans almost 4 years ago
- Target version set to 0.2 - reliability and cacheword interop
#7 Updated by hans almost 4 years ago
- Priority changed from Low to Normal
#8 Updated by hans over 3 years ago
- Target version deleted (
0.2 - reliability and cacheword interop)
#9 Updated by hans over 3 years ago
- Target version set to 0.3
#10 Updated by hans almost 3 years ago
- Target version changed from 0.3 to 0.3.1