Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Oh hey, any chance you could explain this bit of the /usr/bin/google-chrome script I've always wondered about? (Sadly, the bug is RVG.)

   # Sanitize std{in,out,err} because they'll be shared with untrusted child
   # processes (http://crbug.com/376567).
   exec < /dev/null
   exec > >(exec cat)
   exec 2> >(exec cat >&2)
Somehow child processes can abuse stdin/stderr/stdout in ... creative ways?


Funny. /usr/bin/chromium shows nothing like that.

I'm wondering why these launchers differ so much.


/usr/bin/google-chrome is written by Google and analyzed by the security team. /usr/bin/chromium is written by enthusiasts (the distro's package author).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: