D380: 963_src_assuan-socket_INADDR_LOOPBACK.patch

See T2910.

I'm closing this bug due to inactivity. Feel free to reopen it with more
information.

I have seen that but pretty pelase describe it here so that we can also work
with email.

Detail info in https://trac.macports.org/ticket/51708
OS: PPC Tiger, Mac OS X 10.4.11
The build process is automated by macport.

Please describe exactly how you build Libassuan. Compiler, OS etc, error message.

2.4.3 has been released and I assume that this works now. Feel free to re-open
if it is not the case.

Patch applied with commit c52829e for 2.4.3.
Thanks.

Had you a chance to run the suggested test?

Thanks. Changed with commit 678f606 for 2.4.3

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.)

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

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.

Hello,

please run:

  strace -f -E srcdir=tests -o fdpassing.strace tests/fdpassing

and attach fdpassing.strace to this bug report.

Duplicate of T2318

What distribution are you using? You are probably better off using their
supplied binaries, which are hopefully tested.

Version 2.4.0 has been released which replaces the used vasprintf code.

FWIW: The not too long term plan is to replace the use of vasprintf.c by
functions from libgpg-error which is used anyway.

Re-assigning to gnupg. libassuan works correctly, afaics.
When trying to send back Zack's key I had the same problem last week and
increased the limit in dirmngr (84f4c8811fc5bdd78693c4dc289389a8337cc257).
I also mentioned that in a comment to another Debian bug report.

However, their should not be a hang but a proper error diagnostic; it is on my list.

with 2.1.7, i see no hang, but i do see failure with certain large certificates,
like 0xB27B944E34884E85:

0 dkg@alice:~$ gpg2 --send 0xB27B944E34884E85
gpg: sending key 0xB27B944E34884E85 to hkps server hkps.pool.sks-keyservers.net
gpg: keyserver send failed: Too much data for IPC layer
gpg: keyserver send failed: Too much data for IPC layer
2 dkg@alice:~$

maybe the boundary is 500KiB? I don't have this problem with my own OpenPGP cert:

0 dkg@alice:~$ gpg2 --export 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9 | wc

3126   11384  481051

0 dkg@alice:~$ gpg2 --export 0xB27B944E34884E85 | wc

4310   13779  541937

0 dkg@alice:~$

Can you please downgrade to libgpg-error version 1.12 and try again?
I assume that there is a conflict between Pth and the Pthread mutexes from
libgpg-error > 1.12.

You may also consider to update to GnuPG 2.1.3 which does not use Pth anymore.

Please show us the version of your gpg-agent and its configuration
(~/.gnupg/gpg-agent.conf).
The version of gpg-agent is usually expected to be same one of gnupg, and the
invocation is:

/opt/freeware/bin/gpg-agent --daemon /bin/<SOMESHELL> # to invoke subshell
or
/opt/freeware/bin/gpg-agent --daemon # to be background

GnuPG invokes gpg-agent with --use-standard-socket-p to check if gpg-agent exists,
but it seems your GnuPG failed here waiting finish of gpg-agent.

Plerase write proper bug reports or discuss at gnupg-devel. Thanks.

Updated status to 'unread'. I'm not chatting.

Updated status to 'unread'. I'm not chatting.

Here's the updated output with line numbers.

51121==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 12 byte(s) in 1 object(s) allocated from:

#0 0x49f22b in __interceptor_malloc

/home/gpg-user/Clang-3.5/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3

#1 0x4dc25a in socketpair_connect

/home/gpg-user/gcrypt-2.0-sanitize/libassuan-2.2.0/src/assuan-pipe-connect.c:317:15

#2 0x4bdec1 in main

/home/gpg-user/gcrypt-2.0-sanitize/libassuan-2.2.0/tests/fdpassing.c:291:13

#3 0x2afdc8bddec4 in __libc_start_main

/build/buildd/eglibc-2.19/csu/libc-start.c:287

Direct leak of 7 byte(s) in 1 object(s) allocated from:

#0 0x49f22b in __interceptor_malloc

/home/gpg-user/Clang-3.5/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3

#1 0x4bc978 in xmalloc

/home/gpg-user/gcrypt-2.0-sanitize/libassuan-2.2.0/tests/./common.h:62:13

#2 0x2afdc8bddec4 in __libc_start_main

/build/buildd/eglibc-2.19/csu/libc-start.c:287

SUMMARY: AddressSanitizer: 19 byte(s) leaked in 2 allocation(s).

51122==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 3784 byte(s) in 1 object(s) allocated from:

#0 0x49f22b in __interceptor_malloc

/home/gpg-user/Clang-3.5/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3

#1 0x4bed76 in assuan_new_ext

/home/gpg-user/gcrypt-2.0-sanitize/libassuan-2.2.0/src/assuan.c:134:11

#2 0x4bde6f in main

/home/gpg-user/gcrypt-2.0-sanitize/libassuan-2.2.0/tests/fdpassing.c:287:13

#3 0x2afdc8bddec4 in __libc_start_main

/build/buildd/eglibc-2.19/csu/libc-start.c:287

Direct leak of 7 byte(s) in 1 object(s) allocated from:

#0 0x49f22b in __interceptor_malloc

/home/gpg-user/Clang-3.5/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:40:3

#1 0x4bc978 in xmalloc

/home/gpg-user/gcrypt-2.0-sanitize/libassuan-2.2.0/tests/./common.h:62:13

#2 0x2afdc8bddec4 in __libc_start_main

/build/buildd/eglibc-2.19/csu/libc-start.c:287

SUMMARY: AddressSanitizer: 3791 byte(s) leaked in 2 allocation(s).
FAIL: fdpassing

Attached is the script I am using to acceptance test the suite. It requires
Clang 3.5 (Clang 3.5 recipe was provided with Bug 1872).

Can you please lookup the description or the symbol for the ERRNO value 141 ?
find /usr/include -name errno.h | xargs grep 141
might reveal it.

What is the dscription of errno=141 ?

The user shell is ksh.

The gunpg2 memory fault error apears when i'm using libassuan version 2.1.1
(installed from perlz.org link)

I compiled gnupg-2.0.26 with libassuan-2.1.2 and the gnupg2 does not crash but
instead is just blocked waiting for something no matter what the gpg-agent is on
or off.

/opt/freeware/bin/gpg-agent &

[1] 31654070

jobs

[1] + Running /opt/freeware/bin/gpg-agent &

/opt/freeware/bin/gpg2 --gen-key

gpg (GnuPG) 2.0.26; Copyright (C) 2013 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Warning: using insecure memory!
Please select what kind of key you want:

(1) RSA and RSA (default)
(2) DSA and Elgamal
(3) DSA (sign only)
(4) RSA (sign only)

Your selection?
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048)
Requested keysize is 2048 bits
Please specify how long the key should be valid.

   0 = key does not expire
<n>  = key expires in n days
<n>w = key expires in n weeks
<n>m = key expires in n months
<n>y = key expires in n years

Key is valid for? (0)
Key does not expire at all
Is this correct? (y/N) y

GnuPG needs to construct a user ID to identify your key.

Real name: keytest01
Email address: catalin.mocanu@ing.ro
Comment: keytest with gpg-agent up
You selected this USER-ID:

    "keytest01 (keytest with gpg-agent up) <catalin.mocanu@ing.ro>"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
You need a Passphrase to protect your secret key.

[Comment: Here I'm waiting 4-5 minute and nothing is happening]

[2] + Stopped (SIGTSTP) /opt/freeware/bin/gpg2 --gen-key

jobs

[2] + Stopped (SIGTSTP) /opt/freeware/bin/gpg2 --gen-key
[1] - Running /opt/freeware/bin/gpg-agent &

Any hints?

You shell has no session management, right?

Why do you think this is a memory fault? gpg is waiting for gpg-agent to get
ready. gpg-agent is started on the fly. After a minute or so it should
actually give up and return an error if gpg-agent could not be started.

I can confirm that this is fixed with libassuan 2.1.2

Commit b6da2da9 should fix this. At least it fixes a similar bug on Solaris.

This has already been fixed in the repo:

commit e78abe490ff6806f8083b23075ae036e5894513a
Author: Werner Koch <wk@gnupg.org>
Date: Mon Jan 6 16:16:24 2014 +0100

Update libtool and autogen.sh.

--

This is the version from current libgpg-error which already has the
changes done here plus these:

  bf0d67db * Update libtool to support Android.
  dd05f379 * Fix libtool 2.4.2 to correctly detect .def files.
  6971fe55 * Update to libtool 2.4.2.