linux-kernel - Re: Intercepting system calls

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: <alpine.LRH.2.00.1112231047000.21599@twin.jikos.cz>
Date:	Fri, 23 Dec 2011 10:47:37 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Gaurav Saxena <grvsaxena419@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Intercepting system calls

On Thu, 22 Dec 2011, Gaurav Saxena wrote:

> I am writing an application for which I need to intercept some
> filesystem system calls eg. unlink. I need unlink to call my code
> before deleting abc so that I could probably prevent unlink . I would
> like to implement this in a kernel module instead of modifying kernel
> code itself. I would like to intercept system calls by replacing
> system calls but I have not been able to find any method of doing that
> in linux > 3.0. Please suggest some method of doing that.

Write a kernel module that instruments sys_unlink() via krpobes. See 
Documentation/kprobes.txt for details.

-- 
Jiri Kosina
SUSE Labs

--
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/