Page MenuHome GnuPG

GnuPG4Win with Enigmail in Thunderbird inserts unwanted blank lines in quoted text
Closed, InvalidPublic

Description

I have recently been having the same problem with enigmail as this user:
https://sourceforge.net/p/enigmail/forum/support/thread/de00ae35/

Quoting him:
"If someone sends me an email encrypted and signed, I received it correctly. If
I do a reply, encrypted and signed, of that email, the recipient will receive
the reply wit additional blank lines after each original message line."

However, this is not a problem with Enigmail or Thunderbird: I began
experiencing this issue after switching from the Cygwin GPG executable to Gpg4win.

I can reproduce the problem locally and after switching back to the Cygwin
executable, the problem does not occur.

Ways to reproduce:
Write a text-only message to yourself, longer than one line, encrypted with
enigmail.
When you receive the message, hit reply, type something under the quote and send
it, encrypted.
As soon as you receive this (second) message, there will be additional line
breaks in the quoted text that don't belong there.

If you change the GPG executable in the Enigmail settings to gpg.exe from the
bin directory of a Cygwin install, this does not happen.

Unfortunately, Cygwin GPG is an old version and Enigmail warns me that they will
stop supporting this version soon. It would be very nice if gpg4win would behave
like the gpg.exe from Cygwin in this context, because it makes longer email
threads practically unreadable.

Details

Version
2.2.5

Event Timeline

werner lowered the priority of this task from Normal to Low.Jul 29 2015, 12:03 PM
werner added a subscriber: werner.

Cygwin build of GnuPG have never been officially supported. In --clearsign mode
gpg sometimes needs to insert an final line break. Details vary between Unix
(i.e. Cygwin) and Windows builds. Thus I would not call this a bug.

Just to clarify: gpg does not insert just one final line break, it adds a line
break after every line of quoted text. For example,

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam
nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat,
sed diam voluptua. At vero eos et accusam et justo duo dolores et ea
rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem
ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing
elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna
aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo
dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus
est Lorem ipsum dolor sit amet.

would turn into

Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam

nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat,

sed diam voluptua. At vero eos et accusam et justo duo dolores et ea

rebum. Stet clita kasd gubergren, no sea takimata sanctus est Lorem

ipsum dolor sit amet. Lorem ipsum dolor sit amet, consetetur sadipscing

elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna

aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo

dolores et ea rebum. Stet clita kasd gubergren, no sea takimata sanctus

est Lorem ipsum dolor sit amet.

Please try to reproduce it using the command line. You may want to ask on the
Enigmail list on how to do that in the same way Engigmail does.

I managed to get the input out of enigmail and it turns out that the problem
with gpg is only very indirect: The ASCII-armored ciphertext has CR+LF line
endings in gpg4win, while the cygwin version only contains LF. This is probably
the cause of the problem, but certainly not a real bug in gpg4win.

lichtkegel reopened this task as Open.
lichtkegel claimed this task.

Cygwin emulates Unix on Windows and thus uses Unix conventions. Surely you run
into problems when mixing that with native Windows Programs like Enigmail or
Gpg4win.

marcus added a subscriber: marcus.

werner says it's not a bug.