> On May 31, 2021, at 16:07, Roger Marquis <marquis at roble.com> wrote: > > ? >> >> Also, changing the root shell is bad for many reasons and I'm not >> surprised that something doesn't work. > > 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
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. > > GordonI 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