tag:gpgtools.tenderapp.com,2011-11-04:/discussions/beta/956-wrapping-issue-reading-mail-from-pgp-non-commercial-usersGPGTools: Discussion 2016-02-08T16:25:00Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-04-03T04:44:49Z2015-04-03T04:44:50Zwrapping issue / reading mail from PGP non-commercial users<div><p>While it is almost certainly true that Mail and GPGTools are
doing the wrapping (more likely just Mail.app is and then GPGTools
falls because the new line breaks the expected fields), it is also
true that the PGP Desktop string is <em>way</em> too long. All
OpenPGP messages are base64 encoded and the version or comment
lines need to fit within that, but the PGP Desktop string there is
87 characters long.</p>
<p>Symantec need to change that to something like this (but they
probably won't):</p>
<pre>
<code>Version: PGP Desktop 10.2.0 (Build 1672)
Comment: not licensed for commercial use: www.pgp.com</code>
</pre></div>Bentag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-04-03T14:19:19Z2015-04-03T14:19:19Zwrapping issue / reading mail from PGP non-commercial users<div><p>It's all true and the fact is it would be great to fix this
problem even if Symantec fixes PGP Desktop - because of the tons of
users who just won't upgrade.</p>
<p>I reported this back to Symantec to fix it on their side, but I
would like to see even an official workaround for people who just
have to deal with this type of correspondence.</p></div>Juraj Bednartag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-04-03T15:19:30Z2015-04-03T15:19:31Zwrapping issue / reading mail from PGP non-commercial users<div><p>Then you need to see if there's an option in Mail.app to not<br>
automatically word-wrap long lines, because chances are extremely
high<br>
that that's what's adjusting the line and splitting it.</p>
<p>GPGTools just passes any message block which begins and ends
with the<br>
relevant lines (BEGIN PGP MESSAGE and END PGP MESSAGE) to the
GPG<br>
command line program and it operates according to the OpenPGP
standard<br>
(which is why the other clients you mentioned work).</p></div>Bentag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-06-25T11:07:59Z2015-06-25T11:07:59Zwrapping issue / reading mail from PGP non-commercial users<div><p>Hi Juraj,</p>
<p>while as discussed already this isn't a bug, it would indeed
still be great, if we could deal with this form of malformed
content.</p>
<p>We have a ticket for this problem. I connected this discussion
with the existing ticket. That means, should this discussion get
closed, it will be re-opened as soon as the ticket is closed. That
way you'll receive a notification. Feel free to open a new
discussions should you run into further problems or need
assistance.</p>
<p>All the best,<br>
steve</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-07-05T10:36:32Z2015-07-05T10:36:32Zwrapping issue / reading mail from PGP non-commercial users<div><p>Hi Juraj,</p>
<p>good news. We think, this issue has been fixed. If you want to
test the fix, please download our <a href="https://releases.gpgtools.org/nightlies/">latest nightly GPG
Suite</a>. That page also has sig and SHA1 to verify the download.
It would be very helpful, if you can provide feedback, as to wether
the fix works as expected.</p>
<p>If you have other questions you can open a new discussion any
time.</p>
<p>Best, steve</p>
<p>Disclaimer: This is a development version which has not been
thoroughly tested yet, so bugs or crashes are to be expected.
Thanks for helping us test this fix.</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-07-06T13:47:04Z2015-07-06T13:47:05Zwrapping issue / reading mail from PGP non-commercial users<div><p>Thanks, this fixed the issue, thank you very much!</p></div>Juraj Bednartag:gpgtools.tenderapp.com,2011-11-04:Comment/364604752015-07-06T18:34:07Z2015-07-06T18:34:07Zwrapping issue / reading mail from PGP non-commercial users<div><p>Perfect. Glad, this is solved for you. I'm closing this
discussion. If you need further assistance or have questions you
can re-open this discussion here or open a new one any time.</p>
<p>Best, steve</p></div>Steve