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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1164050878.31358.608.camel@laptopd505.fenrus.org>
Date:	Mon, 20 Nov 2006 20:27:57 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	e m <eyubo@...mail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: path_lookup for executable

On Mon, 2006-11-20 at 19:14 +0000, e m wrote:
> Thanks for response. Is there any other way to identify if "current"  is a 
> certain program  such as java.  You cannot surely go by name (comm field of 
> task_struct). Since  It could be linked. In another word, I want to identify 
> the executing current program. Any help appreciated.

since the binary may have been removed from the disk entirely (and no
that is not a corner case, a lot of the background daemons will have
that if their "original" gets rpm-updated or similar)... what would this
mean? What do you want to use it for?



-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
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