mal content <[EMAIL PROTECTED]> wrote:
> I was looking for a way to write a small wrapper program
> that disables network access and then exec()'s a given
> program.
Sorry for the late reply, but ... The easiest way to do
what you described is to run the program in a jail which
has a jail IP t
On 05/07/06, Daan Vreeken [PA4DAN] <[EMAIL PROTECTED]> wrote:
On Wednesday 05 July 2006 03:15, mal content wrote:
> On 03/07/06, Peter Jeremy <[EMAIL PROTECTED]> wrote:
> > For dynamic executables, you could LD_PRELOAD a .so that replaces
> > all the socket-related syscalls.
>
> Excellent suggest
On Wednesday 05 July 2006 03:15, mal content wrote:
> On 03/07/06, Peter Jeremy <[EMAIL PROTECTED]> wrote:
> > For dynamic executables, you could LD_PRELOAD a .so that replaces
> > all the socket-related syscalls.
>
> Excellent suggestion! Ok, I've created a basic .so file with the following
> code
On 03/07/06, Peter Jeremy <[EMAIL PROTECTED]> wrote:
For dynamic executables, you could LD_PRELOAD a .so that replaces
all the socket-related syscalls.
Excellent suggestion! Ok, I've created a basic .so file with the following
code, but I've basically got stuck because I don't know how the orig
On Mon, 2006-Jul-03 18:09:27 +0100, mal content wrote:
>Was it my imagination or did I see a function in libc that
>allowed a process to prevent further network access?
The closest is shutdown(2) which can stop further access in one
direction on an existing socket - not what you want.
>I was look
Was it my imagination or did I see a function in libc that
allowed a process to prevent further network access? I'm
pretty sure that I read the manual page for it and now I can't
find it.
I was looking for a way to write a small wrapper program
that disables network access and then exec()'s a giv
6 matches
Mail list logo