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>] [day] [month] [year] [list]
Message-ID: <CAJYFCiNQkmFoLOsfm9=PqyY6oBmFD0=3m+OQrMZwoZFPeGBeXQ@mail.gmail.com>
Date:   Mon, 24 Jul 2017 22:10:09 +0800
From:   Yubin Ruan <ablacktshirt@...il.com>
To:     linux-kernel@...r.kernel.org
Cc:     comandante@...alinux.com, shen@...fujitsu.com, stefani@...bold.net,
        Dbueso@...e.com
Subject: Conserve /proc/$pid after a process exit

Does anyone have ideas how to preserve a /proc/$pid directory after a process
exit? I want to perform some audit on some process A from within
another process B. Process B have the pid of process A but after A
exit, B can no longer retrieve
info from /proc/$pid. I am wondering whether it is possible for B to
have a special "handle" of /proc/$pid so that after A exist B can
still read from it.

In my situation, A know nothing of B so A can send no message to B.

Are there any mechanism for this purpose? Locking that dir?

Thanks,
Yubin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ