Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 29 Aug 2012 23:08:49 +0400
From: Vasily Kulikov <segoon@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: glibc update

Solar, Dmitry,

On Thu, Aug 23, 2012 at 12:35 +0400, Solar Designer wrote:
> On Thu, Aug 23, 2012 at 02:07:20AM +0400, Dmitry V. Levin wrote:
> > On Sun, Aug 12, 2012 at 10:23:30PM +0400, Solar Designer wrote:
> > [...]
> > > Thanks for researching it.  I think there's no need to do anything about
> > > it yet - we'll upgrade glibc soon.
> > 
> > Is there any specific plan for this glibc update?
> 
> Vasiliy - what are your plans for this, of any?

No special plans.  I worked on this in Spring, I might not remember
all things about this update.

I can continue to work on it after kernel/vzctl commmit and post all the
results.

> I notice that we have
> glibc-2.14.1-owl17 installed on a test build system since February,
> but it lacks changelog records (and the -owl17 appears to be left intact
> from 2.3.6-owl17), so I don't know who worked on it (I guess you?) and
> what state the corresponding patch set is in (I guess dirty hack?)

IIRC, it is very early try.  If it is workable at all, it doesn't
contain all patches I've ported.

> Perhaps you can/should share your latest glibc patches with the team?

The patches and spec file are located on another system.  I'll post the
results tomorrow.

I haven't tested glibc on any network services, only basic world rebuild test
with workable su/make/rpm.  So, it's not close to CVS commit stage.

> > I'm working on update of ALT's glibc, and there are few issues I'd like to
> > discuss if somebody else is interested.  For example, the code introduced
> > by owl-alt-res_randomid.diff is not MT-safe (it even has a comment
> > explicitly stating that fact) but the resolver is expected to be MT-safe
> > nowadays.
> 
> Thank you for mentioning this.  Can you start by posting a list of those
> issues (summaries like the above), as well as whether you have proposed
> fixes for them.

Agreed.  Especially if these issues are not so obvious (like this MT-safety).

Thanks,

-- 
Vasiliy

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ