Observed behaviour: $ env - bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:. $ Expected behaviour: $ env - bash -c 'echo $PATH' /usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin $ dash gets this right. Tagging this "important" because having . on the path is a security hazard which we mostly got rid of everywhere. Having . come back in unusual situations where bash makes up the PATH is quite unexpected and surely not desirable.
Hi Ian, I guess we can merge this one with #781367, doing so now. Regards, Salvatore