Page MenuHome GnuPG
Feed Advanced Search

Sep 28 2016

werner added a project to T1143: better heuristic for choosing an encryption key based on a User ID: Duplicate.
Sep 28 2016, 9:17 AM · Duplicate, gnupg, Feature Request

Aug 5 2016

aheinecke added a project to T2420: TOFU Info for a Key: Duplicate.
Aug 5 2016, 10:49 AM · Duplicate, gpgme, gnupg (gpg21), Feature Request
aheinecke closed T2420: TOFU Info for a Key as Resolved.
Aug 5 2016, 10:49 AM · Duplicate, gpgme, gnupg (gpg21), Feature Request

Jul 19 2016

justus added a project to T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew): gpgrt.
Jul 19 2016, 12:01 PM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report
justus added a comment to T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew).

Yes, that is very likely the same bug. Feel free to reopen this report if yuo
can still reproduce it, in which case a backtrace would be very handy.

Fixed in 28fd0ab.

Jul 19 2016, 12:01 PM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report
justus removed a project from T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew): gnupg.
Jul 19 2016, 12:01 PM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report
justus closed T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew) as Resolved.
Jul 19 2016, 12:01 PM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report

Jul 14 2016

werner removed a project from T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!": Unreleased.
Jul 14 2016, 7:12 PM · Bug Report, gnupg, Duplicate

Jul 5 2016

aheinecke added a project to T2330: GpgOL tries to decrypt sent E-Mails which are encrypted by Outlook: Duplicate.
Jul 5 2016, 2:42 PM · Duplicate, gpgol, Bug Report
aheinecke added a comment to T2330: GpgOL tries to decrypt sent E-Mails which are encrypted by Outlook.

Hi,

Thanks for your report. With gpg4win-2.3.2 we addressed that problem. See also
issue2319 which was also about this problem.

Please let us know if you still have that problem with 2.3.2 I could reproduce
it in testing and with the fix it no longer happens so I'm hopeful this can be
resolved :-)

Regards,
Andre

Jul 5 2016, 2:42 PM · Duplicate, gpgol, Bug Report
aheinecke added a comment to T2330: GpgOL tries to decrypt sent E-Mails which are encrypted by Outlook.

Duplicate of T2319

Jul 5 2016, 2:42 PM · Duplicate, gpgol, Bug Report

Jun 9 2016

gfontenot added a comment to T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew).

Sorry for going AWOL on this, Werner. Do you still need a backtrace from me, or is the
one from 2371 enough?

Jun 9 2016, 4:58 PM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report
gniibe added a comment to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!".

It was fixed in db1ecc8212defdd183abbb6b1407fcc8d2dc9552 for 2.1.
In 2.1, HDRLEN=0 for all callers, so, there will be no same "Ohhhh jeeee" any more.

In 1.4 and 2.0, HDRLEN is used as a hint. There is no need to change 1.4 and
2.0. Detail is described in:
https://lists.gnupg.org/pipermail/gnupg-devel/2016-June/031178.html

Jun 9 2016, 12:56 AM · Bug Report, gnupg, Duplicate
gniibe closed T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!" as Resolved.
Jun 9 2016, 12:56 AM · Bug Report, gnupg, Duplicate
gniibe removed a project from T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!": In Progress.
Jun 9 2016, 12:56 AM · Bug Report, gnupg, Duplicate
gniibe added a project to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!": Unreleased.
Jun 9 2016, 12:56 AM · Bug Report, gnupg, Duplicate

Jun 8 2016

werner added a project to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!": In Progress.
Jun 8 2016, 6:51 PM · Bug Report, gnupg, Duplicate
werner added a comment to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!".

So, how do we proceed? Release 2.1.13 and wait for potential problems?

Jun 8 2016, 6:50 PM · Bug Report, gnupg, Duplicate

Jun 4 2016

werner added a project to T1445: keyid-format fingerprint: Duplicate.
Jun 4 2016, 11:03 AM · gnupg, Duplicate, Feature Request

Jun 2 2016

gniibe added a comment to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!".

In 1.4 and 2.0, --import just copies the block, so the bug doesn't hit. In 2.1,
when it tries to write to keybox, the bug hits.

Jun 2 2016, 6:57 AM · Bug Report, gnupg, Duplicate
gniibe added a comment to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!".

The check what Neal introduced is somehow orthogonal to the change of mine.

The key in question, there is a User ID packet of length >= 256 (because he
include ssh key string in his User ID).
In the code of build-packet.c, gpg assumed the length of User ID is < 256 and it
is hard coded to have header length 2.
With the check (in gpg 2.1), it causes an error. I think that, in gpg 1.4 and
2.0, gpg creates malformed packet with incorrect length (LSB of the length).

Jun 2 2016, 1:50 AM · Bug Report, gnupg, Duplicate

Jun 1 2016

dkg added a comment to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!".

fwiw, i first encountered this by doing a full-keyring refresh from the
keyservers. Dying rather than adjusting or accomodating the malformed header
meant that all keys after this one failed to refresh.

In general, dying outright seems likely to make an observed problem worse than
it needs to be.

Jun 1 2016, 3:27 PM · Bug Report, gnupg, Duplicate
bernhard added a project to T2070: Can not leave passphrase empty when exporting secret key: Duplicate.
Jun 1 2016, 3:25 PM · Duplicate, Bug Report, gnupg
neal added a comment to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!".

FWIW, I added the stricter check. Previously, we specified the header size, but
didn't check that it was respected. When discussing this with Werner, he said
that respecting the header size was important, which is why I chose to die
rather than silently change the header size.

Jun 1 2016, 2:49 PM · Bug Report, gnupg, Duplicate
werner added a project to T2307: Failure to export secret key (Can't encode length=518 in a 2 byte header!): Duplicate.
Jun 1 2016, 2:01 PM · Duplicate, Bug Report, gnupg, gnupg (gpg21)
werner added a comment to T2307: Failure to export secret key (Can't encode length=518 in a 2 byte header!).

Duplicate of T2374

Jun 1 2016, 2:01 PM · Duplicate, Bug Report, gnupg, gnupg (gpg21)
werner added a project to T2374: exporting public key fails with "Ohhhh jeeee: Can't encode length=294 in a 2 byte header!": Duplicate.
Jun 1 2016, 1:59 PM · Bug Report, gnupg, Duplicate

May 30 2016

werner added a project to T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew): Duplicate.
May 30 2016, 8:08 AM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report
werner added a comment to T2358: gnupg 2.1, gpg-agent crashing on 'assertion failed' (OS X, Homebrew).

Duplicate of T2371

May 30 2016, 8:08 AM · gpgrt, Duplicate, gpgagent, gnupg (gpg21), Bug Report

May 27 2016

werner lowered the priority of T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL from High to Normal.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

Duplicate of T2171

May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner removed a project from T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Bug Report.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a project to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Duplicate.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

You can now. Thus is not a bug but a feature request.

Note that we do not use Microsoft compilers but use gcc and in cross build
environment.

May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a project to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Feature Request.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

May 6 2016

werner added a comment to T2107: dirmngr crash when searching keyservers on OpenBSD.

Duplicate of T2348

May 6 2016, 8:23 PM · Duplicate, gnupg, Bug Report, dirmngr
werner added a project to T2107: dirmngr crash when searching keyservers on OpenBSD: Duplicate.
May 6 2016, 8:23 PM · Duplicate, gnupg, Bug Report, dirmngr

Apr 22 2016

justus added a comment to T2323: fdpassing fails during make check.

Thanks for the output. That indeed confirms my suspicion. Let's read it together:

[...]
libassuan.so.0 =>
/home/ann/gnupg-2.1.11/libassuan-2.4.2/src/.libs/libassuan.so.0 (0x002e4000)
libgpg-error.so.0 => /lib/i386-linux-gnu/libgpg-error.so.0 (0x0066d000)

ldd says which library is used to satisfy a dependency at load time. You see
here that for libassuan.so.0 your newly built library is used. That is good.
However, for libgpg-error.so.0 the library from your system is used which does
not have gpgrt_asprintf, hence the error message in your first log.

What you need to do is to make sure the runtime linker finds your gpg-error
library. Since this kind of problem will occur for each library, it is best to
install all the libraries you built to a common prefix, say /home/ann/local or
/usr/local by specifying --prefix=/my/prefix at configure time, and then to set
LD_LIBRARY_PATH to /my/prefix/lib and include /my/prefix/bin in PATH, so that
gpg-error-config and libassuan-config and co are found at compile time. Feel
free to ask questions if you get stuck.

(If you don't want to do all this by hand, and merely want a working modern
GnuPG, you can also use the 'speedo' framework. See the README in the GnuPG
repository for some hints.)

Apr 22 2016, 2:12 PM · Duplicate, libassuan
justus removed a project from T2323: fdpassing fails during make check: Bug Report.
Apr 22 2016, 2:12 PM · Duplicate, libassuan
justus closed T2323: fdpassing fails during make check as Invalid.
Apr 22 2016, 2:12 PM · Duplicate, libassuan
ann added a comment to T2323: fdpassing fails during make check.

Apr 22 2016, 4:25 AM · Duplicate, libassuan
ann added a comment to T2323: fdpassing fails during make check.

Thank you. I've attached the output from 'ldd tests/fdpassing'. Not sure how to
read it.

Apr 22 2016, 4:25 AM · Duplicate, libassuan

Apr 18 2016

justus claimed T2323: fdpassing fails during make check.
Apr 18 2016, 12:35 PM · Duplicate, libassuan
justus added a comment to T2323: fdpassing fails during make check.

I don't think the bugs are necessarily related. Your issue looks like you build
your own libgpg-error and linked fdpassing against that, but your runtime linker
uses your system-supplied libgpg-error. Try running 'ldd tests/fdpassing' to
see which libgpg-error is used at run-time. Feel free to ask if you need more
assistance.

Apr 18 2016, 12:35 PM · Duplicate, libassuan
justus lowered the priority of T2323: fdpassing fails during make check from High to Normal.
Apr 18 2016, 12:35 PM · Duplicate, libassuan
ann added a project to T2323: fdpassing fails during make check: Duplicate.
Apr 18 2016, 5:55 AM · Duplicate, libassuan

Feb 23 2016

ueno added a comment to T2034: pinentry emacs features need documentation.

It has been there since the 21.1 release. The relevant commits are:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=b021ef186f6062705a29ae8e3840ad32db451811
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=719349f6d0e464d4f71963b87f6bfa08ac630aa7

Feb 23 2016, 8:14 AM · Bug Report, pinentry

Feb 22 2016

neal added a comment to T2034: pinentry emacs features need documentation.

@ueno: This is reasonable. Thanks for the explanation. Do you happen to know
approximately what version started to enable these protections?

Feb 22 2016, 11:32 AM · Bug Report, pinentry
ueno reopened T2034: pinentry emacs features need documentation as "Open".
Feb 22 2016, 3:18 AM · Bug Report, pinentry
ueno added a comment to T2034: pinentry emacs features need documentation.

D315: 782_0001-doc-Make-Emacs-frontend-description-more-accurate.patch

Feb 22 2016, 3:18 AM · Bug Report, pinentry
ueno added a comment to T2034: pinentry emacs features need documentation.

Thanks for writing this up, Neal. However, I found the claim a bit
inaccurate by now. I am attaching a proposed fix for this.

Emacs keeps all key presses buffered.
(You can see the recent key presses by typing @code{C-h l}
(@code{view-lossage}) in emacs.)

This is not the case with the common `read-passwd' function, which
clears the log on every key press. See:
http://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/subr.el#n2126

Because of this concern, Emacs doesn't
enable this by default (the user has to run @code{(pinentry-start)},
e.g., from his or her @code{.emacs} file, explicitly).

This is no longer true. Emacs checks the allow-emacs-pinentry option
of gpg-agent, and start it if desired.

Further, Emacs is a huge program,
which doesn't provide any process isolation to speak of. As such,
having it handle the passphrase adds a huge chunk of code to the
user's trusted computing base.

Yes. However, all official packages on elpa.gnu.org are digitally
signed and supposed to work courteously. Users can still use unsigned
or 3rd party packages, but I think it is similar to the situation
where distribution packages are used.

In conclusion, I would say the Emacs pinentry provides the same level
of security as the current pinentry-gtk2 (as long as the
implementation is sane). My only concern was that Emacs `read-passwd'
is implemented in Elisp and thus cannot use secure memory. However,
it is also true for pinentry-gtk2, which uses the default GtkEntry
now.

Feb 22 2016, 3:18 AM · Bug Report, pinentry

Jan 15 2016

werner closed T2055: AIX 7.1 Key Generation Failed with Segmentaiton fault signal 11 as Resolved.
Jan 15 2016, 4:26 PM · Bug Report, gnupg, Duplicate
werner added a comment to T2055: AIX 7.1 Key Generation Failed with Segmentaiton fault signal 11.

Let's assume this is the case and the bug has been resolved.

Jan 15 2016, 4:26 PM · Bug Report, gnupg, Duplicate

Jan 5 2016

aheinecke added a comment to T1768: Outlook 2010 crashes and disables GPG4Win 2.2.2. Plugin.

Duplicate of T1837

Jan 5 2016, 11:45 AM · Duplicate, Info Needed, Bug Report, gpg4win
aheinecke added a project to T1768: Outlook 2010 crashes and disables GPG4Win 2.2.2. Plugin: Duplicate.
Jan 5 2016, 11:45 AM · Duplicate, Info Needed, Bug Report, gpg4win

Dec 18 2015

werner added a comment to T2199: PATCH v3 0/7] SP800-90A Deterministic Random Bit Generator.

or well, gcrypt-devel in this case.

Dec 18 2015, 4:47 PM · Mistaken, libgcrypt, Duplicate
werner added a comment to T2199: PATCH v3 0/7] SP800-90A Deterministic Random Bit Generator.

Please do not postarbitray pacthes to the tracker. Patches need to go to
gnupg-devel instead.

Dec 18 2015, 4:46 PM · Mistaken, libgcrypt, Duplicate
werner added a project to T2199: PATCH v3 0/7] SP800-90A Deterministic Random Bit Generator: Duplicate.
Dec 18 2015, 4:46 PM · Mistaken, libgcrypt, Duplicate

Dec 11 2015

aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Thanks for helping keep track of all these issues.

Yes this only fixes the problem that has already been fixed in the last Gpg4win
Versions. So that this will be fixed in future gnupg-2.1 versions.

Still to help us better seperate the problems I would like to close this as for
me this bug was about "Wrong encoding in a localized version".

  • the more critical "passphrase with non ASCII characters" problem (as reported

only here, see T1691 (andreaerdna on Aug 19 2014, 02:36 AM / Roundup)); does this bug need a
dedicated new Issue to be addressed and solved?

I actually overlooked this in this issue. Can you please open another issue for
that. And add me to the Nosy.

  • the "utf-8 encoding of encrypted filenames" / "strange behaviour of --utf8-

strings, --no-utf8-strings and --charset options" (as reported in Issue 1409 ad
probably similar to Gpgtar Issue 1624 / Gpa Issue 2185)

If this problem was still existing with gpg4win this is still a problem.

  • the "charset weirdness searching keyserver for some non-ASCII user IDs under

non-UTF-8 locales" (as reported in Issue 1514).

This appears not to be windows specific. Also I think this works except for
cases where the Key in question is problematic. If I search on windows for
emanuel@intevation.de I get the correct Umlauts shown. Might be a Problem though
for characters that are unrepresentable in the 8 Bit codepage.

Dec 11 2015, 4:21 PM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
andreaerdna reopened T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows as "Open".
Dec 11 2015, 3:43 PM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
andreaerdna added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

It sounds great!

So this patch, as the previous one, solves the "incorrect display of GPG 2
output translated into another language" (as reported here and previously also
in Issue 1373 and Issue 1674).

Does this patch solve also the "incorrect display of filenames with non ASCII
characters" (as reported here and previously also in Issue 1409)?

By the way, as I understand, this patch doesn't fix:

  • the more critical "passphrase with non ASCII characters" problem (as reported

only here, see T1691 (andreaerdna on Aug 19 2014, 02:36 AM / Roundup)); does this bug need a
dedicated new Issue to be addressed and solved?

  • the "utf-8 encoding of encrypted filenames" / "strange behaviour of --utf8-

strings, --no-utf8-strings and --charset options" (as reported in Issue 1409 ad
probably similar to Gpgtar Issue 1624 / Gpa Issue 2185)

  • the "charset weirdness searching keyserver for some non-ASCII user IDs under

non-UTF-8 locales" (as reported in Issue 1514).

Dec 11 2015, 3:43 PM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
werner added a project to T2182: Why does GPG ciphertext length differ with fixed plaintext length?: Duplicate.
Dec 11 2015, 1:11 PM · Support, Duplicate, gnupg
werner added a comment to T2182: Why does GPG ciphertext length differ with fixed plaintext length?.

Please do not open another bug but comment on the very same bug you posted a few
days ago (issue2166).

In any case, this is a question and not appropriate for a bug tracker. Use one
of the mailing lists for such questions or see https://gnupg.org/service.html
for commercial support offers.

Dec 11 2015, 1:11 PM · Support, Duplicate, gnupg
werner added a comment to T2182: Why does GPG ciphertext length differ with fixed plaintext length?.

Duplicate of T2166

Dec 11 2015, 1:11 PM · Support, Duplicate, gnupg
aheinecke closed T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows as Resolved.
Dec 11 2015, 1:10 PM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

After some more discussion and testing in the development jabber channel werner
agreed to include this patch. Pushed to libgpg-error with 823e858. So this will
hopefully be part of the first gnupg modern release that will include localization.

Dec 11 2015, 1:10 PM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

D210: 737_0001-Fix-windows-8bit-encoding-conversion.patch

Dec 11 2015, 11:32 AM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
aheinecke changed Version from 2.0.26 to 2.1 on T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.
Dec 11 2015, 11:32 AM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg
aheinecke added a comment to T1691: Charset / codepage problems in GnuPG 2.0.26 on MS Windows.

Updated Patch against libgpg-error where this code now lives.

Please apply this patch or something similiar.

The problem I can see is that with this code in libgpg-error now GUI
applications may use it which want to get "GUI Native".

Probably better to introduce a new function "wchar_to_console" ? And use it from
GnuPG. Does GPA use that conversion function?

Might be a good time for this now where gnupg master already depends on new
symbols in libgpg-error.

Dec 11 2015, 11:32 AM · gnupg (gpg14), Windows 32, gnupg (gpg20), gpg4win, Windows, Bug Report, gnupg

Nov 6 2015

neal added a project to T1232: expired user-id selection preference: Duplicate.
Nov 6 2015, 12:39 PM · Duplicate, Bug Report, gnupg

Nov 4 2015

neal removed a project from T259: Old link in GPH: Stalled.
Nov 4 2015, 12:13 AM · Duplicate, Bug Report, gpgweb
neal closed T259: Old link in GPH as Resolved.
Nov 4 2015, 12:13 AM · Duplicate, Bug Report, gpgweb
neal added a comment to T259: Old link in GPH.

Current URL was reported in 1495. Closing this issue and leaving that one open.

Nov 4 2015, 12:13 AM · Duplicate, Bug Report, gpgweb
neal added a project to T259: Old link in GPH: Duplicate.
Nov 4 2015, 12:12 AM · Duplicate, Bug Report, gpgweb

Oct 28 2015

werner closed T2059: Rate limit password attempts by pinentry., a subtask of T2034: pinentry emacs features need documentation, as Resolved.
Oct 28 2015, 5:28 PM · Bug Report, pinentry

Oct 20 2015

iprok closed T2111: ssh-agent support broken as Resolved.
Oct 20 2015, 4:30 PM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
iprok changed Version from 2.1.9 to 2.1.8 on T2111: ssh-agent support broken.
Oct 20 2015, 4:30 PM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
iprok added a comment to T2111: ssh-agent support broken.

Removing and readding key helped. Thanks. Seems to be solved in 2.1.9

Oct 20 2015, 4:30 PM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
gniibe added a comment to T2111: ssh-agent support broken.

Please remove your private key(s) of ed25519 and register it again.

Please see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798956#24

Oct 20 2015, 12:42 PM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
iprok changed Version from 2.1.8 to 2.1.9 on T2111: ssh-agent support broken.
Oct 20 2015, 11:31 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
iprok added a comment to T2111: ssh-agent support broken.

The same issue in 2.1.9

Oct 20 2015, 11:31 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
iprok renamed T2111: ssh-agent support broken from ssh-agent support broken in 2.1.8 to ssh-agent support broken.
Oct 20 2015, 11:31 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate

Oct 16 2015

aheinecke added a comment to T2007: GPG OL: Cannot decrypt mails send with OpenPGP/MIME format.

Duplicate of T1826

Oct 16 2015, 2:41 PM · Duplicate, Bug Report, gpgol
aheinecke added a project to T2007: GPG OL: Cannot decrypt mails send with OpenPGP/MIME format: Duplicate.
Oct 16 2015, 2:41 PM · Duplicate, Bug Report, gpgol
aheinecke added a comment to T2007: GPG OL: Cannot decrypt mails send with OpenPGP/MIME format.

Please try the latest 1.3.0 beta version which is available from:

https://wiki.gnupg.org/GpgOL/Development/Testversions

This version has experimental read support for PGP/MIME mails.

I'm closing this issue as a duplicate of T1826 which already tracks PGP-MIME
support in gpgol.

Oct 16 2015, 2:41 PM · Duplicate, Bug Report, gpgol

Oct 13 2015

werner removed External Link on T2123: « keyserver receive failed: General error» when using HKPS.
Oct 13 2015, 6:18 AM · Bug Report, gnupg, Duplicate
werner closed T2123: « keyserver receive failed: General error» when using HKPS as Resolved.
Oct 13 2015, 6:18 AM · Bug Report, gnupg, Duplicate

Oct 12 2015

archange added a comment to T2123: « keyserver receive failed: General error» when using HKPS.

OK, sorry, I didn’t came accross bugs.gnupg.org but directly on another issue.
Will comment on the other one now.

Oct 12 2015, 11:48 AM · Bug Report, gnupg, Duplicate
archange set External Link to https://bugs.gnupg.org/gnupg/issue2050. on T2123: « keyserver receive failed: General error» when using HKPS.
Oct 12 2015, 11:48 AM · Bug Report, gnupg, Duplicate

Oct 10 2015

werner added a comment to T2123: « keyserver receive failed: General error» when using HKPS.

Duplicate of T2050

Oct 10 2015, 8:45 PM · Bug Report, gnupg, Duplicate
werner added a project to T2123: « keyserver receive failed: General error» when using HKPS: Duplicate.
Oct 10 2015, 8:45 PM · Bug Report, gnupg, Duplicate
werner added a comment to T2123: « keyserver receive failed: General error» when using HKPS.

Please read the first lines of bugs.gnupg.org. Anyway I chnaged your role and
you may now add comments to other items.

Oct 10 2015, 8:45 PM · Bug Report, gnupg, Duplicate

Sep 28 2015

gniibe added a comment to T2111: ssh-agent support broken.

For no pinentry pop-up, I think that this is same cause described in the Issue 2112.
Please try the patch in T2112

Sep 28 2015, 10:35 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
gniibe claimed T2111: ssh-agent support broken.
Sep 28 2015, 10:35 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate

Sep 24 2015

iprok added a comment to T2111: ssh-agent support broken.

I use several key of near all types: ed25519, rsa, dsa, ecdsa. All of them have
stopped working.

Sep 24 2015, 10:15 PM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
werner added a project to T2111: ssh-agent support broken: ssh.
Sep 24 2015, 10:42 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate
werner added a project to T2111: ssh-agent support broken: Duplicate.
Sep 24 2015, 10:42 AM · Debian, Bug Report, gnupg, gnupg (gpg21), ssh, Duplicate

Sep 10 2015

gniibe added a comment to T1974: libgcrypt: build fails on Gentoo/FreeBSD 10.0 or later (x86-fbsd).

Fixed in 1.6.4.

Sep 10 2015, 4:37 AM · Duplicate, Gentoo, libgcrypt, Bug Report
gniibe closed T1974: libgcrypt: build fails on Gentoo/FreeBSD 10.0 or later (x86-fbsd) as Resolved.
Sep 10 2015, 4:37 AM · Duplicate, Gentoo, libgcrypt, Bug Report
gniibe removed a project from T1974: libgcrypt: build fails on Gentoo/FreeBSD 10.0 or later (x86-fbsd): Restricted Project.
Sep 10 2015, 4:37 AM · Duplicate, Gentoo, libgcrypt, Bug Report