netdev - Re: newline characters in unix socket names and /proc/net/unix

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150317212727.GB9874@chaz.gmail.com>
Date:	Tue, 17 Mar 2015 21:27:27 +0000
From:	Stephane Chazelas <stephane.chazelas@...il.com>
To:	netdev@...r.kernel.org
Cc:	Craig Small <csmall@...ian.org>,
	Vic Abell <vabell@...f.comcastbiz.net>
Subject: Re: newline characters in unix socket names and /proc/net/unix

2015-03-14 22:33:42 +0000, Stephane Chazelas:
[...]
> it seems the kernel doesn't escape newline characters in the
> file names displayed in /proc/net/unix
[...]
> and is used by things like fuser, lsof for instance to map Inode
> to Path (and libgtop, systemd (to check which sockets are still
> in use for cleanup) at least).
[...]

A solution for fuser and lsof (at least) would be to use the new
netlink-based API where available (like "ss -ax" does on recent
systems) that doesn't have the problem.

For lsof, that would also mean (for linux-3.3 and above) that it
could display information about the peer of the socket (like it
does with lsof -E for pipes).

-- 
Stephane
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html