From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 0NqiL842SWVM6T8AWB0awg (envelope-from ) for ; Mon, 06 Nov 2023 13:56:14 -0500 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=iel82Nj6; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id BF31B1E098; Mon, 6 Nov 2023 13:56:14 -0500 (EST) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id A87FC1E00F for ; Mon, 6 Nov 2023 13:56:12 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 577123858401 for ; Mon, 6 Nov 2023 18:56:12 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 63C103858D20 for ; Mon, 6 Nov 2023 18:56:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 63C103858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 63C103858D20 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1699296962; cv=none; b=bxoTt7s4p/PsYmoK+RxICM7JFi61S+5gbdgmoR3pNsXzkD4tEXH5sL89NA8Il0bQmQGMaJQ6oTONHKn8SuDorBJtBMi2qxTTXGPDC0+yN5reoyHuDhA655QgMCD3mx8OIX0BGgcaiFnKcv2nkv64kFCYkFXUfBqx9akePOL3xJg= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1699296962; c=relaxed/simple; bh=Df4OjtA9Mcyc1/mbw3eznThEdDMtC8eq01k3GVaA8bo=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=IpPwyaNoyw1M85h+7Qy+FHO8wxeBav14hmbq7dmArWwbcf35aJi4xOMvTvSzVoenSNd6COfjBQk5f14g+8DiujT7xcDtxbiyiSNdT0nbfW34UfH9YbCd7C6y62k721O9QbqjoQjgbStmK901klfO6BDJrlJMfS99vW6uhIhBgu8= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1699296960; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Go78Pm5kSKTSdFUSCt4GYL5zVsy/dHss9BBoDlq/6Sw=; b=iel82Nj62Vy+RPYWwJg08YE2OUoQwuAmPIUylubpaietr8JVC+uVOdfCbTWeq6Iyf2VXK+ l07ItvPpDekVU/8RWFPdbpl59ESqaQ0VLucCvehbBriGP/JSG3/rQ5blvgNFCl7oJP4tjc tzuDWD9k0kTLb/5itE01XIJAjvWm3ng= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-381-qtRP51nUOmC3fAIIW4eg9Q-1; Mon, 06 Nov 2023 13:55:38 -0500 X-MC-Unique: qtRP51nUOmC3fAIIW4eg9Q-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 20FD98966A9 for ; Mon, 6 Nov 2023 18:55:38 +0000 (UTC) Received: from f38-zws-nv (unknown [10.22.16.59]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AAA0B2166B26; Mon, 6 Nov 2023 18:55:37 +0000 (UTC) Date: Mon, 6 Nov 2023 11:55:36 -0700 From: Kevin Buettner To: Andrew Burgess Cc: gdb-patches@sourceware.org, Siddhesh Poyarekar Subject: Re: [RFC] Adding a SECURITY policy for GDB Message-ID: <20231106115536.084239ef@f38-zws-nv> In-Reply-To: <877cmvui64.fsf@redhat.com> References: <877cmvui64.fsf@redhat.com> Organization: Red Hat MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org On Mon, 06 Nov 2023 13:26:27 +0000 Andrew Burgess wrote: > I'd be interested to hear: > > * Do people feel I'm being too restrictive in what I consider a > security issue? Are there any additional classes of bug that you > would see as a security issue within GDB? > > * I've tried to highlight areas of GDB that might pose a risk if run > in a non-secure setting, e.g. GDB run the inferior, so using GDB to > debug unknown inferiors can allow arbitrary code execution, or that > gdbserver on an open network would allow access to the machine > running gdbserver. Are there any other areas of GDB for which we > should list as being potentially dangerous if not run in a secure > (sandboxed) environment? Some crash detection/analysis tools use GDB in an automatic fashion to provide diagnostics. I think it should be made clear that such tools should use GDB in a sandboxed environment. Kevin