summaryrefslogtreecommitdiff
path: root/readconf.c
diff options
context:
space:
mode:
authorColin Watson <cjwatson@debian.org>2014-02-09 16:09:58 +0000
committerColin Watson <cjwatson@debian.org>2020-02-21 12:06:07 +0000
commit3309e464e5ae6c940ddd584eed4d2d403f4c168c (patch)
treecba1516165e10e7095ab30cf8100644059865217 /readconf.c
parent387c2c1954773733bae9fca21a92db62c31180bd (diff)
Allow harmless group-writability
Allow secure files (~/.ssh/config, ~/.ssh/authorized_keys, etc.) to be group-writable, provided that the group in question contains only the file's owner. Rejected upstream for IMO incorrect reasons (e.g. a misunderstanding about the contents of gr->gr_mem). Given that per-user groups and umask 002 are the default setup in Debian (for good reasons - this makes operating in setgid directories with other groups much easier), we need to permit this by default. Bug: https://bugzilla.mindrot.org/show_bug.cgi?id=1060 Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=314347 Last-Update: 2019-10-09 Patch-Name: user-group-modes.patch
Diffstat (limited to 'readconf.c')
-rw-r--r--readconf.c3
1 files changed, 1 insertions, 2 deletions
diff --git a/readconf.c b/readconf.c
index 2399208f8..7f251dd4a 100644
--- a/readconf.c
+++ b/readconf.c
@@ -1902,8 +1902,7 @@ read_config_file_depth(const char *filename, struct passwd *pw,
1902 1902
1903 if (fstat(fileno(f), &sb) == -1) 1903 if (fstat(fileno(f), &sb) == -1)
1904 fatal("fstat %s: %s", filename, strerror(errno)); 1904 fatal("fstat %s: %s", filename, strerror(errno));
1905 if (((sb.st_uid != 0 && sb.st_uid != getuid()) || 1905 if (!secure_permissions(&sb, getuid()))
1906 (sb.st_mode & 022) != 0))
1907 fatal("Bad owner or permissions on %s", filename); 1906 fatal("Bad owner or permissions on %s", filename);
1908 } 1907 }
1909 1908