Date: Tue, 1 Jun 2021 23:22:32 +0200 From: =?UTF-8?Q?Mikl=c3=b3s_Quartus?= <qmi@foresthacker.hu> To: freebsd-security@freebsd.org Subject: Re: sysrc bug Message-ID: <242de1fa-ccd5-c9d6-4b2e-330ac9dcc152@foresthacker.hu> In-Reply-To: <E8315698-19C7-46FB-AD46-CD61057FECD7@tetlows.org> References: <s2s2o821-3n23-6811-2020-s172porqps6n@mx.roble.com> <E8315698-19C7-46FB-AD46-CD61057FECD7@tetlows.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/1/21 5:54 AM, Gordon Tetlow via freebsd-security wrote: > Surprised this old myth is still being repeated. Having used various >> root shells in FreeBSD and other Unux/Linux systems for decades I have to >> ask specifically what said reasons are, particularly considering >> /usr/sbin/sysrc starts with "#!/bin/sh" (as does and should every system >> shell script). > It’s likely due to the quoting behavior of newlines passed as the argument when he ran the script, which varies between shell implementations. As I said, I’m not surprised something broke because many utilities are not tested with different shell behaviors. > > I also believe if we have a reproducible test case, we should go ahead and fix it. > > Gordon I have Bash shell in my root terminal (did not change the default shell, just type 'bash -l' from the default csh) and I could not reproduce this error on 13.0-RELEASE . The rc.conf remains fine showing just the expected changes. -- Regards, Miklós GPG fingerprint: 3C4B 1364 A379 7366 7FED 260A 2208 F2CE 3FCE A0D3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?242de1fa-ccd5-c9d6-4b2e-330ac9dcc152>