| 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
| ||
|
Date: Fri, 23 Dec 2011 14:38:59 +0530 From: Gaurav Saxena <grvsaxena419@...il.com> To: "J. R. Okajima" <hooanon05@...oo.co.jp> Cc: linux-kernel@...r.kernel.org Subject: Re: Intercepting system calls Hello J. R. Okajima On Fri, Dec 23, 2011 at 12:55 PM, J. R. Okajima <hooanon05@...oo.co.jp> wrote: > > Hello Gaurav, > > Gaurav Saxena: >> I am writing an application for which I need to intercept some >> filesystem system calls eg. unlink. I need unlink to call my code > ::: > > For kernel space, CONFIG_KPROBES may help you. > See Documentation/kprobes.txt in detail. Ok I have seen details of KPROBES, I think it will suit to my requirements, I just wanted to know a few things, Can I use probes to prevent unlink of certain files? Also is CONFIG_KPROBES set to "y" on linux kernels available with distros like ubuntu? > > For user space, $LD_PRELOAD may help you. > You will need to develop your shared object library which contains > your_unlink() and replaces the original unlink(). > See ld.so(8) manual page. > > > J. R. Okajima -- Thanks and Regards , Gaurav -- 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