mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Christian Wiese <chris@opensde.net>
To: musl@lists.openwall.com
Subject: Re: install.sh is wrong with libc.so
Date: Wed, 15 Jan 2014 13:58:39 +0100	[thread overview]
Message-ID: <20140115135839.6856a21c@mopad> (raw)
In-Reply-To: <da7baff3-ca15-4883-9e71-6aaa3bd2f20b@email.android.com>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

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= 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.
> 
> 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.
> 

see above answer.

Cheers,
Chris

-- 
PGP Fingerprint: F96B A15F DF25 2B3E 49CB BA16 241B F3E7 52FE AFC6

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-01-15 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  8:42 orc
2014-01-15 11:01 ` Laurent Bercot
2014-01-15 11:35 ` Christian Wiese
2014-01-15 11:52   ` orc
2014-01-15 12:58     ` Christian Wiese [this message]
2014-01-15 12:13 ` Szabolcs Nagy
2014-01-15 12:48   ` orc
2014-01-15 14:18     ` Szabolcs Nagy
2014-01-15 16:31     ` Rich Felker
2014-01-16  1:34       ` orc

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140115135839.6856a21c@mopad \
    --to=chris@opensde.net \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).