-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We somehow talked past each other :D
I will try to explain the problem with a scenario:
1. You encrypt an image with OpenKeychain, so you open OpenKeychain
and go to "encrypt". The way it works in Android is that you now call
a method to open everything with MIME type "image/*". Then all
applications that serve images, like the gallery application pop up
and can be used to open an image.
2. You select the image from one of the apps which then returns the
data stream to OpenKeychain. OpenKeychain encrypts it using a
protected file storage.
3. Now the crucial step: Now this encrypted blob is shared to other
applications. Maybe you want to upload it via Dropbox. You are not
really supposed to save it anywhere on the disk, that's not Android's
model. So what MIME type should now be used to share this encrypted
blob? Following the RFC3156 we use "application/octet-stream" but
that's really unspecific. Recall that we are using no ASCII armor here.
The other way round it gets more problematic.
Consider decryption: You open OpenKeychain and want to decrypt a file.
So you only want to see the apps that serve the PGP-encrypted blobs.
Again, we can only use "application/octet-stream" per RFC, because
there is no specific MIME type for encrypted PGP-blobs.
Regards
Dominik
On 04/14/2015 07:04 PM, Werner Koch wrote:
On Mon, 13 Apr 2015 19:24, dominik(_at_)dominikschuermann(_dot_)de said:
The problem here is that Android does not allow to set a
Content-Type when sharing data between applications. A MIME type
however is the most preferred way of indicating the type of data
that is being
So what is the problem for an OpenPGP parser to do that on the
decrypted and de-mimed plaintext? Why inventing another mechanism
when we already have a matured one.
Assume your suggestion is added: Soon after that someone else may
request that license information is important enough that it needs
to go into OpenPGP. We would end up with our own meta data system.
With MIME all that is instantly available.
Shalom-Salam,
Werner
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJVLWN2AAoJEHGMBwEAASKCc00H/3HP0p/ghQUQQaJHsEGn1K97
iQ30/3I03fHi9kJSVWD8zqGsvvmGISyKKry0tCeiIVW2F/dhiJphcJSrcPteSOCz
qIvRSs4uqC/kwDeWeG9idZL/sdxjwnSug8IlaEBq8Vy6x//2JEpL1udbUQ9If2Dw
7/LYi6XFBZyRU84NAX7go80C3e334oymnV8sEvmSQdtNPRMlMOIWdwoJiddGdOnM
riujZ5mEHBU8i/YSdJQ7ZjUNmSHPVf+oZFq9Oe+sTG7XUq4iSgViQln17CsqrlP3
VeKzyXHafKm6HQhdsWCEq5DUUQHLGG0BKvjftuQRTdpAtgwDS8iS3qII9xZd0YY=
=ZPoY
-----END PGP SIGNATURE-----
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp