Use NoNewPrivs for daisydog.

Doesn't look like daisydog is launching anything that requires to
elevate privilege.

BUG=chromium:730623
TEST=security_SandboxedServices.

Change-Id: Ia6ea273c543c2e4a9bd9d7dd0e49142d2e08640a
Reviewed-on: https://chromium-review.googlesource.com/527817
Commit-Ready: Jorge Lucangeli Obes <jorgelo@chromium.org>
Tested-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
1 file changed
tree: 3ff9b64128ea344bf5e055d07cb5a47a6fc7cc09
  1. 51-watchdog.rules
  2. COPYING
  3. Makefile
  4. OWNERS
  5. PRESUBMIT.cfg
  6. README.md
  7. daisydog.c
  8. daisydog.conf
README.md

GPL Code is copied with explicit permission from Daniel Widyanto:
http://embeddedfreak.wordpress.com/2010/08/23/howto-use-linux-watchdog/

The project name is based on Samsung's “daisy” reference board design and I liked this quote from the daisy dog FAQ:

Daisy Dogs are not persnickety little ankle biters

When this daisydog doesn't run, the machine should reset. :)

An alternative code to start with would have been:
https://dev.openwrt.org/ticket/2270

The watchdog project is alot more complicated than what the Chromium OS project needs.