Blame SOURCES/0115-cryptsetup-generator-remove-warning-about-crypttab-a.patch

17b0f1
From d066c82a5a5c63c50617be27409ae0bb4bd3a356 Mon Sep 17 00:00:00 2001
17b0f1
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>
17b0f1
Date: Sat, 14 Mar 2015 22:35:30 -0400
17b0f1
Subject: [PATCH] cryptsetup-generator: remove warning about crypttab access
17b0f1
 mode
17b0f1
MIME-Version: 1.0
17b0f1
Content-Type: text/plain; charset=UTF-8
17b0f1
Content-Transfer-Encoding: 8bit
17b0f1
17b0f1
This file contains no privileged data — just names of devices to decrypt
17b0f1
and files containing keys. On a running system most of this can be inferred from
17b0f1
the device tree anyway.
17b0f1
17b0f1
(cherry picked from commit 71e4e1258436e7e81d772aed52a02bb5d9c87cb8)
17b0f1
---
17b0f1
 src/cryptsetup/cryptsetup-generator.c | 7 -------
17b0f1
 1 file changed, 7 deletions(-)
17b0f1
17b0f1
diff --git a/src/cryptsetup/cryptsetup-generator.c b/src/cryptsetup/cryptsetup-generator.c
17b0f1
index dfbca8754f..d191def5f8 100644
17b0f1
--- a/src/cryptsetup/cryptsetup-generator.c
17b0f1
+++ b/src/cryptsetup/cryptsetup-generator.c
17b0f1
@@ -377,13 +377,6 @@ static int add_crypttab_devices(void) {
17b0f1
                 return 0;
17b0f1
         }
17b0f1
 
17b0f1
-        /* If we readd support for specifying passphrases
17b0f1
-         * directly in crypttab we should upgrade the warning
17b0f1
-         * below, though possibly only if a passphrase is
17b0f1
-         * specified directly. */
17b0f1
-        if (st.st_mode & 0005)
17b0f1
-                log_debug("/etc/crypttab is world-readable. This is usually not a good idea.");
17b0f1
-
17b0f1
         for (;;) {
17b0f1
                 int r, k;
17b0f1
                 char line[LINE_MAX], *l, *uuid;