linux-kernel - Re: Linux 2.6.18 break scratchbox

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: <d4e708d60610052341v8e8718cpfca5b60a28bfc93b@mail.gmail.com>
Date:	Fri, 6 Oct 2006 08:41:56 +0200
From:	"koos vriezen" <koos.vriezen@...il.com>
To:	"Pavel Machek" <pavel@....cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Linux 2.6.18 break scratchbox

2006/10/4, Pavel Machek <pavel@....cz>:
> Hi!
>
> > Hit by http://bugzilla.scratchbox.org/bugzilla/show_bug.cgi?id=279 I
> > wondered why such
> > a change that could break existing setups entered 2.6.18.
> > Now I can peek through '/proc/<pid of process outside chroot env w/ my
> > UID>/root' into the
> > box's root (and that's why scratchbox is broken now).
>
> File bug at bugzilla.kernel.org :-).
>
> I'm afraid we did not know about this ABI change, and noone using
> scratchbox tested 2.6.18-rcX...

Well I did google for this before this report and eg.
http://nchip.livejournal.com/ already mentioned it (but probably
didn't report it at lkml) and there where some other links.
But since I couldn't find any info on this new feature, that one can
now read and write file through the /proc/xx/root link, I ask it here.
And hopefully, if it's a regression, would be fixed in the stable tree
ASAP. (Somehow I almost can't believe this change wouldn't show
immediately in a regression test setup, and there must be a reason for
opening this door w/o using an axe).

Koos
>                                                                 Pavel
-
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/