mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org, Jacques Gelinas <jack@solucorp.qc.ca>
Subject: Re: System call wrapping
Date: Mon, 21 Oct 2002 14:33:32 -0400	[thread overview]
Message-ID: <3DB4487C.F6355C59@opersys.com> (raw)
In-Reply-To: <ap1g9a$pso$1@ncc1701.cistron.net>


Miquel van Smoorenburg wrote:
> In article <1035222121.1063.20.camel@pc177>,
> Henrý Þór Baldursson  <henry@f-prot.com> wrote:
> >In our Windows product we have something called "Realtime protector"
> >which monitors file access on Windows running machines and scans them
> >before allowing access.
> >
> >We now want, due to customer demand, to supply our Linux users with
> >similar functionality, and we've created a 2.4.x kernel module which
> >wrapped the open system call by means of overwriting
> >sys_call_table[__NR_open].
>
> What is wrong with a preloaded library (by means of /etc/ld.so.preload)
> that intercepts open at the library level (and calls the real open()
> using RLTD_NEXT) ? Just let it talk over a unix socket to your
> scanner server.

Jacques Gelinas already has something that does precisely that:
http://www.solucorp.qc.ca/virtualfs/

I don't know if it's still being updated, but the ideas are all there.

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

  reply	other threads:[~2002-10-21 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 17:42 Henrý Þór Baldursson
2002-10-21 18:12 ` Alan Cox
2002-10-21 18:16 ` Miquel van Smoorenburg
2002-10-21 18:33   ` Karim Yaghmour [this message]
2002-10-22 14:02   ` Rogier Wolff
2002-10-21 20:14 ` Rik van Riel
2002-10-21 20:33   ` Lucio Maciel
2002-10-22  5:19     ` Greg KH
2002-10-22  1:01   ` jw schultz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DB4487C.F6355C59@opersys.com \
    --to=karim@opersys.com \
    --cc=jack@solucorp.qc.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome