linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Steve Schmidtke <steve_schmidtke@hotmail.com>, kraxel@bytesex.org
Subject: Re: [uml-devel] RE: uml_switch security fixing
Date: Wed, 9 Mar 2005 11:34:12 +0100	[thread overview]
Message-ID: <200503091134.12352.blaisorblade@yahoo.it> (raw)
In-Reply-To: <BAY24-F21573D60D3DDE776FDC27C835F0@phx.gbl>

On Monday 07 March 2005 05:42, Steve Schmidtke wrote:
> Blaisorblade wrote:
> >Hey, has anyone found the time to put together any patch to workaround the
> >security bug in uml_net?

> Attached are two patches.  The first one, uml_net-slip.diff, is the minimal
> patch to apply to uml_net.  The second one, uml_net-uml.diff, applies to
> 2.4.27-1um
Thanks for your time and work!
> (note the half-hearted attempt to plug a FD leak in there as 
> well).
Verified, both seem correct (the closed fd's are local var, so there is no 
possibility they were closed elsewhere).

half-hearted... ok, found in my dictionary!!! Wow!
> As a nice bonus, a UML with this patch still works with an 
> unpatched uml_net binary.
Hmm, this means many users could avoid upgrading... Well, it's their box 
anyway.

But an unpatched UML won't work with a newer uml_net binary (for SLIP usage 
only and only for closing the interface, I mean), right?

I see that this way it's not possible to avoid this (and frankly, I was ready 
to discard SLIP support until the fix was ready, so it is ok). Also the patch 
is very little (and applies unchanged to 2.6.11, so I guess there will be 0 
backporting problems).

I'm applying this nevertheless in my tools (I think I'll forward all this to 
Jeff, or maybe I'll send him a released tarball + the splitout changes), and 
I'm also going to publish as much information as I can (which means 
pre-adding an entry to the Wiki).

I also looked at the versioning for uml_net, but what happens is that we can 
only stop unpatched uml_net from working with newer UML for any protocol, not 
anything else. So I won't change that. However, I just saw that we did it 
correctly until Version 3 of the uml_net protocol...
I wonder what has happened after.

> >I think it would be ok also to simply comment out the offending code (even
> >providing some kind of -D configuration option for who really needs SLIP
> >support, and they are few)!
> >
> >Suggestions?
>
> Agreed, tuntap is a compile time option, slip should be as well.
Ok... tuntap is compile-time because of a rough check for host support.
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2005-03-09 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07  4:42 [uml-devel] RE: uml_switch security fixing Steve Schmidtke
2005-03-09 10:34 ` Blaisorblade [this message]
2005-03-09 18:53   ` Steve Schmidtke
2005-03-09 19:31     ` Blaisorblade
2005-03-12  5:48 ` Jeff Dike
  -- strict thread matches above, loose matches on Subject: below --
2005-03-02 14:53 [uml-devel] " Blaisorblade
2005-03-03 12:47 ` [uml-devel] " Nuutti Kotivuori
2005-03-09  9:23   ` Blaisorblade

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=200503091134.12352.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=kraxel@bytesex.org \
    --cc=steve_schmidtke@hotmail.com \
    --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