From: Gustavo Guillermo <gustavo@compunauta.com>
To: terry white <twhite@aniota.com>,
linux-admin <linux-admin@vger.kernel.org>
Subject: Re: bash replacement ...
Date: Thu, 11 Dec 2014 22:40:55 -0600 [thread overview]
Message-ID: <548A71D7.8010908@compunauta.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1412111746080.14812@yossarian>
You've to rename the running binary instead of replacing it but in one
single execution, so later you can delete the old one.
for example:
mv /bin/bash /bin/bash.orig; cp /usr/src/bash_source/build/bash
/bin/bash; chmod 755 /bin/bash
try it..
Cheers.
On 11/12/14 19:56, terry white wrote:
> ... ciao:
>
> when the bash vulnerability was announced i built the 'new'
> patched version. in my case, two. though, not automatic, not really
> problematic.
> however, when i tried to replace the running 'bash', the system
> disallowd that operation.
>
> so, i booted a rescue system, and did the replacement that way.
>
> is there a way i could have done that on the native system ?
>
> thanks ...
>
>
next prev parent reply other threads:[~2014-12-12 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 1:56 bash replacement terry white
2014-12-12 4:40 ` Gustavo Guillermo [this message]
2014-12-13 0:49 ` terry white
2015-01-13 8:34 ` Marian Marinov
2015-01-13 9:41 ` terry white
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=548A71D7.8010908@compunauta.com \
--to=gustavo@compunauta.com \
--cc=linux-admin@vger.kernel.org \
--cc=twhite@aniota.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).