Date: Sat, 07 Dec 2024 03:37:33 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 283110] freebsd-update IDS vs. installed permissions for kernels (444 vs 555) Message-ID: <bug-283110-227-rYrfQhp6f2@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283110-227@https.bugs.freebsd.org/bugzilla/> References: <bug-283110-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283110 --- Comment #3 from wbe@psr.com --- (In reply to Mark Johnston from comment #1) Doing a chmod 444 is easy enough. I didn't because I wasn't (previously) 1= 00% sure doing so was OK, especially on the kernel file itself which something obviously runs. You say it's OK, then I'm happy. Maybe I'm missing something obvious, but how is it that permissions are get= ting preserved by upgrade? I would have expected removing/moving/archiving the = old copies, then creating new files would produce files with the appropriate new permissions. Instead, it seems like something is going to extra effort to preserve the old permissions. ctl.ko, for example, is 555 even though it w= as one of the updated files. Maybe this a security thing in case the new permissions are greater (e.g., 555 if previously 444)? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283110-227-rYrfQhp6f2>