-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/14/2015 10:15 PM, Werner Koch wrote:
On Tue, 14 Apr 2015 20:59, dominik(_at_)dominikschuermann(_dot_)de said:
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.
Okay, so your comments are about PGP/MIME. I assumed you were
talking about
5.9. Literal Data Packet (Tag 11) [...] - A one-octet field that
describes how the data is formatted.
where we discussed to add an 'm' format to describe that the
content is a MIME message.
Not sure what this has to do with my problem. The Literal Data Packet
indicates the type of the data that is inside the encrypted blob not
the type of the encrypted blob. The Literal Data Packet together with
the actual data is encrypted and can not be accessed before decryption.
But yes, this is another problem for us and adding an "m" format
together with a MIME type would fix this. So +1 for this.
If you want to indicate that the content is some OpenPGP data you
should use the the MIME types "application/pgp-encrypted" etc.
along with the above suggested format specifier. You can of course
do the same at the outer level.
What needs to be changed for this?
Maybe I misunderstand the RFC3156, but "application/pgp-encrypted"
only contains the version number not the encrypted blob. The actual
blob is inside "application/octet-stream".
Where is it specified that "application/pgp-encrypted" can also
directly contain the data? Please point me to the line in the RFC.
I think this comes from the fact that RFC3156 only talks about ASCII
armored data for email transfer.
Regards
Dominik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJVLXv0AAoJEHGMBwEAASKCuqsIAI6bG709cIIxZHQ153IEHSZ/
icjPVUhi21pMN0SyIZtg+FnzJwPeLlK68e3T8GJ/LMEISHOdvL/2WJDS1AbR1Dgz
PHMjFNl14A3CwQ2mMQ8TTbv5tlTf4TeLDYLm4S6T0gmL7ouO248DXLNbEraT/Uu8
7BBXEatWsjHQIxEMTMVeSehnaJYbtToo1AUwxz4nxBRQZWfEYBeDo9HVUtGzvYVH
204LhY4t+2iqkiSDbCzCX0RIc4SlsWjTJ6F4Y/Qy4kgRX0hvONUHXcsALyNkIWAF
1eYta3k25j+vekWz3t+HMTjjredPZ51JA3YylI4SrwsaJwzFxXuW2iNysc7ccmE=
=Z5MC
-----END PGP SIGNATURE-----
_______________________________________________
openpgp mailing list
openpgp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/openpgp