This might be fixed in 0.8.0-5 by https://bugs.debian.org/1073806
But the comment here (PSz) seems very suspicious to me: https://salsa.debian.org/debian/atftp/-/blob/0.8.0-5/tftpd.c?ref_type=tags#L703 Note that by this point in the code `data->client_info->client` is set to the peer address, and `to` is set to the host address (the address the client sent its packet "to"). The code proceeds to override `to.sa_family` to the host family. This is wrong if the client connected using ipv4 but the host uses an ipv6 socket. It probably results in some garbage address being passed to `bind`. I have a feeling the `memset` which was added in 0.8.0-5 "solved" this because it so happens that it results in the all zeros address being passed, but relying on this is super dodgy. I'm not 100% sure what the correct fix is, but my guess is the `data->client_info->client` and `to` addresses need to be properly converted to the same type (v4 or v6) and then it will work? Eg convert `to` to a "::ffff:a:b:c:d` type address first? ** Bug watch added: Debian Bug tracker #1073806 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073806 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065463 Title: atftpd require UDPv4 socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atftp/+bug/2065463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
