Diff of the two buildlogs: -- --- b1/build.log 2023-08-06 22:15:09.913998820 +0000 +++ b2/build.log 2023-08-06 22:17:09.889961217 +0000 @@ -1,6 +1,6 @@ I: pbuilder: network access will be disabled during build -I: Current time: Sat Sep 7 16:36:37 -12 2024 -I: pbuilder-time-stamp: 1725770197 +I: Current time: Mon Aug 7 12:15:12 +14 2023 +I: pbuilder-time-stamp: 1691360112 I: Building the build Environment I: extracting base tarball [/var/cache/pbuilder/bullseye-reproducible-base.tgz] I: copying local configuration @@ -18,8 +18,8 @@ I: copying [./stunnel4_5.56+dfsg-10.debian.tar.xz] I: Extracting source gpgv: unknown type of key resource 'trustedkeys.kbx' -gpgv: keyblock resource '/tmp/dpkg-verify-sig.ebDj5UZv/trustedkeys.kbx': General error -gpgv: Signature made Tue Apr 20 18:15:26 2021 -12 +gpgv: keyblock resource '/tmp/dpkg-verify-sig.3gRtSaUw/trustedkeys.kbx': General error +gpgv: Signature made Wed Apr 21 20:15:26 2021 +14 gpgv: using RSA key 2EE7A7A517FC124CF115C354651EEFB02527DF13 gpgv: issuer "roam@debian.org" gpgv: Can't check signature: No public key @@ -43,135 +43,166 @@ dpkg-source: info: applying 13-tls13.patch I: Not using root during the build. I: Installing the build-deps -I: user script /srv/workspace/pbuilder/2945234/tmp/hooks/D02_print_environment starting +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/D01_modify_environment starting +debug: Running on ionos1-amd64. +I: Changing host+domainname to test build reproducibility +I: Adding a custom variable just for the fun of it... +I: Changing /bin/sh to bash +'/bin/sh' -> '/bin/bash' +lrwxrwxrwx 1 root root 9 Aug 7 12:15 /bin/sh -> /bin/bash +I: Setting pbuilder2's login shell to /bin/bash +I: Setting pbuilder2's GECOS to second user,second room,second work-phone,second home-phone,second other +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/D01_modify_environment finished +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/D02_print_environment starting I: set - BUILDDIR='/build' - BUILDUSERGECOS='first user,first room,first work-phone,first home-phone,first other' - BUILDUSERNAME='pbuilder1' - BUILD_ARCH='amd64' - DEBIAN_FRONTEND='noninteractive' - DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all,-fixfilepath parallel=16 ' - DISTRIBUTION='bullseye' - HOME='/root' - HOST_ARCH='amd64' + BASH=/bin/sh + BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:globasciiranges:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath + BASH_ALIASES=() + BASH_ARGC=() + BASH_ARGV=() + BASH_CMDS=() + BASH_LINENO=([0]="12" [1]="0") + BASH_SOURCE=([0]="/tmp/hooks/D02_print_environment" [1]="/tmp/hooks/D02_print_environment") + BASH_VERSINFO=([0]="5" [1]="1" [2]="4" [3]="1" [4]="release" [5]="x86_64-pc-linux-gnu") + BASH_VERSION='5.1.4(1)-release' + BUILDDIR=/build + BUILDUSERGECOS='second user,second room,second work-phone,second home-phone,second other' + BUILDUSERNAME=pbuilder2 + BUILD_ARCH=amd64 + DEBIAN_FRONTEND=noninteractive + DEB_BUILD_OPTIONS='buildinfo=+all reproducible=+all,-fixfilepath parallel=15 ' + DIRSTACK=() + DISTRIBUTION=bullseye + EUID=0 + FUNCNAME=([0]="Echo" [1]="main") + GROUPS=() + HOME=/root + HOSTNAME=i-capture-the-hostname + HOSTTYPE=x86_64 + HOST_ARCH=amd64 IFS=' ' - INVOCATION_ID='c50557ae6b6d4a79a57c53e8e3ff01e9' - LANG='C' - LANGUAGE='en_US:en' - LC_ALL='C' - MAIL='/var/mail/root' - OPTIND='1' - PATH='/usr/sbin:/usr/bin:/sbin:/bin:/usr/games' - PBCURRENTCOMMANDLINEOPERATION='build' - PBUILDER_OPERATION='build' - PBUILDER_PKGDATADIR='/usr/share/pbuilder' - PBUILDER_PKGLIBDIR='/usr/lib/pbuilder' - PBUILDER_SYSCONFDIR='/etc' - PPID='2945234' - PS1='# ' - PS2='> ' + INVOCATION_ID=7a2e09f9c4474422969ad2ca1704e331 + LANG=C + LANGUAGE=et_EE:et + LC_ALL=C + MACHTYPE=x86_64-pc-linux-gnu + MAIL=/var/mail/root + OPTERR=1 + OPTIND=1 + OSTYPE=linux-gnu + PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path + PBCURRENTCOMMANDLINEOPERATION=build + PBUILDER_OPERATION=build + PBUILDER_PKGDATADIR=/usr/share/pbuilder + PBUILDER_PKGLIBDIR=/usr/lib/pbuilder + PBUILDER_SYSCONFDIR=/etc + PIPESTATUS=([0]="0") + POSIXLY_CORRECT=y + PPID=518328 PS4='+ ' - PWD='/' - SHELL='/bin/bash' - SHLVL='2' - SUDO_COMMAND='/usr/bin/timeout -k 18.1h 18h /usr/bin/ionice -c 3 /usr/bin/nice /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.SWBSpl3H/pbuilderrc_bqVH --distribution bullseye --hookdir /etc/pbuilder/first-build-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/bullseye-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SWBSpl3H/b1 --logfile b1/build.log stunnel4_5.56+dfsg-10.dsc' - SUDO_GID='110' - SUDO_UID='105' - SUDO_USER='jenkins' - TERM='unknown' - TZ='/usr/share/zoneinfo/Etc/GMT+12' - USER='root' - _='/usr/bin/systemd-run' - http_proxy='http://85.184.249.68:3128' + PWD=/ + SHELL=/bin/bash + SHELLOPTS=braceexpand:errexit:hashall:interactive-comments:posix + SHLVL=3 + SUDO_COMMAND='/usr/bin/timeout -k 24.1h 24h /usr/bin/ionice -c 3 /usr/bin/nice -n 11 /usr/bin/unshare --uts -- /usr/sbin/pbuilder --build --configfile /srv/reproducible-results/rbuild-debian/r-b-build.SWBSpl3H/pbuilderrc_pcgr --distribution bullseye --hookdir /etc/pbuilder/rebuild-hooks --debbuildopts -b --basetgz /var/cache/pbuilder/bullseye-reproducible-base.tgz --buildresult /srv/reproducible-results/rbuild-debian/r-b-build.SWBSpl3H/b2 --logfile b2/build.log stunnel4_5.56+dfsg-10.dsc' + SUDO_GID=110 + SUDO_UID=105 + SUDO_USER=jenkins + TERM=unknown + TZ=/usr/share/zoneinfo/Etc/GMT-14 + UID=0 + USER=root + _='I: set' + http_proxy=http://78.137.99.97:3128 I: uname -a - Linux ionos5-amd64 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux + Linux i-capture-the-hostname 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux I: ls -l /bin total 5476 - -rwxr-xr-x 1 root root 1234376 Mar 27 2022 bash - -rwxr-xr-x 3 root root 38984 Jul 20 2020 bunzip2 - -rwxr-xr-x 3 root root 38984 Jul 20 2020 bzcat - lrwxrwxrwx 1 root root 6 Jul 20 2020 bzcmp -> bzdiff - -rwxr-xr-x 1 root root 2225 Jul 20 2020 bzdiff - lrwxrwxrwx 1 root root 6 Jul 20 2020 bzegrep -> bzgrep - -rwxr-xr-x 1 root root 4877 Sep 4 2019 bzexe - lrwxrwxrwx 1 root root 6 Jul 20 2020 bzfgrep -> bzgrep - -rwxr-xr-x 1 root root 3775 Jul 20 2020 bzgrep - -rwxr-xr-x 3 root root 38984 Jul 20 2020 bzip2 - -rwxr-xr-x 1 root root 18424 Jul 20 2020 bzip2recover - lrwxrwxrwx 1 root root 6 Jul 20 2020 bzless -> bzmore - -rwxr-xr-x 1 root root 1297 Jul 20 2020 bzmore - -rwxr-xr-x 1 root root 43936 Sep 23 2020 cat - -rwxr-xr-x 1 root root 72672 Sep 23 2020 chgrp - -rwxr-xr-x 1 root root 64448 Sep 23 2020 chmod - -rwxr-xr-x 1 root root 72672 Sep 23 2020 chown - -rwxr-xr-x 1 root root 151168 Sep 23 2020 cp - -rwxr-xr-x 1 root root 125560 Dec 10 2020 dash - -rwxr-xr-x 1 root root 113664 Sep 23 2020 date - -rwxr-xr-x 1 root root 80968 Sep 23 2020 dd - -rwxr-xr-x 1 root root 93936 Sep 23 2020 df - -rwxr-xr-x 1 root root 147176 Sep 23 2020 dir - -rwxr-xr-x 1 root root 84440 Jan 20 2022 dmesg - lrwxrwxrwx 1 root root 8 Nov 6 2019 dnsdomainname -> hostname - lrwxrwxrwx 1 root root 8 Nov 6 2019 domainname -> hostname - -rwxr-xr-x 1 root root 39712 Sep 23 2020 echo - -rwxr-xr-x 1 root root 28 Jan 24 2023 egrep - -rwxr-xr-x 1 root root 39680 Sep 23 2020 false - -rwxr-xr-x 1 root root 28 Jan 24 2023 fgrep - -rwxr-xr-x 1 root root 69032 Jan 20 2022 findmnt - -rwsr-xr-x 1 root root 34896 Feb 26 2021 fusermount - -rwxr-xr-x 1 root root 203072 Jan 24 2023 grep - -rwxr-xr-x 2 root root 2346 Apr 9 2022 gunzip - -rwxr-xr-x 1 root root 6447 Apr 9 2022 gzexe - -rwxr-xr-x 1 root root 98048 Apr 9 2022 gzip - -rwxr-xr-x 1 root root 22600 Nov 6 2019 hostname - -rwxr-xr-x 1 root root 72840 Sep 23 2020 ln - -rwxr-xr-x 1 root root 56952 Feb 7 2020 login - -rwxr-xr-x 1 root root 147176 Sep 23 2020 ls - -rwxr-xr-x 1 root root 149736 Jan 20 2022 lsblk - -rwxr-xr-x 1 root root 85184 Sep 23 2020 mkdir - -rwxr-xr-x 1 root root 76896 Sep 23 2020 mknod - -rwxr-xr-x 1 root root 48064 Sep 23 2020 mktemp - -rwxr-xr-x 1 root root 59632 Jan 20 2022 more - -rwsr-xr-x 1 root root 55528 Jan 20 2022 mount - -rwxr-xr-x 1 root root 18664 Jan 20 2022 mountpoint - -rwxr-xr-x 1 root root 147080 Sep 23 2020 mv - lrwxrwxrwx 1 root root 8 Nov 6 2019 nisdomainname -> hostname - lrwxrwxrwx 1 root root 14 Dec 16 2021 pidof -> /sbin/killall5 - -rwxr-xr-x 1 root root 43872 Sep 23 2020 pwd - lrwxrwxrwx 1 root root 4 Mar 27 2022 rbash -> bash - -rwxr-xr-x 1 root root 52032 Sep 23 2020 readlink - -rwxr-xr-x 1 root root 72704 Sep 23 2020 rm - -rwxr-xr-x 1 root root 52032 Sep 23 2020 rmdir - -rwxr-xr-x 1 root root 27472 Sep 27 2020 run-parts - -rwxr-xr-x 1 root root 122224 Dec 22 2018 sed - lrwxrwxrwx 1 root root 4 Aug 8 03:47 sh -> dash - -rwxr-xr-x 1 root root 43808 Sep 23 2020 sleep - -rwxr-xr-x 1 root root 84928 Sep 23 2020 stty - -rwsr-xr-x 1 root root 71912 Jan 20 2022 su - -rwxr-xr-x 1 root root 39744 Sep 23 2020 sync - -rwxr-xr-x 1 root root 531928 Feb 16 2021 tar - -rwxr-xr-x 1 root root 14456 Sep 27 2020 tempfile - -rwxr-xr-x 1 root root 101408 Sep 23 2020 touch - -rwxr-xr-x 1 root root 39680 Sep 23 2020 true - -rwxr-xr-x 1 root root 14328 Feb 26 2021 ulockmgr_server - -rwsr-xr-x 1 root root 35040 Jan 20 2022 umount - -rwxr-xr-x 1 root root 39744 Sep 23 2020 uname - -rwxr-xr-x 2 root root 2346 Apr 9 2022 uncompress - -rwxr-xr-x 1 root root 147176 Sep 23 2020 vdir - -rwxr-xr-x 1 root root 63744 Jan 20 2022 wdctl - lrwxrwxrwx 1 root root 8 Nov 6 2019 ypdomainname -> hostname - -rwxr-xr-x 1 root root 1984 Apr 9 2022 zcat - -rwxr-xr-x 1 root root 1678 Apr 9 2022 zcmp - -rwxr-xr-x 1 root root 5898 Apr 9 2022 zdiff - -rwxr-xr-x 1 root root 29 Apr 9 2022 zegrep - -rwxr-xr-x 1 root root 29 Apr 9 2022 zfgrep - -rwxr-xr-x 1 root root 2081 Apr 9 2022 zforce - -rwxr-xr-x 1 root root 8049 Apr 9 2022 zgrep - -rwxr-xr-x 1 root root 2206 Apr 9 2022 zless - -rwxr-xr-x 1 root root 1842 Apr 9 2022 zmore - -rwxr-xr-x 1 root root 4577 Apr 9 2022 znew -I: user script /srv/workspace/pbuilder/2945234/tmp/hooks/D02_print_environment finished + -rwxr-xr-x 1 root root 1234376 Mar 28 2022 bash + -rwxr-xr-x 3 root root 38984 Jul 21 2020 bunzip2 + -rwxr-xr-x 3 root root 38984 Jul 21 2020 bzcat + lrwxrwxrwx 1 root root 6 Jul 21 2020 bzcmp -> bzdiff + -rwxr-xr-x 1 root root 2225 Jul 21 2020 bzdiff + lrwxrwxrwx 1 root root 6 Jul 21 2020 bzegrep -> bzgrep + -rwxr-xr-x 1 root root 4877 Sep 5 2019 bzexe + lrwxrwxrwx 1 root root 6 Jul 21 2020 bzfgrep -> bzgrep + -rwxr-xr-x 1 root root 3775 Jul 21 2020 bzgrep + -rwxr-xr-x 3 root root 38984 Jul 21 2020 bzip2 + -rwxr-xr-x 1 root root 18424 Jul 21 2020 bzip2recover + lrwxrwxrwx 1 root root 6 Jul 21 2020 bzless -> bzmore + -rwxr-xr-x 1 root root 1297 Jul 21 2020 bzmore + -rwxr-xr-x 1 root root 43936 Sep 24 2020 cat + -rwxr-xr-x 1 root root 72672 Sep 24 2020 chgrp + -rwxr-xr-x 1 root root 64448 Sep 24 2020 chmod + -rwxr-xr-x 1 root root 72672 Sep 24 2020 chown + -rwxr-xr-x 1 root root 151168 Sep 24 2020 cp + -rwxr-xr-x 1 root root 125560 Dec 11 2020 dash + -rwxr-xr-x 1 root root 113664 Sep 24 2020 date + -rwxr-xr-x 1 root root 80968 Sep 24 2020 dd + -rwxr-xr-x 1 root root 93936 Sep 24 2020 df + -rwxr-xr-x 1 root root 147176 Sep 24 2020 dir + -rwxr-xr-x 1 root root 84440 Jan 21 2022 dmesg + lrwxrwxrwx 1 root root 8 Nov 8 2019 dnsdomainname -> hostname + lrwxrwxrwx 1 root root 8 Nov 8 2019 domainname -> hostname + -rwxr-xr-x 1 root root 39712 Sep 24 2020 echo + -rwxr-xr-x 1 root root 28 Jan 25 2023 egrep + -rwxr-xr-x 1 root root 39680 Sep 24 2020 false + -rwxr-xr-x 1 root root 28 Jan 25 2023 fgrep + -rwxr-xr-x 1 root root 69032 Jan 21 2022 findmnt + -rwsr-xr-x 1 root root 34896 Feb 27 2021 fusermount + -rwxr-xr-x 1 root root 203072 Jan 25 2023 grep + -rwxr-xr-x 2 root root 2346 Apr 10 2022 gunzip + -rwxr-xr-x 1 root root 6447 Apr 10 2022 gzexe + -rwxr-xr-x 1 root root 98048 Apr 10 2022 gzip + -rwxr-xr-x 1 root root 22600 Nov 8 2019 hostname + -rwxr-xr-x 1 root root 72840 Sep 24 2020 ln + -rwxr-xr-x 1 root root 56952 Feb 8 2020 login + -rwxr-xr-x 1 root root 147176 Sep 24 2020 ls + -rwxr-xr-x 1 root root 149736 Jan 21 2022 lsblk + -rwxr-xr-x 1 root root 85184 Sep 24 2020 mkdir + -rwxr-xr-x 1 root root 76896 Sep 24 2020 mknod + -rwxr-xr-x 1 root root 48064 Sep 24 2020 mktemp + -rwxr-xr-x 1 root root 59632 Jan 21 2022 more + -rwsr-xr-x 1 root root 55528 Jan 21 2022 mount + -rwxr-xr-x 1 root root 18664 Jan 21 2022 mountpoint + -rwxr-xr-x 1 root root 147080 Sep 24 2020 mv + lrwxrwxrwx 1 root root 8 Nov 8 2019 nisdomainname -> hostname + lrwxrwxrwx 1 root root 14 Dec 17 2021 pidof -> /sbin/killall5 + -rwxr-xr-x 1 root root 43872 Sep 24 2020 pwd + lrwxrwxrwx 1 root root 4 Mar 28 2022 rbash -> bash + -rwxr-xr-x 1 root root 52032 Sep 24 2020 readlink + -rwxr-xr-x 1 root root 72704 Sep 24 2020 rm + -rwxr-xr-x 1 root root 52032 Sep 24 2020 rmdir + -rwxr-xr-x 1 root root 27472 Sep 28 2020 run-parts + -rwxr-xr-x 1 root root 122224 Dec 23 2018 sed + lrwxrwxrwx 1 root root 9 Aug 7 12:15 sh -> /bin/bash + -rwxr-xr-x 1 root root 43808 Sep 24 2020 sleep + -rwxr-xr-x 1 root root 84928 Sep 24 2020 stty + -rwsr-xr-x 1 root root 71912 Jan 21 2022 su + -rwxr-xr-x 1 root root 39744 Sep 24 2020 sync + -rwxr-xr-x 1 root root 531928 Feb 17 2021 tar + -rwxr-xr-x 1 root root 14456 Sep 28 2020 tempfile + -rwxr-xr-x 1 root root 101408 Sep 24 2020 touch + -rwxr-xr-x 1 root root 39680 Sep 24 2020 true + -rwxr-xr-x 1 root root 14328 Feb 27 2021 ulockmgr_server + -rwsr-xr-x 1 root root 35040 Jan 21 2022 umount + -rwxr-xr-x 1 root root 39744 Sep 24 2020 uname + -rwxr-xr-x 2 root root 2346 Apr 10 2022 uncompress + -rwxr-xr-x 1 root root 147176 Sep 24 2020 vdir + -rwxr-xr-x 1 root root 63744 Jan 21 2022 wdctl + lrwxrwxrwx 1 root root 8 Nov 8 2019 ypdomainname -> hostname + -rwxr-xr-x 1 root root 1984 Apr 10 2022 zcat + -rwxr-xr-x 1 root root 1678 Apr 10 2022 zcmp + -rwxr-xr-x 1 root root 5898 Apr 10 2022 zdiff + -rwxr-xr-x 1 root root 29 Apr 10 2022 zegrep + -rwxr-xr-x 1 root root 29 Apr 10 2022 zfgrep + -rwxr-xr-x 1 root root 2081 Apr 10 2022 zforce + -rwxr-xr-x 1 root root 8049 Apr 10 2022 zgrep + -rwxr-xr-x 1 root root 2206 Apr 10 2022 zless + -rwxr-xr-x 1 root root 1842 Apr 10 2022 zmore + -rwxr-xr-x 1 root root 4577 Apr 10 2022 znew +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/D02_print_environment finished -> Attempting to satisfy build-dependencies -> Creating pbuilder-satisfydepends-dummy package Package: pbuilder-satisfydepends-dummy @@ -294,7 +325,7 @@ Get: 55 http://deb.debian.org/debian bullseye/main amd64 net-tools amd64 1.60+git20181103.0eebece-1 [250 kB] Get: 56 http://deb.debian.org/debian bullseye/main amd64 netcat-openbsd amd64 1.217-3 [41.1 kB] Get: 57 http://deb.debian.org/debian bullseye/main amd64 openssl amd64 1.1.1n-0+deb11u4 [853 kB] -Fetched 25.1 MB in 0s (61.3 MB/s) +Fetched 25.1 MB in 1s (30.4 MB/s) debconf: delaying package configuration, since apt-utils is not installed Selecting previously unselected package bsdextrautils. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 19707 files and directories currently installed.) @@ -539,7 +570,11 @@ Building tag database... -> Finished parsing the build-deps I: Building the package -I: Running cd /build/stunnel4-5.56+dfsg/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games" HOME="/nonexistent/first-build" dpkg-genchanges -S > ../stunnel4_5.56+dfsg-10_source.changes +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/A99_set_merged_usr starting +Not re-configuring usrmerge for bullseye +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/A99_set_merged_usr finished +hostname: Name or service not known +I: Running cd /build/stunnel4-5.56+dfsg/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-buildpackage -us -uc -b && env PATH="/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/i/capture/the/path" HOME="/nonexistent/second-build" dpkg-genchanges -S > ../stunnel4_5.56+dfsg-10_source.changes dpkg-buildpackage: info: source package stunnel4 dpkg-buildpackage: info: source version 3:5.56+dfsg-10 dpkg-buildpackage: info: source distribution unstable @@ -839,7 +874,7 @@ touch src/dhparam.c make[1]: Leaving directory '/build/stunnel4-5.56+dfsg' dh_auto_build - make -j16 + make -j15 make[1]: Entering directory '/build/stunnel4-5.56+dfsg' Making all in src make[2]: Entering directory '/build/stunnel4-5.56+dfsg/src' @@ -865,13 +900,13 @@ gcc -DHAVE_CONFIG_H -I. -I/usr/kerberos/include -I/usr/include -DLIBDIR='"/usr/lib/x86_64-linux-gnu/stunnel"' -DCONFDIR='"/etc/stunnel"' -DPIDFILE='"/var/run/stunnel4.pid"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -c -o stunnel-pty.o `test -f 'pty.c' || echo './'`pty.c gcc -DHAVE_CONFIG_H -I. -I/usr/kerberos/include -I/usr/include -DLIBDIR='"/usr/lib/x86_64-linux-gnu/stunnel"' -DCONFDIR='"/etc/stunnel"' -DPIDFILE='"/var/run/stunnel4.pid"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -c -o stunnel-libwrap.o `test -f 'libwrap.c' || echo './'`libwrap.c gcc -DHAVE_CONFIG_H -I. -I/usr/kerberos/include -I/usr/include -DLIBDIR='"/usr/lib/x86_64-linux-gnu/stunnel"' -DCONFDIR='"/etc/stunnel"' -DPIDFILE='"/var/run/stunnel4.pid"' -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -c -o stunnel-ui_unix.o `test -f 'ui_unix.c' || echo './'`ui_unix.c -/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -c -o env.lo env.c +/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -c -o env.lo env.c sed -e 's|@bindir[@]|/usr/bin|g' './stunnel3.in' >stunnel3 libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fstack-protector -D_FORTIFY_SOURCE=2 -c env.c -fPIC -DPIC -o .libs/env.o -/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -avoid-version -Wl,-z,relro -Wl,-z,now -fPIE -pie -Wl,-z,noexecstack -o libstunnel.la -rpath /usr/lib/x86_64-linux-gnu/stunnel env.lo -lsystemd -ldl -lutil -lnsl -lwrap +/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -avoid-version -Wl,-z,relro -Wl,-z,now -fPIE -pie -Wl,-z,noexecstack -o libstunnel.la -rpath /usr/lib/x86_64-linux-gnu/stunnel env.lo -lsystemd -ldl -lutil -lnsl -lwrap libtool: link: gcc -shared -fPIC -DPIC .libs/env.o -lsystemd -ldl -lutil -lnsl -lwrap -g -O2 -fstack-protector-strong -pthread -fstack-protector -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z -Wl,noexecstack -pthread -Wl,-soname -Wl,libstunnel.so -o .libs/libstunnel.so libtool: link: ( cd ".libs" && rm -f "libstunnel.la" && ln -s "../libstunnel.la" "libstunnel.la" ) -/bin/bash ../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -L/usr/lib64 -L/usr/lib -lssl -lcrypto -Wl,-z,relro -Wl,-z,now -fPIE -pie -Wl,-z,noexecstack -o stunnel stunnel-tls.o stunnel-str.o stunnel-file.o stunnel-client.o stunnel-log.o stunnel-options.o stunnel-protocol.o stunnel-network.o stunnel-resolver.o stunnel-ssl.o stunnel-ctx.o stunnel-verify.o stunnel-sthreads.o stunnel-fd.o stunnel-dhparam.o stunnel-cron.o stunnel-stunnel.o stunnel-pty.o stunnel-libwrap.o stunnel-ui_unix.o -lsystemd -ldl -lutil -lnsl -lwrap +/bin/sh ../libtool --tag=CC --mode=link gcc -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -L/usr/lib64 -L/usr/lib -lssl -lcrypto -Wl,-z,relro -Wl,-z,now -fPIE -pie -Wl,-z,noexecstack -o stunnel stunnel-tls.o stunnel-str.o stunnel-file.o stunnel-client.o stunnel-log.o stunnel-options.o stunnel-protocol.o stunnel-network.o stunnel-resolver.o stunnel-ssl.o stunnel-ctx.o stunnel-verify.o stunnel-sthreads.o stunnel-fd.o stunnel-dhparam.o stunnel-cron.o stunnel-stunnel.o stunnel-pty.o stunnel-libwrap.o stunnel-ui_unix.o -lsystemd -ldl -lutil -lnsl -lwrap libtool: link: gcc -g -O2 -fdebug-prefix-map=/build/stunnel4-5.56+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread -Wextra -Wpedantic -Wformat=2 -Wconversion -Wno-long-long -Wno-deprecated-declarations -fPIE -fstack-protector -D_FORTIFY_SOURCE=2 -Wl,-z -Wl,relro -Wl,-z -Wl,now -fPIE -pie -Wl,-z -Wl,noexecstack -o stunnel stunnel-tls.o stunnel-str.o stunnel-file.o stunnel-client.o stunnel-log.o stunnel-options.o stunnel-protocol.o stunnel-network.o stunnel-resolver.o stunnel-ssl.o stunnel-ctx.o stunnel-verify.o stunnel-sthreads.o stunnel-fd.o stunnel-dhparam.o stunnel-cron.o stunnel-stunnel.o stunnel-pty.o stunnel-libwrap.o stunnel-ui_unix.o -L/usr/lib64 -L/usr/lib -lssl -lcrypto -lsystemd -ldl -lutil -lnsl -lwrap -pthread make[3]: Leaving directory '/build/stunnel4-5.56+dfsg/src' make[2]: Leaving directory '/build/stunnel4-5.56+dfsg/src' @@ -909,24 +944,24 @@ Using AnyEvent model $VAR1 = 'AnyEvent::Impl::EV'; Found the certificate at debian/tests/certs/certificate.pem and the private key at debian/tests/certs/key.pem -Using the /tmp/bYp2lb6tnR temporary directory +Using the /tmp/l5SUJBruap temporary directory About to get the stunnel version information Got stunnel version 5.56 Listening for cleartext connections on 127.0.0.1:6502 -Connected to 127.0.0.1:6502, local 127.0.0.1:34574 -Accepted a connection from 127.0.0.1:34574 -Got a local connection id 127.0.0.1:34574 +Connected to 127.0.0.1:6502, local 127.0.0.1:59454 +Accepted a connection from 127.0.0.1:59454 +Got a local connection id 127.0.0.1:59454 Waiting for the server to acknowledge a completed client connection -Got an eof from 127.0.0.1:34574, all seems well +Got an eof from 127.0.0.1:59454, all seems well Waiting for the client connection itself to report completion Looks like we are done with the test cleartext connection! Got listening port 8086 for the stunnel server Let us hope this was enough to get stunnel to listen there... -Created the stunnel config file /tmp/bYp2lb6tnR/stunnel.conf: +Created the stunnel config file /tmp/l5SUJBruap/stunnel.conf: ====== -pid = /tmp/bYp2lb6tnR/stunnel.pid +pid = /tmp/l5SUJBruap/stunnel.pid foreground = yes -output = /tmp/bYp2lb6tnR/stunnel.log +output = /tmp/l5SUJBruap/stunnel.log cert = debian/tests/certs/certificate.pem key = debian/tests/certs/key.pem @@ -935,149 +970,149 @@ accept = 127.0.0.1:8086 connect = 127.0.0.1:6502 ====== -2024.09.07 16:37:26 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform -2024.09.07 16:37:26 LOG5[ui]: Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 -2024.09.07 16:37:26 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP -2024.09.07 16:37:26 LOG5[ui]: Reading configuration from file /tmp/bYp2lb6tnR/stunnel.conf -2024.09.07 16:37:26 LOG5[ui]: UTF-8 byte order mark not detected -2024.09.07 16:37:26 LOG5[ui]: FIPS mode disabled -2024.09.07 16:37:26 LOG4[ui]: Insecure file permissions on debian/tests/certs/key.pem -2024.09.07 16:37:26 LOG5[ui]: Configuration successful -2024.09.07 16:37:26 LOG5[0]: Service [test] accepted connection from 127.0.0.1:35714 -2024.09.07 16:37:26 LOG5[0]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:26 LOG5[0]: Service [test] connected remote server from 127.0.0.1:34586 -2024.09.07 16:37:26 LOG5[0]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:26 LOG5[1]: Service [test] accepted connection from 127.0.0.1:35716 -2024.09.07 16:37:26 LOG5[1]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:26 LOG5[1]: Service [test] connected remote server from 127.0.0.1:34598 -2024.09.07 16:37:26 LOG5[1]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:26 LOG5[2]: Service [test] accepted connection from 127.0.0.1:35720 -2024.09.07 16:37:26 LOG5[2]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:26 LOG5[2]: Service [test] connected remote server from 127.0.0.1:34602 -2024.09.07 16:37:26 LOG5[2]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:26 LOG5[3]: Service [test] accepted connection from 127.0.0.1:35736 -2024.09.07 16:37:26 LOG5[3]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:26 LOG5[3]: Service [test] connected remote server from 127.0.0.1:34608 -2024.09.07 16:37:26 LOG5[3]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:26 LOG5[4]: Service [test] accepted connection from 127.0.0.1:35750 -2024.09.07 16:37:26 LOG5[4]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:26 LOG5[4]: Service [test] connected remote server from 127.0.0.1:34622 -2024.09.07 16:37:26 LOG5[4]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:27 LOG5[5]: Service [test] accepted connection from 127.0.0.1:35760 -2024.09.07 16:37:27 LOG5[5]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:27 LOG5[5]: Service [test] connected remote server from 127.0.0.1:34630 -2024.09.07 16:37:27 LOG5[5]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:27 LOG5[6]: Service [test] accepted connection from 127.0.0.1:35776 -2024.09.07 16:37:27 LOG5[6]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:27 LOG5[6]: Service [test] connected remote server from 127.0.0.1:34632 -2024.09.07 16:37:27 LOG5[6]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:27 LOG5[7]: Service [test] accepted connection from 127.0.0.1:35778 -2024.09.07 16:37:27 LOG5[7]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:27 LOG5[7]: Service [test] connected remote server from 127.0.0.1:34634 -2024.09.07 16:37:27 LOG5[7]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:27 LOG5[8]: Service [test] accepted connection from 127.0.0.1:35780 -2024.09.07 16:37:27 LOG5[8]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:27 LOG5[8]: Service [test] connected remote server from 127.0.0.1:34636 -2024.09.07 16:37:27 LOG5[8]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:27 LOG5[9]: Service [test] accepted connection from 127.0.0.1:35790 -2024.09.07 16:37:27 LOG5[9]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:27 LOG5[9]: Service [test] connected remote server from 127.0.0.1:34650 -2024.09.07 16:37:27 LOG5[9]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:27 LOG5[ui]: Terminated -2024.09.07 16:37:27 LOG5[ui]: Terminating 1 service thread(s) -2024.09.07 16:37:27 LOG5[ui]: Service threads terminated -Started the stunnel server, pid 2957848 +2023.08.07 12:16:17 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform +2023.08.07 12:16:17 LOG5[ui]: Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 +2023.08.07 12:16:17 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP +2023.08.07 12:16:17 LOG5[ui]: Reading configuration from file /tmp/l5SUJBruap/stunnel.conf +2023.08.07 12:16:17 LOG5[ui]: UTF-8 byte order mark not detected +2023.08.07 12:16:17 LOG5[ui]: FIPS mode disabled +2023.08.07 12:16:17 LOG4[ui]: Insecure file permissions on debian/tests/certs/key.pem +2023.08.07 12:16:17 LOG5[ui]: Configuration successful +2023.08.07 12:16:17 LOG5[0]: Service [test] accepted connection from 127.0.0.1:58796 +2023.08.07 12:16:17 LOG5[0]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:17 LOG5[0]: Service [test] connected remote server from 127.0.0.1:59460 +2023.08.07 12:16:17 LOG5[0]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:17 LOG5[1]: Service [test] accepted connection from 127.0.0.1:58812 +2023.08.07 12:16:17 LOG5[1]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:17 LOG5[1]: Service [test] connected remote server from 127.0.0.1:59468 +2023.08.07 12:16:17 LOG5[1]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:17 LOG5[2]: Service [test] accepted connection from 127.0.0.1:58818 +2023.08.07 12:16:17 LOG5[2]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:17 LOG5[2]: Service [test] connected remote server from 127.0.0.1:59474 +2023.08.07 12:16:17 LOG5[2]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:17 LOG5[3]: Service [test] accepted connection from 127.0.0.1:58822 +2023.08.07 12:16:17 LOG5[3]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:17 LOG5[3]: Service [test] connected remote server from 127.0.0.1:59486 +2023.08.07 12:16:17 LOG5[3]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:17 LOG5[4]: Service [test] accepted connection from 127.0.0.1:58834 +2023.08.07 12:16:18 LOG5[4]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:18 LOG5[4]: Service [test] connected remote server from 127.0.0.1:49340 +2023.08.07 12:16:18 LOG5[4]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:18 LOG5[5]: Service [test] accepted connection from 127.0.0.1:52858 +2023.08.07 12:16:18 LOG5[5]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:18 LOG5[5]: Service [test] connected remote server from 127.0.0.1:49350 +2023.08.07 12:16:18 LOG5[5]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:18 LOG5[6]: Service [test] accepted connection from 127.0.0.1:52862 +2023.08.07 12:16:18 LOG5[6]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:18 LOG5[6]: Service [test] connected remote server from 127.0.0.1:49354 +2023.08.07 12:16:18 LOG5[6]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:18 LOG5[7]: Service [test] accepted connection from 127.0.0.1:52864 +2023.08.07 12:16:18 LOG5[7]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:18 LOG5[7]: Service [test] connected remote server from 127.0.0.1:49366 +2023.08.07 12:16:18 LOG5[7]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:18 LOG5[8]: Service [test] accepted connection from 127.0.0.1:52872 +2023.08.07 12:16:18 LOG5[8]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:18 LOG5[8]: Service [test] connected remote server from 127.0.0.1:49372 +2023.08.07 12:16:18 LOG5[8]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:18 LOG5[9]: Service [test] accepted connection from 127.0.0.1:52874 +2023.08.07 12:16:18 LOG5[9]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:18 LOG5[9]: Service [test] connected remote server from 127.0.0.1:49382 +2023.08.07 12:16:18 LOG5[9]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:18 LOG5[ui]: Terminated +2023.08.07 12:16:18 LOG5[ui]: Terminating 1 service thread(s) +2023.08.07 12:16:18 LOG5[ui]: Service threads terminated +Started the stunnel server, pid 534857 Trying a connection through stunnel, iteration 1 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35714 +Registered a client connection as 127.0.0.1:58796 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34586 -Got an eof from 127.0.0.1:34586, all seems well -The server reported a completed connection: 127.0.0.1:34586 +Accepted a connection from 127.0.0.1:59460 +Got an eof from 127.0.0.1:59460, all seems well +The server reported a completed connection: 127.0.0.1:59460 The stunnel connection seems to have gone through for iteration 1 Trying a connection through stunnel, iteration 2 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35716 +Registered a client connection as 127.0.0.1:58812 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34598 -Got an eof from 127.0.0.1:34598, all seems well -The server reported a completed connection: 127.0.0.1:34598 +Accepted a connection from 127.0.0.1:59468 +Got an eof from 127.0.0.1:59468, all seems well +The server reported a completed connection: 127.0.0.1:59468 The stunnel connection seems to have gone through for iteration 2 Trying a connection through stunnel, iteration 3 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35720 +Registered a client connection as 127.0.0.1:58818 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34602 -Got an eof from 127.0.0.1:34602, all seems well -The server reported a completed connection: 127.0.0.1:34602 +Accepted a connection from 127.0.0.1:59474 +Got an eof from 127.0.0.1:59474, all seems well +The server reported a completed connection: 127.0.0.1:59474 The stunnel connection seems to have gone through for iteration 3 Trying a connection through stunnel, iteration 4 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35736 +Registered a client connection as 127.0.0.1:58822 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34608 -Got an eof from 127.0.0.1:34608, all seems well -The server reported a completed connection: 127.0.0.1:34608 +Accepted a connection from 127.0.0.1:59486 +Got an eof from 127.0.0.1:59486, all seems well +The server reported a completed connection: 127.0.0.1:59486 The stunnel connection seems to have gone through for iteration 4 Trying a connection through stunnel, iteration 5 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35750 +Registered a client connection as 127.0.0.1:58834 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34622 -Got an eof from 127.0.0.1:34622, all seems well -The server reported a completed connection: 127.0.0.1:34622 +Accepted a connection from 127.0.0.1:49340 +Got an eof from 127.0.0.1:49340, all seems well +The server reported a completed connection: 127.0.0.1:49340 The stunnel connection seems to have gone through for iteration 5 Trying a connection through stunnel, iteration 6 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35760 +Registered a client connection as 127.0.0.1:52858 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34630 -Got an eof from 127.0.0.1:34630, all seems well -The server reported a completed connection: 127.0.0.1:34630 +Accepted a connection from 127.0.0.1:49350 +Got an eof from 127.0.0.1:49350, all seems well +The server reported a completed connection: 127.0.0.1:49350 The stunnel connection seems to have gone through for iteration 6 Trying a connection through stunnel, iteration 7 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35776 +Registered a client connection as 127.0.0.1:52862 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34632 -Got an eof from 127.0.0.1:34632, all seems well -The server reported a completed connection: 127.0.0.1:34632 +Accepted a connection from 127.0.0.1:49354 +Got an eof from 127.0.0.1:49354, all seems well +The server reported a completed connection: 127.0.0.1:49354 The stunnel connection seems to have gone through for iteration 7 Trying a connection through stunnel, iteration 8 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35778 +Registered a client connection as 127.0.0.1:52864 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34634 -Got an eof from 127.0.0.1:34634, all seems well -The server reported a completed connection: 127.0.0.1:34634 +Accepted a connection from 127.0.0.1:49366 +Got an eof from 127.0.0.1:49366, all seems well +The server reported a completed connection: 127.0.0.1:49366 The stunnel connection seems to have gone through for iteration 8 Trying a connection through stunnel, iteration 9 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35780 +Registered a client connection as 127.0.0.1:52872 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34636 -Got an eof from 127.0.0.1:34636, all seems well -The server reported a completed connection: 127.0.0.1:34636 +Accepted a connection from 127.0.0.1:49372 +Got an eof from 127.0.0.1:49372, all seems well +The server reported a completed connection: 127.0.0.1:49372 The stunnel connection seems to have gone through for iteration 9 Trying a connection through stunnel, iteration 10 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35790 +Registered a client connection as 127.0.0.1:52874 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34650 -Got an eof from 127.0.0.1:34650, all seems well -The server reported a completed connection: 127.0.0.1:34650 +Accepted a connection from 127.0.0.1:49382 +Got an eof from 127.0.0.1:49382, all seems well +The server reported a completed connection: 127.0.0.1:49382 The stunnel connection seems to have gone through for iteration 10 -Trying to stop stunnel at pid 2957848 +Trying to stop stunnel at pid 534857 The stunnel process terminated successfully Checking for leftover children No child processes left over @@ -1088,24 +1123,24 @@ Using AnyEvent model $VAR1 = 'AnyEvent::Impl::Event'; Found the certificate at debian/tests/certs/certificate.pem and the private key at debian/tests/certs/key.pem -Using the /tmp/gpQ0worSRI temporary directory +Using the /tmp/p4COnnoxvF temporary directory About to get the stunnel version information Got stunnel version 5.56 Listening for cleartext connections on 127.0.0.1:6502 -Connected to 127.0.0.1:6502, local 127.0.0.1:34658 -Got a local connection id 127.0.0.1:34658 +Connected to 127.0.0.1:6502, local 127.0.0.1:49390 +Got a local connection id 127.0.0.1:49390 Waiting for the server to acknowledge a completed client connection -Accepted a connection from 127.0.0.1:34658 -Got an eof from 127.0.0.1:34658, all seems well +Accepted a connection from 127.0.0.1:49390 +Got an eof from 127.0.0.1:49390, all seems well Waiting for the client connection itself to report completion Looks like we are done with the test cleartext connection! Got listening port 8086 for the stunnel server Let us hope this was enough to get stunnel to listen there... -Created the stunnel config file /tmp/gpQ0worSRI/stunnel.conf: +Created the stunnel config file /tmp/p4COnnoxvF/stunnel.conf: ====== -pid = /tmp/gpQ0worSRI/stunnel.pid +pid = /tmp/p4COnnoxvF/stunnel.pid foreground = yes -output = /tmp/gpQ0worSRI/stunnel.log +output = /tmp/p4COnnoxvF/stunnel.log cert = debian/tests/certs/certificate.pem key = debian/tests/certs/key.pem @@ -1114,149 +1149,149 @@ accept = 127.0.0.1:8086 connect = 127.0.0.1:6502 ====== -2024.09.07 16:37:27 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform -2024.09.07 16:37:27 LOG5[ui]: Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 -2024.09.07 16:37:27 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP -2024.09.07 16:37:27 LOG5[ui]: Reading configuration from file /tmp/gpQ0worSRI/stunnel.conf -2024.09.07 16:37:27 LOG5[ui]: UTF-8 byte order mark not detected -2024.09.07 16:37:27 LOG5[ui]: FIPS mode disabled -2024.09.07 16:37:27 LOG4[ui]: Insecure file permissions on debian/tests/certs/key.pem -2024.09.07 16:37:27 LOG5[ui]: Configuration successful -2024.09.07 16:37:28 LOG5[0]: Service [test] accepted connection from 127.0.0.1:35802 -2024.09.07 16:37:28 LOG5[0]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[0]: Service [test] connected remote server from 127.0.0.1:34672 -2024.09.07 16:37:28 LOG5[0]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[1]: Service [test] accepted connection from 127.0.0.1:35804 -2024.09.07 16:37:28 LOG5[1]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[1]: Service [test] connected remote server from 127.0.0.1:34686 -2024.09.07 16:37:28 LOG5[1]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[2]: Service [test] accepted connection from 127.0.0.1:35810 -2024.09.07 16:37:28 LOG5[2]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[2]: Service [test] connected remote server from 127.0.0.1:34688 -2024.09.07 16:37:28 LOG5[2]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[3]: Service [test] accepted connection from 127.0.0.1:35812 -2024.09.07 16:37:28 LOG5[3]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[3]: Service [test] connected remote server from 127.0.0.1:34694 -2024.09.07 16:37:28 LOG5[3]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[4]: Service [test] accepted connection from 127.0.0.1:35820 -2024.09.07 16:37:28 LOG5[4]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[4]: Service [test] connected remote server from 127.0.0.1:34704 -2024.09.07 16:37:28 LOG5[4]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[5]: Service [test] accepted connection from 127.0.0.1:35826 -2024.09.07 16:37:28 LOG5[5]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[5]: Service [test] connected remote server from 127.0.0.1:34712 -2024.09.07 16:37:28 LOG5[5]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[6]: Service [test] accepted connection from 127.0.0.1:35840 -2024.09.07 16:37:28 LOG5[6]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[6]: Service [test] connected remote server from 127.0.0.1:34714 -2024.09.07 16:37:28 LOG5[6]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:28 LOG5[7]: Service [test] accepted connection from 127.0.0.1:35852 -2024.09.07 16:37:28 LOG5[7]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:28 LOG5[7]: Service [test] connected remote server from 127.0.0.1:34720 -2024.09.07 16:37:28 LOG5[7]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:29 LOG5[8]: Service [test] accepted connection from 127.0.0.1:35854 -2024.09.07 16:37:29 LOG5[8]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:29 LOG5[8]: Service [test] connected remote server from 127.0.0.1:34730 -2024.09.07 16:37:29 LOG5[8]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:29 LOG5[9]: Service [test] accepted connection from 127.0.0.1:35858 -2024.09.07 16:37:29 LOG5[9]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:29 LOG5[9]: Service [test] connected remote server from 127.0.0.1:34736 -2024.09.07 16:37:29 LOG5[9]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:29 LOG5[ui]: Terminated -2024.09.07 16:37:29 LOG5[ui]: Terminating 1 service thread(s) -2024.09.07 16:37:29 LOG5[ui]: Service threads terminated -Started the stunnel server, pid 2958251 +2023.08.07 12:16:19 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform +2023.08.07 12:16:19 LOG5[ui]: Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 +2023.08.07 12:16:19 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP +2023.08.07 12:16:19 LOG5[ui]: Reading configuration from file /tmp/p4COnnoxvF/stunnel.conf +2023.08.07 12:16:19 LOG5[ui]: UTF-8 byte order mark not detected +2023.08.07 12:16:19 LOG5[ui]: FIPS mode disabled +2023.08.07 12:16:19 LOG4[ui]: Insecure file permissions on debian/tests/certs/key.pem +2023.08.07 12:16:19 LOG5[ui]: Configuration successful +2023.08.07 12:16:19 LOG5[0]: Service [test] accepted connection from 127.0.0.1:52880 +2023.08.07 12:16:19 LOG5[0]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:19 LOG5[0]: Service [test] connected remote server from 127.0.0.1:49392 +2023.08.07 12:16:19 LOG5[0]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:19 LOG5[1]: Service [test] accepted connection from 127.0.0.1:52886 +2023.08.07 12:16:19 LOG5[1]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:19 LOG5[1]: Service [test] connected remote server from 127.0.0.1:49406 +2023.08.07 12:16:19 LOG5[1]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:19 LOG5[2]: Service [test] accepted connection from 127.0.0.1:52896 +2023.08.07 12:16:19 LOG5[2]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:19 LOG5[2]: Service [test] connected remote server from 127.0.0.1:49408 +2023.08.07 12:16:19 LOG5[2]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:19 LOG5[3]: Service [test] accepted connection from 127.0.0.1:52910 +2023.08.07 12:16:19 LOG5[3]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:19 LOG5[3]: Service [test] connected remote server from 127.0.0.1:49416 +2023.08.07 12:16:19 LOG5[3]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:19 LOG5[4]: Service [test] accepted connection from 127.0.0.1:52922 +2023.08.07 12:16:19 LOG5[4]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:19 LOG5[4]: Service [test] connected remote server from 127.0.0.1:49418 +2023.08.07 12:16:19 LOG5[4]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:20 LOG5[5]: Service [test] accepted connection from 127.0.0.1:52934 +2023.08.07 12:16:20 LOG5[5]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:20 LOG5[5]: Service [test] connected remote server from 127.0.0.1:49422 +2023.08.07 12:16:20 LOG5[5]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:20 LOG5[6]: Service [test] accepted connection from 127.0.0.1:52950 +2023.08.07 12:16:20 LOG5[6]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:20 LOG5[6]: Service [test] connected remote server from 127.0.0.1:49434 +2023.08.07 12:16:20 LOG5[6]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:20 LOG5[7]: Service [test] accepted connection from 127.0.0.1:52964 +2023.08.07 12:16:20 LOG5[7]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:20 LOG5[7]: Service [test] connected remote server from 127.0.0.1:49448 +2023.08.07 12:16:20 LOG5[7]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:20 LOG5[8]: Service [test] accepted connection from 127.0.0.1:52972 +2023.08.07 12:16:20 LOG5[8]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:20 LOG5[8]: Service [test] connected remote server from 127.0.0.1:49458 +2023.08.07 12:16:20 LOG5[8]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:20 LOG5[9]: Service [test] accepted connection from 127.0.0.1:52988 +2023.08.07 12:16:20 LOG5[9]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:20 LOG5[9]: Service [test] connected remote server from 127.0.0.1:49466 +2023.08.07 12:16:20 LOG5[9]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:20 LOG5[ui]: Terminated +2023.08.07 12:16:20 LOG5[ui]: Terminating 1 service thread(s) +2023.08.07 12:16:20 LOG5[ui]: Service threads terminated +Started the stunnel server, pid 535009 Trying a connection through stunnel, iteration 1 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35802 +Registered a client connection as 127.0.0.1:52880 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34672 -Got an eof from 127.0.0.1:34672, all seems well -The server reported a completed connection: 127.0.0.1:34672 +Accepted a connection from 127.0.0.1:49392 +Got an eof from 127.0.0.1:49392, all seems well +The server reported a completed connection: 127.0.0.1:49392 The stunnel connection seems to have gone through for iteration 1 Trying a connection through stunnel, iteration 2 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35804 +Registered a client connection as 127.0.0.1:52886 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34686 -Got an eof from 127.0.0.1:34686, all seems well -The server reported a completed connection: 127.0.0.1:34686 +Accepted a connection from 127.0.0.1:49406 +Got an eof from 127.0.0.1:49406, all seems well +The server reported a completed connection: 127.0.0.1:49406 The stunnel connection seems to have gone through for iteration 2 Trying a connection through stunnel, iteration 3 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35810 +Registered a client connection as 127.0.0.1:52896 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34688 -Got an eof from 127.0.0.1:34688, all seems well -The server reported a completed connection: 127.0.0.1:34688 +Accepted a connection from 127.0.0.1:49408 +Got an eof from 127.0.0.1:49408, all seems well +The server reported a completed connection: 127.0.0.1:49408 The stunnel connection seems to have gone through for iteration 3 Trying a connection through stunnel, iteration 4 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35812 +Registered a client connection as 127.0.0.1:52910 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34694 -Got an eof from 127.0.0.1:34694, all seems well -The server reported a completed connection: 127.0.0.1:34694 +Accepted a connection from 127.0.0.1:49416 +Got an eof from 127.0.0.1:49416, all seems well +The server reported a completed connection: 127.0.0.1:49416 The stunnel connection seems to have gone through for iteration 4 Trying a connection through stunnel, iteration 5 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35820 +Registered a client connection as 127.0.0.1:52922 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34704 -Got an eof from 127.0.0.1:34704, all seems well -The server reported a completed connection: 127.0.0.1:34704 +Accepted a connection from 127.0.0.1:49418 +Got an eof from 127.0.0.1:49418, all seems well +The server reported a completed connection: 127.0.0.1:49418 The stunnel connection seems to have gone through for iteration 5 Trying a connection through stunnel, iteration 6 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35826 +Registered a client connection as 127.0.0.1:52934 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34712 -Got an eof from 127.0.0.1:34712, all seems well -The server reported a completed connection: 127.0.0.1:34712 +Accepted a connection from 127.0.0.1:49422 +Got an eof from 127.0.0.1:49422, all seems well +The server reported a completed connection: 127.0.0.1:49422 The stunnel connection seems to have gone through for iteration 6 Trying a connection through stunnel, iteration 7 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35840 +Registered a client connection as 127.0.0.1:52950 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34714 -Got an eof from 127.0.0.1:34714, all seems well -The server reported a completed connection: 127.0.0.1:34714 +Accepted a connection from 127.0.0.1:49434 +Got an eof from 127.0.0.1:49434, all seems well +The server reported a completed connection: 127.0.0.1:49434 The stunnel connection seems to have gone through for iteration 7 Trying a connection through stunnel, iteration 8 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35852 +Registered a client connection as 127.0.0.1:52964 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34720 -Got an eof from 127.0.0.1:34720, all seems well -The server reported a completed connection: 127.0.0.1:34720 +Accepted a connection from 127.0.0.1:49448 +Got an eof from 127.0.0.1:49448, all seems well +The server reported a completed connection: 127.0.0.1:49448 The stunnel connection seems to have gone through for iteration 8 Trying a connection through stunnel, iteration 9 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35854 +Registered a client connection as 127.0.0.1:52972 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34730 -Got an eof from 127.0.0.1:34730, all seems well -The server reported a completed connection: 127.0.0.1:34730 +Accepted a connection from 127.0.0.1:49458 +Got an eof from 127.0.0.1:49458, all seems well +The server reported a completed connection: 127.0.0.1:49458 The stunnel connection seems to have gone through for iteration 9 Trying a connection through stunnel, iteration 10 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35858 +Registered a client connection as 127.0.0.1:52988 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34736 -Got an eof from 127.0.0.1:34736, all seems well -The server reported a completed connection: 127.0.0.1:34736 +Accepted a connection from 127.0.0.1:49466 +Got an eof from 127.0.0.1:49466, all seems well +The server reported a completed connection: 127.0.0.1:49466 The stunnel connection seems to have gone through for iteration 10 -Trying to stop stunnel at pid 2958251 +Trying to stop stunnel at pid 535009 The stunnel process terminated successfully Checking for leftover children No child processes left over @@ -1267,24 +1302,24 @@ Using AnyEvent model $VAR1 = 'AnyEvent::Impl::IOAsync'; Found the certificate at debian/tests/certs/certificate.pem and the private key at debian/tests/certs/key.pem -Using the /tmp/2cqiKFuDnn temporary directory +Using the /tmp/R2CmoJo2mX temporary directory About to get the stunnel version information Got stunnel version 5.56 Listening for cleartext connections on 127.0.0.1:6502 -Connected to 127.0.0.1:6502, local 127.0.0.1:34750 -Accepted a connection from 127.0.0.1:34750 -Got a local connection id 127.0.0.1:34750 +Connected to 127.0.0.1:6502, local 127.0.0.1:49480 +Accepted a connection from 127.0.0.1:49480 +Got a local connection id 127.0.0.1:49480 Waiting for the server to acknowledge a completed client connection -Got an eof from 127.0.0.1:34750, all seems well +Got an eof from 127.0.0.1:49480, all seems well Waiting for the client connection itself to report completion Looks like we are done with the test cleartext connection! Got listening port 8086 for the stunnel server Let us hope this was enough to get stunnel to listen there... -Created the stunnel config file /tmp/2cqiKFuDnn/stunnel.conf: +Created the stunnel config file /tmp/R2CmoJo2mX/stunnel.conf: ====== -pid = /tmp/2cqiKFuDnn/stunnel.pid +pid = /tmp/R2CmoJo2mX/stunnel.pid foreground = yes -output = /tmp/2cqiKFuDnn/stunnel.log +output = /tmp/R2CmoJo2mX/stunnel.log cert = debian/tests/certs/certificate.pem key = debian/tests/certs/key.pem @@ -1293,149 +1328,149 @@ accept = 127.0.0.1:8086 connect = 127.0.0.1:6502 ====== -2024.09.07 16:37:29 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform -2024.09.07 16:37:29 LOG5[ui]: Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 -2024.09.07 16:37:29 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP -2024.09.07 16:37:29 LOG5[ui]: Reading configuration from file /tmp/2cqiKFuDnn/stunnel.conf -2024.09.07 16:37:29 LOG5[ui]: UTF-8 byte order mark not detected -2024.09.07 16:37:29 LOG5[ui]: FIPS mode disabled -2024.09.07 16:37:29 LOG4[ui]: Insecure file permissions on debian/tests/certs/key.pem -2024.09.07 16:37:29 LOG5[ui]: Configuration successful -2024.09.07 16:37:29 LOG5[0]: Service [test] accepted connection from 127.0.0.1:35860 -2024.09.07 16:37:29 LOG5[0]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:29 LOG5[0]: Service [test] connected remote server from 127.0.0.1:34766 -2024.09.07 16:37:29 LOG5[0]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:29 LOG5[1]: Service [test] accepted connection from 127.0.0.1:35868 -2024.09.07 16:37:29 LOG5[1]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:29 LOG5[1]: Service [test] connected remote server from 127.0.0.1:34778 -2024.09.07 16:37:29 LOG5[1]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:29 LOG5[2]: Service [test] accepted connection from 127.0.0.1:35884 -2024.09.07 16:37:29 LOG5[2]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:29 LOG5[2]: Service [test] connected remote server from 127.0.0.1:34792 -2024.09.07 16:37:29 LOG5[2]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:29 LOG5[3]: Service [test] accepted connection from 127.0.0.1:35888 -2024.09.07 16:37:29 LOG5[3]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:29 LOG5[3]: Service [test] connected remote server from 127.0.0.1:34800 -2024.09.07 16:37:29 LOG5[3]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[4]: Service [test] accepted connection from 127.0.0.1:35894 -2024.09.07 16:37:30 LOG5[4]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:30 LOG5[4]: Service [test] connected remote server from 127.0.0.1:34814 -2024.09.07 16:37:30 LOG5[4]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[5]: Service [test] accepted connection from 127.0.0.1:35896 -2024.09.07 16:37:30 LOG5[5]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:30 LOG5[5]: Service [test] connected remote server from 127.0.0.1:34818 -2024.09.07 16:37:30 LOG5[5]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[6]: Service [test] accepted connection from 127.0.0.1:35910 -2024.09.07 16:37:30 LOG5[6]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:30 LOG5[6]: Service [test] connected remote server from 127.0.0.1:34834 -2024.09.07 16:37:30 LOG5[6]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[7]: Service [test] accepted connection from 127.0.0.1:35916 -2024.09.07 16:37:30 LOG5[7]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:30 LOG5[7]: Service [test] connected remote server from 127.0.0.1:34844 -2024.09.07 16:37:30 LOG5[7]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[8]: Service [test] accepted connection from 127.0.0.1:35922 -2024.09.07 16:37:30 LOG5[8]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:30 LOG5[8]: Service [test] connected remote server from 127.0.0.1:34852 -2024.09.07 16:37:30 LOG5[8]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[9]: Service [test] accepted connection from 127.0.0.1:35932 -2024.09.07 16:37:30 LOG5[9]: s_connect: connected 127.0.0.1:6502 -2024.09.07 16:37:30 LOG5[9]: Service [test] connected remote server from 127.0.0.1:34864 -2024.09.07 16:37:30 LOG5[9]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket -2024.09.07 16:37:30 LOG5[ui]: Terminated -2024.09.07 16:37:30 LOG5[ui]: Terminating 1 service thread(s) -2024.09.07 16:37:30 LOG5[ui]: Service threads terminated -Started the stunnel server, pid 2958528 +2023.08.07 12:16:20 LOG5[ui]: stunnel 5.56 on x86_64-pc-linux-gnu platform +2023.08.07 12:16:20 LOG5[ui]: Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 +2023.08.07 12:16:20 LOG5[ui]: Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP +2023.08.07 12:16:20 LOG5[ui]: Reading configuration from file /tmp/R2CmoJo2mX/stunnel.conf +2023.08.07 12:16:20 LOG5[ui]: UTF-8 byte order mark not detected +2023.08.07 12:16:20 LOG5[ui]: FIPS mode disabled +2023.08.07 12:16:20 LOG4[ui]: Insecure file permissions on debian/tests/certs/key.pem +2023.08.07 12:16:20 LOG5[ui]: Configuration successful +2023.08.07 12:16:20 LOG5[0]: Service [test] accepted connection from 127.0.0.1:52996 +2023.08.07 12:16:20 LOG5[0]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:20 LOG5[0]: Service [test] connected remote server from 127.0.0.1:49490 +2023.08.07 12:16:20 LOG5[0]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[1]: Service [test] accepted connection from 127.0.0.1:53004 +2023.08.07 12:16:21 LOG5[1]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[1]: Service [test] connected remote server from 127.0.0.1:49494 +2023.08.07 12:16:21 LOG5[1]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[2]: Service [test] accepted connection from 127.0.0.1:53012 +2023.08.07 12:16:21 LOG5[2]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[2]: Service [test] connected remote server from 127.0.0.1:49496 +2023.08.07 12:16:21 LOG5[2]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[3]: Service [test] accepted connection from 127.0.0.1:53026 +2023.08.07 12:16:21 LOG5[3]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[3]: Service [test] connected remote server from 127.0.0.1:49504 +2023.08.07 12:16:21 LOG5[3]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[4]: Service [test] accepted connection from 127.0.0.1:53038 +2023.08.07 12:16:21 LOG5[4]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[4]: Service [test] connected remote server from 127.0.0.1:49514 +2023.08.07 12:16:21 LOG5[4]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[5]: Service [test] accepted connection from 127.0.0.1:53054 +2023.08.07 12:16:21 LOG5[5]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[5]: Service [test] connected remote server from 127.0.0.1:49528 +2023.08.07 12:16:21 LOG5[5]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[6]: Service [test] accepted connection from 127.0.0.1:53066 +2023.08.07 12:16:21 LOG5[6]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[6]: Service [test] connected remote server from 127.0.0.1:49544 +2023.08.07 12:16:21 LOG5[6]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[7]: Service [test] accepted connection from 127.0.0.1:53082 +2023.08.07 12:16:21 LOG5[7]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[7]: Service [test] connected remote server from 127.0.0.1:49552 +2023.08.07 12:16:21 LOG5[7]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:21 LOG5[8]: Service [test] accepted connection from 127.0.0.1:53090 +2023.08.07 12:16:21 LOG5[8]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:21 LOG5[8]: Service [test] connected remote server from 127.0.0.1:49554 +2023.08.07 12:16:22 LOG5[8]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:22 LOG5[9]: Service [test] accepted connection from 127.0.0.1:53092 +2023.08.07 12:16:22 LOG5[9]: s_connect: connected 127.0.0.1:6502 +2023.08.07 12:16:22 LOG5[9]: Service [test] connected remote server from 127.0.0.1:49556 +2023.08.07 12:16:22 LOG5[9]: Connection closed: 18 byte(s) sent to TLS, 0 byte(s) sent to socket +2023.08.07 12:16:22 LOG5[ui]: Terminated +2023.08.07 12:16:22 LOG5[ui]: Terminating 1 service thread(s) +2023.08.07 12:16:22 LOG5[ui]: Service threads terminated +Started the stunnel server, pid 535029 Trying a connection through stunnel, iteration 1 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35860 +Registered a client connection as 127.0.0.1:52996 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34766 -Got an eof from 127.0.0.1:34766, all seems well -The server reported a completed connection: 127.0.0.1:34766 +Accepted a connection from 127.0.0.1:49490 +Got an eof from 127.0.0.1:49490, all seems well +The server reported a completed connection: 127.0.0.1:49490 The stunnel connection seems to have gone through for iteration 1 Trying a connection through stunnel, iteration 2 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35868 +Registered a client connection as 127.0.0.1:53004 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34778 -Got an eof from 127.0.0.1:34778, all seems well -The server reported a completed connection: 127.0.0.1:34778 +Accepted a connection from 127.0.0.1:49494 +Got an eof from 127.0.0.1:49494, all seems well +The server reported a completed connection: 127.0.0.1:49494 The stunnel connection seems to have gone through for iteration 2 Trying a connection through stunnel, iteration 3 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35884 +Registered a client connection as 127.0.0.1:53012 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34792 -Got an eof from 127.0.0.1:34792, all seems well -The server reported a completed connection: 127.0.0.1:34792 +Accepted a connection from 127.0.0.1:49496 +Got an eof from 127.0.0.1:49496, all seems well +The server reported a completed connection: 127.0.0.1:49496 The stunnel connection seems to have gone through for iteration 3 Trying a connection through stunnel, iteration 4 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35888 +Registered a client connection as 127.0.0.1:53026 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34800 -Got an eof from 127.0.0.1:34800, all seems well -The server reported a completed connection: 127.0.0.1:34800 +Accepted a connection from 127.0.0.1:49504 +Got an eof from 127.0.0.1:49504, all seems well +The server reported a completed connection: 127.0.0.1:49504 The stunnel connection seems to have gone through for iteration 4 Trying a connection through stunnel, iteration 5 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35894 +Registered a client connection as 127.0.0.1:53038 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34814 -Got an eof from 127.0.0.1:34814, all seems well -The server reported a completed connection: 127.0.0.1:34814 +Accepted a connection from 127.0.0.1:49514 +Got an eof from 127.0.0.1:49514, all seems well +The server reported a completed connection: 127.0.0.1:49514 The stunnel connection seems to have gone through for iteration 5 Trying a connection through stunnel, iteration 6 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35896 +Registered a client connection as 127.0.0.1:53054 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34818 -Got an eof from 127.0.0.1:34818, all seems well -The server reported a completed connection: 127.0.0.1:34818 +Accepted a connection from 127.0.0.1:49528 +Got an eof from 127.0.0.1:49528, all seems well +The server reported a completed connection: 127.0.0.1:49528 The stunnel connection seems to have gone through for iteration 6 Trying a connection through stunnel, iteration 7 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35910 +Registered a client connection as 127.0.0.1:53066 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34834 -Got an eof from 127.0.0.1:34834, all seems well -The server reported a completed connection: 127.0.0.1:34834 +Accepted a connection from 127.0.0.1:49544 +Got an eof from 127.0.0.1:49544, all seems well +The server reported a completed connection: 127.0.0.1:49544 The stunnel connection seems to have gone through for iteration 7 Trying a connection through stunnel, iteration 8 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35916 +Registered a client connection as 127.0.0.1:53082 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34844 -Got an eof from 127.0.0.1:34844, all seems well -The server reported a completed connection: 127.0.0.1:34844 +Accepted a connection from 127.0.0.1:49552 +Got an eof from 127.0.0.1:49552, all seems well +The server reported a completed connection: 127.0.0.1:49552 The stunnel connection seems to have gone through for iteration 8 Trying a connection through stunnel, iteration 9 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35922 +Registered a client connection as 127.0.0.1:53090 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34852 -Got an eof from 127.0.0.1:34852, all seems well -The server reported a completed connection: 127.0.0.1:34852 +Accepted a connection from 127.0.0.1:49554 +Got an eof from 127.0.0.1:49554, all seems well +The server reported a completed connection: 127.0.0.1:49554 The stunnel connection seems to have gone through for iteration 9 Trying a connection through stunnel, iteration 10 Trying to connect to the stunnel server at 127.0.0.1:8086 ...connected! -Registered a client connection as 127.0.0.1:35932 +Registered a client connection as 127.0.0.1:53092 Waiting for the cleartext listener to receive this connection -Accepted a connection from 127.0.0.1:34864 -Got an eof from 127.0.0.1:34864, all seems well -The server reported a completed connection: 127.0.0.1:34864 +Accepted a connection from 127.0.0.1:49556 +Got an eof from 127.0.0.1:49556, all seems well +The server reported a completed connection: 127.0.0.1:49556 The stunnel connection seems to have gone through for iteration 10 -Trying to stop stunnel at pid 2958528 +Trying to stop stunnel at pid 535029 The stunnel process terminated successfully Checking for leftover children No child processes left over @@ -1449,7 +1484,7 @@ find tests/logs/ -type f -name '*.log' -print0 | xargs -0r grep -EHe '^' -- 1>&2; \ false; \ } - make -j16 test VERBOSE=1 + make -j15 test VERBOSE=1 make[2]: Entering directory '/build/stunnel4-5.56+dfsg' Making check in src make[3]: Entering directory '/build/stunnel4-5.56+dfsg/src' @@ -1477,7 +1512,7 @@ make check-local make[5]: Entering directory '/build/stunnel4-5.56+dfsg/tests' ./make_test -Sat Sep 7 16:37:32 -12 2024 +Mon Aug 7 12:16:23 +14 2023 stunnel 5.56 on x86_64-pc-linux-gnu platform Compiled/running with OpenSSL 1.1.1n 15 Mar 2022 Threading:PTHREAD Sockets:POLL,IPv6,SYSTEMD TLS:ENGINE,FIPS,OCSP,PSK,SNI Auth:LIBWRAP @@ -1543,12 +1578,12 @@ make[2]: Entering directory '/build/stunnel4-5.56+dfsg/src' make[3]: Entering directory '/build/stunnel4-5.56+dfsg/src' /bin/mkdir -p '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/bin' - /bin/bash ../libtool --mode=install /usr/bin/install -c stunnel '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/bin' + /bin/sh ../libtool --mode=install /usr/bin/install -c stunnel '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/bin' libtool: install: /usr/bin/install -c stunnel /build/stunnel4-5.56+dfsg/debian/stunnel4/usr/bin/stunnel /bin/mkdir -p '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/bin' /usr/bin/install -c stunnel3 '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/bin' /bin/mkdir -p '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/lib/x86_64-linux-gnu/stunnel' - /bin/bash ../libtool --mode=install /usr/bin/install -c libstunnel.la '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/lib/x86_64-linux-gnu/stunnel' + /bin/sh ../libtool --mode=install /usr/bin/install -c libstunnel.la '/build/stunnel4-5.56+dfsg/debian/stunnel4/usr/lib/x86_64-linux-gnu/stunnel' libtool: install: /usr/bin/install -c .libs/libstunnel.so /build/stunnel4-5.56+dfsg/debian/stunnel4/usr/lib/x86_64-linux-gnu/stunnel/libstunnel.so libtool: install: /usr/bin/install -c .libs/libstunnel.lai /build/stunnel4-5.56+dfsg/debian/stunnel4/usr/lib/x86_64-linux-gnu/stunnel/libstunnel.la libtool: warning: remember to run 'libtool --finish /usr/lib/x86_64-linux-gnu/stunnel' @@ -1643,12 +1678,14 @@ dpkg-buildpackage: info: binary-only upload (no source included) dpkg-genchanges: info: not including original source code in upload I: copying local configuration +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/B01_cleanup starting +I: user script /srv/workspace/pbuilder/518328/tmp/hooks/B01_cleanup finished I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env -I: removing directory /srv/workspace/pbuilder/2945234 and its subdirectories -I: Current time: Sat Sep 7 16:38:13 -12 2024 -I: pbuilder-time-stamp: 1725770293 +I: removing directory /srv/workspace/pbuilder/518328 and its subdirectories +I: Current time: Mon Aug 7 12:17:09 +14 2023 +I: pbuilder-time-stamp: 1691360229