From: Robin Green <greenrd@greenrd.org>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Module exploits into the host?
Date: Wed, 3 Mar 2004 20:09:37 +0000 [thread overview]
Message-ID: <20040303200937.GK14069@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
Even with the skas patch, is it possible for an insmod to allow an attacker to
break out of a UML?
If not, why not?
If so, are there any configurations that are not vulnerable to this?
--
Robin
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-03-03 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 20:09 Robin Green [this message]
2004-03-03 21:29 ` [uml-devel] Module exploits into the host? Henrik Nordstrom
2004-03-03 23:14 ` [uml-devel] More security questions (was: Module exploits into the host?) Robin Green
2004-03-07 11:06 ` BlaisorBlade
2004-03-08 21:33 ` Jeff Dike
2004-03-09 23:21 ` Robin Green
2004-03-04 9:36 ` [uml-devel] Module exploits into the host? Cameron Patrick
2004-03-04 10:19 ` Peter
2004-03-04 19:45 ` [uml-devel] CFP workshop on UML Security (was: Module exploits into the host?) Goetz Bock
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=20040303200937.GK14069@localhost.localdomain \
--to=greenrd@greenrd.org \
--cc=user-mode-linux-devel@lists.sourceforge.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