From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists1p.gnu.org (lists1p.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3FD13606A31C for ; Tue, 17 Nov 2026 16:01:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=g3srppaC Received: from localhost ([::1] helo=lists1p.gnu.org) by lists1p.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1xTLbt-0006ra-TW; Tue, 17 Nov 2026 11:00:42 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1xTLbe-0006lz-C0 for qemu-devel@nongnu.org; Tue, 17 Nov 2026 11:00:28 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1xTLbb-0000OW-Kj for qemu-devel@nongnu.org; Tue, 17 Nov 2026 11:00:25 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1794931220; h=from:from:reply-to: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=XzBgYDMDQpnl6Of9lphOKltuNVvUSB9EE0MvS8bnoIo=; b=g3srppaCrG5tp7QnMZ7vYLEq4rPCSmSQZB4iE2eIfc+jt24U6007vqkG6EfvUY8PQIiAd7 U6DeZ6LPNQx99SzAdA7k7972FENErcM1SVPKyqj00cOCDCWDba1Y1GVAEC9YEqEDY687Ld DBepdNCgpmPgzif8S8pNMJ2Ta6mqHh0= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-584-cvLsVVhKPP6jErREenZr0Q-1; Tue, 17 Nov 2026 11:00:16 -0500 X-MC-Unique: cvLsVVhKPP6jErREenZr0Q-1 X-Mimecast-MFC-AGG-ID: cvLsVVhKPP6jErREenZr0Q_1794931215 Received: from mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.93]) (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 mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 48D831800547; Tue, 17 Nov 2026 16:00:15 +0000 (UTC) Received: from redhat.com (headnet04.pony-001.prod.iad2.dc.redhat.com [10.2.32.116]) by mx-prod-int-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 7165C18011F4; Tue, 17 Nov 2026 16:00:14 +0000 (UTC) Date: Tue, 17 Nov 2026 16:00:11 +0000 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Mark Cave-Ayland Cc: qemu-devel@nongnu.org Subject: Re: System emulator security boundary policy now enforceable Message-ID: References: X-Archived-By: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/2.4.3 (2026-10-09) X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.93 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: qemu development List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Sender: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org X-Spam-Status: No, score=-7.3 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=4.0.1 X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on aws-us-west-2-korg-listserv-alma10-1 On Tue, Nov 17, 2026 at 10:32:51AM +0000, Mark Cave-Ayland wrote: > On 17/11/2026 10:09, Daniel P. Berrangé wrote: > > > With the latest pull request of mine that is merged, we now have > > the mechanism for enforcement of the QEMU security boundary policy > > with annotations completed across QOM classes for machine types, > > devices and accelerators. > > > > For a bug disclosure affecting a system emulator to be accepted > > as a security flaw the reproducer scenario must now pass without > > warnings when adding the '-compat insecure-input' flag. > > > > For example: > > > > $ qemu-system-x86_64 -compat insecure-input=warn > > qemu-system-x86_64: warning: Insecure QOM type tcg-accel accepted by policy > > > > $ qemu-system-x86_64 -compat insecure-input=warn -machine isapc -device ne2k_isa > > qemu-system-x86_64: warning: Insecure QOM type isapc-machine accepted by policy > > qemu-system-x86_64: warning: Insecure QOM type tcg-accel accepted by policy > > qemu-system-x86_64: -device ne2k_isa: warning: Insecure QOM type ne2k_isa accepted by policy > > > > Alternatively you can have QEMU crash on the first violation > > > > $ qemu-system-x86_64 -compat insecure-input=reject -machine isapc -device ne2k_isa > > qemu-system-x86_64: Insecure QOM type isapc-machine disabled by policy > > This type does does not provide a security boundary to protect against untrusted data or actions > > > > > > When triaging an incoming disclosure affecting system emulators > > please use this mechanism as the primary guide for whether to > > handle it as a security flaw with a CVE assignment request, or > > merely a normal public bug. > > > > This mechanism is intended as authoritative, while the security.rst > > docs describing virtualization vs non-virtualization use cases are > > merely a high level approximation. > Hurray! What is the best way to update AGENTS.md and friends accordingly to > take advantage of this? Presumably we at least need to tell the agent that > only reproducers within the security boundary should be considered > "Confidential". > > Unfortunately I'm not sure we can go as far as telling the agent not to > raise a GitLab issue unless it lies within the security boundary, otherwise > we risk still missing some useful bug reports. So the onslaught continues... I guess if we at least tell the agent to use the new arg "-compat insecure-types=reject" in their reproducers, they'll avoid creating confidential issues for those non-virt scnearios, and their comments will hopefully show that they included this arg. Won't cut down the bug count, but will marginally reduce the triage work as we won't need to manually turn off confidentiality and explain this to users over and over and over again. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|