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] [thread-next>] [day] [month] [year] [list]
Message-ID: <54818A4B.60100@arm.com>
Date:	Fri, 05 Dec 2014 10:34:51 +0000
From:	"Suzuki K. Poulose" <Suzuki.Poulose@....com>
To:	Steven Stewart-Gallus <sstewartgallus00@...angara.bc.ca>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: How can I parse the command name from /proc/<pid>/stat?

On 04/12/14 19:44, Steven Stewart-Gallus wrote:
> Hello,
>
> Given an evil hacker trying to confuse process monitors that might use such
> strange process names as 'pause) R 0 0 (foo' how can I correctly parse the
> command name from /proc/<pid>/stat? Maybe I should just use /proc/<pid>/status?
> Maybe there should be some documentation written on the issue? I just wanted to
> send an email off to check if I was missing anything before writing a few small
> additions to the documentation or filing a bug report. procps-ng seems to use an
> ugly hack that involves knowing the limits on the size of a possible command
> name that I'm not actually sure works totally correctly.

You can do something like :

cmd_start = strchr(stat_buf, '(');
cmd_end = strrchr(stat_buf, ')');

Cheers
Suzuki


>
> Thank you,
> Steven Stewart-Gallus
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ