Hacker News Reader

Comment by gruez | Hacker News Reader

This but unironically. There's no way to ensure that nobody overwrote your .profile or .bashrc with a backdoored sudo that steals your password, or runs your command and then runs an evil command afterwards.

View on HN

`which sudo`?

`/usr/bin/sudo`?

If they can override sudo, they can override which.

if you use \which it'll always be a shell built-in ;) though someone can put a different shell in your .zshrc

  $ which() { echo foo; }
  $ \which
  foo

The backslash only prevents alias expansion.

He meant `command which`

> it'll always be a shell built-in

`command which` wouldn't have been the built-in

`exec /tmp/fake-bash` in bashrc to intercept everything?

Then use the absolute path.

Reply on news.ycombinator.com