linux-kernel - Re: Fwd: brk randomization breaks columns

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-next>] [day] [month] [year] [list]

Message-ID: <20080204195251.GB4915@elf.ucw.cz>
Date:	Mon, 4 Feb 2008 20:52:51 +0100
From:	Pavel Machek <pavel@....cz>
To:	Abel Bernabeu <abel.bernabeu@...il.com>
Cc:	mingo@...e.hu, kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: brk randomization breaks columns

> >
> > > I still don't seem to fully understand what is happening here --
> > > aparently this is triggerable only with old programs linked against
> > > libc.so.5, and I am not able to trigger it with my trivial program when
> > > I link it against old libc.so.5, which just basically does brk() and
> > > checks whether /proc/<pid>/maps are OK. Seems to me that (at least
> > > certain versions) of libc.so.5 (wrongly) assume that end of the bss is
> > > the start of the heap, but I will try to investigate it more.
> 
> I think I am getting the some problem with brand new binaries produced
> by myself :(
> 
> Look at this report I posted days ago:
> 
> http://marc.info/?l=linux-kernel&m=120169141603789&w=2

Your crash is in kernel, no? Anyway, I can workaround mine by
disabling randomization...
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/