linux-kernel - Re: make tar*-pkg considered dangerous

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5050BBC1.1090207@gmail.com>
Date:	Wed, 12 Sep 2012 18:43:45 +0200
From:	Zdenek Kaspar <zkaspar82@...il.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: make tar*-pkg considered dangerous

On 09/12/2012 05:16 AM, Andi Kleen wrote:
> 
> Hi,
> 
> We've had some incidents with people destroying Fedore 17 installs
> (to the point of reinstall) by installing a kernel tarball generated with 
> make tar*-pkg
> 
> The problem is that the tarball includes /lib/{modules,firmware},
> but on FC17 /lib is a symlink. tar when it unpacks the tarball
> replaces the symlink with the directory. So they end up
> with a /lib which only contains the new kernel files, but nothing else,
> 
> And then the system doesn't boot anymore.
> 
> I'm not sure there is a good fix for this. I don't know of a way to
> convince tar to not do that. And putting everything into /usr 
> would be very incompatible.
> 
> Disable these make targets or add warnings?  If disabling people should
> use rpms or dpkgs instead?
> 
> -Andi
> 

I dont use the dpkg/rpm variants myself, but unpack with -h should be
enough?

HTH, Z.
--
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/