On Sat, 16 May 2009 15:10:06 david wrote: > You encrypt the document first - before sending. So type oo document > then encrypt it - save it it to disk then open email and add it as an > attachment - this will preserve formatting you do not then have to > encrypt again - you could digitally sign if you wish. > > David > > webmas...@felipe1982.com wrote: > > I will do my best to describe as succinctly and clearly as possible. To > > begin, I use openSUSE, openoffice for documents, and [usually] kmail for > > email. I created a document in OOo and clicked on the 'email' button to > > send it to my "other" email address x...@student.qut.edu.au [backup]. I > > sent the file signed and encrypted. The other address has only a web > > interface, and as such, has no support for PGP/MIME. As expected, I see > > two attachments, application/pgp-encrypted "VERSION 1" file, and > > application/octet-stream (my encrypted .odt file). It isn't actually > > binary, it appeares in ASCII when downloaded and opened in text editor. I > > ran it through Kgpg, and also separately through gpg command line, and > > was disappointed that I did not recover my original .odt file. > > > > The top portion contains email header information stuff (stuff I don't > > want, or care to understand). There is a signature at the very bottom, > > but verification fails (it is *my*own* pub/priv key pair). In the middle, > > above the signature, and below the email header stuff, there is an > > ascii-armoured portion of data. I have not yet attempted to select it > > all, copy, paste, decrypt, because I thought to myself, "there must be a > > better (read: easier) way to do this..." So, is there? > > > > I forwarded the message back to my x...@felipe1982.com address, and viewed > > it in kmail (which as you all know, supports cool things like pgp/mime). > > But it (after submitting my passphrase) will not decrypt! > > > > Is this the normal behaviour of pgp/mime. I did read a little (albeit > > quickly and not in detail) of rfc3156 (is this the most recent?). > > > > Any ideas, suggestions, comments appreciated. Thanks. > > > > Felipe > > > > > > > > > > > > _______________________________________________ > > Gnupg-users mailing list > > Gnupg-users@gnupg.org > > http://lists.gnupg.org/mailman/listinfo/gnupg-users I assume[d] (maybe incorrectly?) that clients without support for pgp/mime would still be able to manually extract/download the attachments and manually decrypt them and reliably open, read and change them. Does the RFC allow for 'legacy' email clients to still read/decrypt attachments as normal?
Felipe
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
