Package: passt Version: 0.0~git20251210.d04c480-1 Severity: important Dear Maintainer,
After ugprading from passt 0.0~git20250919.623dbf6 to passt 0.0~git20251210.d04c480, I noticed podman containers that leverage pasta as part of their network stack suffered from significant connectivity issues. For some reason, HTTPS traffic is affected, HTTP is not. I assume the problem stems from the combination of pasta + some TLS libraries, hence the title. In the end, the issue can be reproduced this way: podman run --rm docker.io/curlimages/curl curl -sv https://perdu.com/ Specifically, curl exits with return code 56, meaning "Failure in receiving network data". A brief analysis of syscalls does not seem to reveal anything suspicious. I have tested the following packages: passt_0.0~git20250919.623dbf6-1_amd64.deb -- ok, works as expected passt_0.0~git20251208.e8b56a3-1_amd64.deb -- ko, timeout passt_0.0~git20251209.c3f1ba7-1_amd64.deb -- ko, timeout passt_0.0~git20251210.d04c480-1_amd64.deb -- ko, timeout I remain available for more information. -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.17.11+deb14-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages passt depends on: ii libc6 2.42-6 passt recommends no packages. Versions of packages passt suggests: ii apparmor 4.1.0-1+b1 -- no debconf information
