From 7fd5226a97ea9161382384b1fa6c6b329933ad27 Mon Sep 17 00:00:00 2001
From: Joshua Peraza <jperaza@chromium.org>
Date: Wed, 27 Nov 2019 11:49:15 -0800
Subject: [PATCH] Give database settings kOwnerOnly permissions

Bug: b/145240822
Change-Id: Id3720471ce67edd981c35b62cf1d8f810899646c
Reviewed-on: https://chromium-review.googlesource.com/c/crashpad/crashpad/+/1940848
Reviewed-by: Mark Mentovai <mark@chromium.org>
---
 client/settings.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/client/settings.cc b/client/settings.cc
index f6db78db..db9dface 100644
--- a/client/settings.cc
+++ b/client/settings.cc
@@ -226,10 +226,10 @@ Settings::ScopedLockedFileHandle Settings::OpenForReadingAndWriting(
   FileHandle handle;
   if (log_open_error) {
     handle = LoggingOpenFileForReadAndWrite(
-        file_path(), mode, FilePermissions::kWorldReadable);
+        file_path(), mode, FilePermissions::kOwnerOnly);
   } else {
     handle = OpenFileForReadAndWrite(
-        file_path(), mode, FilePermissions::kWorldReadable);
+        file_path(), mode, FilePermissions::kOwnerOnly);
   }
 
   return MakeScopedLockedFileHandle(