From: Pavel Machek <pavel@suse.cz>
To: Marko <letterdrop@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Who wants to test cracklinux??
Date: Wed, 29 Mar 2006 00:49:30 +0200 [thread overview]
Message-ID: <20060328224929.GC5760@elf.ucw.cz> (raw)
In-Reply-To: <20060328221223.80753cab.letterdrop@gmx.de>
Hi!
> I've written a small kernel module & shared object for kernel 2.6 to
> enable the following for normal users:
>
> - inb()/outb()... via a wrapper function
ioperm() does that already, no? You mean, you enable it for non-root,
too? That's security hole.
> - enable direct IO access (like ioperm())
> - direct access on physical memory addresses
read/write on /dev/mem. chmod 666 /dev/mem if you want to allow normal
users to access physical memory (security hole, again).
> - installation of user space ISR
That seems nice. Does it work with PCI shared interrupts?
> - change nice level
>
> The module is primary thought for education, but perhaps also helpful
> in software development.
> The module is finished now, but because it's my first kernel code
> there could be something to improve. If anyone wants to test, just
> send me a mail and you'll get the code.
Please post it to the list.
Pavel
--
Picture of sleeping (Linux) penguin wanted...
next prev parent reply other threads:[~2006-03-28 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 20:12 Who wants to test cracklinux?? Marko
2006-03-28 22:01 ` Sam Ravnborg
2006-03-28 22:49 ` Pavel Machek [this message]
2006-03-28 23:49 ` Måns Rullgård
2006-03-29 12:02 ` Jan Engelhardt
2006-03-29 12:32 ` Marko Euth
2006-04-02 22:34 ` Ben Ford
2006-04-02 22:39 ` Arjan van de Ven
2006-04-02 23:07 ` Marko Euth
2006-04-02 23:16 ` Alan Cox
2006-04-03 9:11 ` Jan Engelhardt
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=20060328224929.GC5760@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=letterdrop@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.