Thanks for adding the -N option, it's very handy to test the networking portion.
You're right, in6addr_loopback isn't going to work -- it is then only listening on ::1:60000 and connections to 127.0.0.1:60000 don't work. I think this is going to take a more complicated fix, one of these options is needed: - ensure cups is looking for ippusbxd printers over IPv6 - change ippusbxd to function over IPv4 only - change ippusbxd to bind to two sockets, one for IPv6 in6addr_loopback and one for IPv4 INADDR_LOOPBACK. This would also require using select() to determine which of the two ports is connected each iteration through the loop. This also feels like the best solution. We really can't continue with the current code -- it is currently open for all to connect to, on all interfaces that are configured on the system. I'll ask MITRE for a CVE for this later, once we're closer to having a patch. Thanks Till. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455644 Title: [MIR] ippusbxd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ippusbxd/+bug/1455644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
