lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9353728.11137281237331262320.JavaMail.root@ouachita>
Date:	Tue, 17 Mar 2009 19:07:42 -0400 (EDT)
From:	Joe Malicki <jmalicki@...acarta.com>
To:	Hugh Dickins <hugh@...itas.com>
Cc:	chrisw@...s-sol.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	David Howells <dhowells@...hat.com>
Subject: Re: [PATCH] CRED: Fix check_unsafe_exec()


----- "Joe Malicki" <jmalicki@...acarta.com> wrote:

> ----- "Hugh Dickins" <hugh@...itas.com> wrote:
> 
> > On Thu, 12 Mar 2009, David Howells wrote:
> > > Hugh Dickins <hugh@...itas.com> wrote:
> > >
> > > > We do.  See the original thread.  It's here at
> > > > http://lkml.org/lkml/2009/2/26/233
> > > > and appended below for convenience.  We do know that patch did
> > not
> > > > fix Joe's problem, and we don't yet know whether addressing the
> > > > files->count issue will actually fix it, but I'm hopeful.
> > >
> > > Looks reasonable.
> >
> > Thanks for taking a look.
> >
> > Yes, I'm inclined to go with that, and removing the files->count
> > check from exec.c.  Joe, did you manage to try your testing with
> > my original patch plus that files->count check removed from 2.6.28's
> > unsafe_exec()?
> 
> Sorry for not responding earlier.
> 
> I still got one failure with this new patch.  I added some printks
> to illuminate exactly why it's failing when it fails to setuid, but
> of course, since adding the printks I haven't reproduced yet.
>

My tests were accidentally run without removing the files->count check.

The printks confirmed the failure case was the files->count check,
and removing the files->check has worked thus far (though I can't be
sure until after a day or two has gone by given how infrequent it is).

Thanks!
Joe
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ