Script to check for blacklisted files as described in chrome-os-partner:1991

scripts/image_signing/ensure_no_nonrelease_files.config

Index: scripts/image_signing/ensure_no_nonrelease_files.config
diff --git a/scripts/image_signing/ensure_no_nonrelease_files.config b/scripts/image_signing/ensure_no_nonrelease_files.config
new file mode 100755
index 0000000000000000000000000000000000000000..32a8a7237cf059e2018cff6e06e9bf2ab19ac4a0
--- /dev/null
+++ b/scripts/image_signing/ensure_no_nonrelease_files.config
@@ -0,0 +1,13 @@
+#!/bin/bash
+
+# Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# Files/directories that should never be present in a clean,
+# standard release build. 
+RELEASE_FILE_BLACKLIST=(

[gauravsh, 2011/01/28 01:27:04]

also, it might be nice if you could add comments on why each of these are bad in
a release image. This will be useful as the list grows in the future and or we
make modifications.

+/root/.dev_mode
+/opt/google/chrome/localaccount
+/home/.shadow
+)

[gauravsh, 2011/01/28 01:27:04]

Another blacklist (fine to do it in a separate CL) are the list of files that
should exist or not exist for a final signed image.

Some examples: 
/usr/bin/crosh-workarounds must always exist
/root/.force_update_firmware must always exist

We can run this on the final signed image. This will serve as a final sanity
check and help us catch regressions in the signer.