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: <3kqsi4wasq53l2ugn45jcuowb4ntnbsdwidqulqvuakc4ezslj@hbuct36boj6v>
Date: Wed, 4 Feb 2026 10:21:14 +0100
From: Michal Kubecek <mkubecek@...e.cz>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, Josiah Stearns <B00TK1D@...ton.me>
Subject: Re: [PATCH iproute2-next] ss: escape characters in command name

Dne Tue, Feb 04, 2025 at 08:24:16AM GMT, Stephen Hemminger napsal:
> Since the process name is under user control with prctl(PR_SET_NAME)
> it may contain escape characters to try and mess with screen output.
> 
> Reuse the existing string logic from procps (used by ps command).
> 
> Reported-by: Josiah Stearns <B00TK1D@...ton.me>
> Signed-off-by: Stephen Hemminger <stephen@...workplumber.org>

Hello,

I found this patch while checking if the problem of sanitizing process
names in ss output has been already discussed. As far as I can see, it
was not applied to git and there wasn't any discussion in the list
either. Was it just forgotten or was it rejected for some reason?

Michal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ