Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 May 2021 20:43:01 +0700
From:      Eugene Grosbein <eugen@grosbein.net>
To:        Fas Xmut <fasxmut@protonmail.com>, "freebsd-security@freebsd.org" <freebsd-security@freebsd.org>
Subject:   Re: sysrc (awk) bug
Message-ID:  <ae413c70-4fdc-f65c-1757-b1473c1a21b7@grosbein.net>
In-Reply-To: <0J-hkv9PO-ZfjHO2kiEVatVRNdz0xTZ8pDMOvPreE53RFRsgyWHnU0U1IPO-mxNmswiB5KyGgO067-gLMA0PfW4Py3bBYllvQCBMTc2T8QE=@protonmail.com>
References:  <0J-hkv9PO-ZfjHO2kiEVatVRNdz0xTZ8pDMOvPreE53RFRsgyWHnU0U1IPO-mxNmswiB5KyGgO067-gLMA0PfW4Py3bBYllvQCBMTc2T8QE=@protonmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
30.05.2021 11:36, Fas Xmut via freebsd-security wrote:

> I don't know if it is a security bug or not. When I use sysrc today, the error operations emptied my /etc/rc.conf, that's a small disaster, because my /etc/rc.conf is updated day by day, but now, it is empty.
> 
> First, change your default root shell to sh/ksh or their derived shell. (I have tested, csh will not trigger that bug).
> 
> Second, backup /etc/rc.conf to any other place.
> 
> Then do the following commands:
> 
> ------------------------------------------------------------------------
> # sysrc something_enable="NO"
> # sysrc something_enable="YES
>> "
> awk: newline in string YES
> ... at source line 1
> something_enable: NO -> YES
> ------------------------------------------------------------------------
> 
> Now see what is inside /etc/rc.conf ? Everything is empty! only one thing in it:
> 
> ------------------------------------------------------------------------
> something_enable="YES
> "
> ------------------------------------------------------------------------

What is your FreeBSD version?





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ae413c70-4fdc-f65c-1757-b1473c1a21b7>