From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3DD6A3857B88; Fri, 16 Feb 2024 17:53:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3DD6A3857B88 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1708105999; bh=kWZg0KJypi1l7zU6Wvurs+VzPS6dOBNtZUpmlqXdjtg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ssssyY0URs2CfnjuMf71jNMoFqvCTOVb6tSPZFQ0BMw60Vc5uR6qKscipqW00gI8B Re8GVTz96la9N7e08uI7Pb6yCZHdwNf323TzbV6FBS/9Lx5Qg+H40ybBiZhnZU+HRh 2621bD0kbn6z1mt13G3c4CY+6vqislkyFHyBOt+4= From: "pedro at palves dot net" To: gdb-prs@sourceware.org Subject: [Bug server/30453] gdbserver cannot set breakpoints when /proc/pid/mem is not writable Date: Fri, 16 Feb 2024 17:53:18 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: server X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: pedro at palves dot net X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30453 --- Comment #20 from Pedro Alves --- Thanks, I've commented on the CrOS ticket. > Eventually in 2011 the upstream kernel allowed writes to mem citing "ther= e is no longer a security hazard" in commit [2], which was incorrect becaus= e CVEs and drama ensued [3], which apparently continues to this day. So there was a CVE over a decade ago and it was fixed then. Because there = used to be a bug, and it is now fixed, we should still consider allowing a debug= ger to access memory using the interface bad? That, doesn't compute to me. Bu= gs happen, and they are fixed. There is nothing in the interface that prevent= s it from being hardened, _and_ still allows debuggers to use it. > I can't be the judge of what GDB supports or not, but perhaps if I get th= e kconfig=20 > options to restring /proc/pid/mem upstreamed in the mainline kernel, that= would help=20 > settle the matter? :) Sounds like blackmail. :-P --=20 You are receiving this mail because: You are on the CC list for the bug.=