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]

Date:	Thu, 22 Dec 2011 12:52:32 -0500
From:	"John Stoffel" <john@...ffel.org>
To:	Gaurav Saxena <grvsaxena419@...il.com>
Cc:	richard -rw- weinberger <richard.weinberger@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Intercepting system calls

>>>>> "Gaurav" == Gaurav Saxena <grvsaxena419@...il.com> writes:

>> Intercepting system calls is very bad, don't do it.

Gaurav> Oh. I will not do it then, could you suggest me something so
Gaurav> that I could prevent unlink on some file say using kernel
Gaurav> support. I want to save file on unlink how could I do that
Gaurav> without kernel support, or how could I do that using a kernel
Gaurav> module.

Write a FUSE module to mount the filesystem through, inside your FUSE
module you can intercept the unlink/truncate/write calls and decide
what you want to have happen.

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