From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4489 Path: news.gmane.org!not-for-mail From: Christian Wiese Newsgroups: gmane.linux.lib.musl.general Subject: Re: install.sh is wrong with libc.so Date: Wed, 15 Jan 2014 13:58:39 +0100 Message-ID: <20140115135839.6856a21c@mopad> References: <5905c9fb-9fc8-4cf1-ac29-ed830c8ae5a1@email.android.com> <20140115123552.39250038@mopad> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/.rupi6JJ0.hl9E.cL_Cy=yq"; protocol="application/pgp-signature" X-Trace: ger.gmane.org 1389790747 11101 80.91.229.3 (15 Jan 2014 12:59:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 15 Jan 2014 12:59:07 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4493-gllmg-musl=m.gmane.org@lists.openwall.com Wed Jan 15 13:59:16 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1W3Q3u-0007Qo-Aq for gllmg-musl@plane.gmane.org; Wed, 15 Jan 2014 13:59:14 +0100 Original-Received: (qmail 30491 invoked by uid 550); 15 Jan 2014 12:59:13 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30481 invoked from network); 15 Jan 2014 12:59:13 -0000 In-Reply-To: X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; i686-pc-linux-gnu) Xref: news.gmane.org gmane.linux.lib.musl.general:4489 Archived-At: --Sig_/.rupi6JJ0.hl9E.cL_Cy=yq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, > Dangerous in case after performing installation, dynamic linked > system becomes unusable: no logins are accepted, no shell can be > spawned, even self-boot with init=3D kernel command line will give you > nothing but a kernel panic. (Of course I should have a static linked > busybox, but I even did not expected such a change will occur since > 0.9.12) Yes, a static busybox would might have helped there, but doing a libc update on a running system should be avoided anyways even if it kind of worked out before in your case as it seems! > >I think the info about how you are building would be quite helpful. >=20 > I did installation as root user. I also do not run > restrictive/hardened kernels. Sorry I lost log of installation, but > after installing 0.9.15' libc.so "make install" refused to run with > "Permission denied" error. Rest is simple: no command can be > executed, login attempts refused, symptoms like "rm -fr /" was > executed, only with "Permission denied". Only boot from rescue flash > drive with prepared initrd showed that /lib/libc.so was > half-installed with mode 600. >=20 see above answer. Cheers, Chris --=20 PGP Fingerprint: F96B A15F DF25 2B3E 49CB BA16 241B F3E7 52FE AFC6 --Sig_/.rupi6JJ0.hl9E.cL_Cy=yq Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iEYEARECAAYFAlLWhf8ACgkQJBvz51L+r8bDnACgiy7T3bw5zQd1LQ8OKHoJR5zK Wf8AnRI76xVlm0bHZZt2hzMWKbRN6DBA =f6AM -----END PGP SIGNATURE----- --Sig_/.rupi6JJ0.hl9E.cL_Cy=yq--