Update to upstream version '1.36'
with Debian dir a356b2e6c8aa7a93775b2d72d637cf05ccdfbd16

* configure.ac: Bump LT version to C27/A27/R0.

Signed-off-by: Werner Koch <wk@gnupg.org>

--

--

* src/gpgrt-int.h (BUFFER_BLOCK_SIZE) [W32]: Increase from 512 to 8k.
* src/w32-estream.c (READBUF_SIZE, WRITEBUF_SIZE): Increase from 4k to
8k.

Signed-off-by: Werner Koch <wk@gnupg.org>

--

GnuPG-bug-id: 4409
Signed-off-by: Werner Koch <wk@gnupg.org>

--

In particular for PIV cards ithe use of BAD_PIN sounds worong, thus
we now use dedicated codes.

Signed-off-by: Werner Koch <wk@gnupg.org>

* src/gpgrt-int.h (_gpgrt_functions_w32_pollable): Declare with extern
so that strict toolchains don't get confused.
--

GnuPG-bug-id: 4356
Signed-off-by: Werner Koch <wk@gnupg.org>

Update to upstream version '1.35'
with Debian dir 6200bcd0bd7a66efbbc46b59d0056cb38c47c15e

--

--

--

Because gpgrt-config is not anymore generated from gpgrt-config.in and
a stale (generated) gpgrt-config was hanging around in the build
directory the make distcheck target didn't caught this situation and
we accidently distributed the old gpgrt-config from the build
directory.

Signed-off-by: Werner Koch <wk@gnupg.org>

* gpgscm/scheme.c (gc_reservation_failure): Fix adding ";".
[!NDEBUG] (scheme_init_custom_alloc): Don't init seserved_lineno.

--

In some build environment, NDEBUG is defined (although it's
bad practice).  This change supports such a situation.

GnuPG-bug-id: 3959
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>

--

* configure.ac: Bump LT version to C26/A26/R0.

Signed-off-by: Werner Koch <wk@gnupg.org>

* doc/Makefile.am (errorref.txt.x):
--

Fixes-commit: fd6f64f1


Signed-off-by: Werner Koch <wk@gnupg.org>

* doc/Makefile.am (errorref.txt.x): Don't use $<.

--

Variable $< is only valid for suffix rules in BSD make.

Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>

* src/gpg-error.def.in (gogrt_abort): Correct to gpgrt_abort.

* configure.ac (LDADD_FOR_TESTS_KLUDGE): New for --disable-new-dtags.
* tests/Makefile.am (LDADD): Use LDADD_FOR_TESTS_KLUDGE.
(t_lock_LDADD, t_poll_LDADD): Use LDADD.

--

GnuPG-bug-id: 4298
Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>

* configure.ac: Check against --disable-new-dtags.

Signed-off-by: NIIBE Yutaka <gniibe@fsij.org>

--

* src/init.c (emergency_cleanup_list): New gloabl var.
(_gpgrt_add_emergency_cleanup): New.
(_gpgrt_abort): New. Repalce all calls to abort by this.  Also replace
all assert by either log_assert or a stderr output followed by a
_gpgrt_abort.
(run_emergency_cleanup): New.
* src/visibility.c (gpgrt_add_emergency_cleanup): New public API.
(gpgrt_abort): New public API.
--

Libgcrypt uses its own assert function which makes sure to terminate
the secure memory.  This is safe as log as an assert is triggered
internally in Libgcrypt.  GnuPG runs emergency cleanup handlers right
before log_fatal etc to tell Libgcrypt to terminate the secure memory.
With the move of the logging function to gpgrt in gnupg 2.3 this did
not anymore.  Thus we now provide a mechanism in gpgrt to do right
that.  Eventually Libgcrypt can also make use of this.

What this does not handle are calls to abort or failed asserts in
external libraries or in libc.  We can't do anything about it in a
library because a library may not setup signal handlers.

Signed-off-by: Werner Koch <wk@gnupg.org>