BTW since it was trivial to try, forcing the conifig to LINUX4 did not change anything (as expected).
The library that makes the difference consists of all the usual suspects that we've already seen/heard - it is linked from: tls_prng_dev.o tls_prng_egd.o tls_prng_file.o tls_fprint.o tls_prng_exch.o tls_stream.o tls_bio_ops.o tls_misc.o tls_dh.o tls_rsa.o tls_verify.o tls_dane.o tls_certkey.o tls_session.o tls_client.o tls_server.o tls_scache.o tls_mgr.o tls_seed.o tls_level.o tls_proxy_clnt.o tls_proxy_context_print.o tls_proxy_context_scan.o tls_proxy_client_print.o tls_proxy_client_scan.o tls_proxy_server_print.o tls_proxy_server_scan.o tls_proxy_client_misc.o The linking parameter difference is in the default toolchain options like -Wl,-Bsymbolic-functions -flto=auto but also any other that are not in the cmdline but still different defaults. Suggestions: a) - gdb debug the different behavior (debug symbols could be hard) b) to easen (a) consider - build a non debug split libpostfix-tls.so in debian and ubuntu - verify that using those two libs still makes it work/fail - now gdb debug it c) - identify all the differences in our build toolchain - Build it in Ubuntu but overriding it to how Debian would work If that resulting lib makes it work, then reduce the overrides one by one until we found what makes it work/fail d) - I'm open for other ideas :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885403 Title: posttls-finger fails to connect to private/tlsmgr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1885403/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
