lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAC-fF8SMUsj8pPJO+VYdRSQAOcwyBpJY1C9V3VEk3zrFS=Jy4Q@mail.gmail.com> Date: Sun, 16 Oct 2016 23:43:13 +0300 From: Isaac Boukris <iboukris@...il.com> To: netdev@...r.kernel.org Subject: iproute: ss truncates abstract unix domain socket embedding null Hello, The unix(7) man page says that null have no special meaning in abstract unix domain socket address (the length is specified therefore). However, when such name (embedding null) is used, ss (and netstat) will only show up to the first null occurrence (second technically, if we count the null prefix). e.g. the name "\0/tmp/fo\0.sock" is displayed as: "@/tmp/fo" (whilst strace tool shows it as: sun_path=@"/tmp/fo\0.sock"). Would it be more useful if it printed the whole name and escaped the null? If so, would '\0' be ok for escaping the null? Thanks!
Powered by blists - more mailing lists