webpg-chrome
webpg-chrome copied to clipboard
gmail integration and line wraps
With the understanding that the gmail support is super-beta, on the sign/encrypt and send action, all the lines wrap, causing the recipient to be unable to decrypt/verify the message - see attached.
I believe this has been fixed in the development version of WebPG, and should be present in the next release.
Problem's on Firefox too. I cannot read message Gmail treated it as plain text and wrapped it
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 uheou ns hueno sutns -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJR0anvAAoJEKsuyZb1RVYssAkH/iAfjEQyTUrkKJV0UcftIHrU ycLCrJoQJOLAPMVjPfuZKhsn+Hk7voMIlcJBhTXi+ZP1CddV4a8qT2I8xvI95ljx ZY33MzGprUzG+g6Rc1fLwtfNmuduutvT1gvOmgMfwYap+Id2km5StmnYDDxhxeLl 93WO1MDqkE5YRtf1obw2xC/eoXqWB5lYXsyKumEdwU9n1Vbro1gJwEomNuQYbHj1 0GUNXGQBWN33kb5x1fXowICrDXl5bRYscC+X/ksTtREwuCh6Mboc5kXLrLKMAOxK /NYcgbdj4Uuc3GWltzaS0DvoBZig6TzA4tg/WWZT0vCxhycYTkj1kxVfJBWBcuU= =8y6v -----END PGP SIGNATURE-----
@NgoHuy can you confirm the fix for this with the running development cycle (v0.9.4)?
Instructions for installing the dev version are here: https://github.com/kylehuff/webpg-chrome/wiki#install-development-build
I confim that can fix Thank you very much
Line wraps fixed in Chrome with 0.9.4, but while previous signed messages to myself under 0.9.3 pass signature checks (and are cleanly formatted when viewed with WebPG), new ones do not. Not sure if I should put that under something else, though.
I just wanted to add a note that I'm using 0.9.4 on Firefox, but as far as I can tell, this is not fixed.
Using 0.9.4 on Chrome on OSX works when I use the master branch, but I've started noticing <img class="ajT" src="images/cleardot.gif">
being added to the end of messages over the last few days.
This is something added by the GMAIL web interface, and unfortunately, these types of issues are going to be prevalent due to the manner in which the WebPG GMAIL integration works currently.
I am in the process of revising how the sending mechanism for GMAIL works entirely to prevent these types of issues, as well as add support for true PGP/MIME email messages (at present, only sending of inline PGP data as the message content is supported).
Great, let me know if there's anything I can do