From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C7BEEC433E1 for ; Tue, 18 Aug 2020 18:35:54 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 938732075E for ; Tue, 18 Aug 2020 18:35:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=crudebyte.com header.i=@crudebyte.com header.b="QDCrLb1T" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 938732075E Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=crudebyte.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:49464 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k86Sf-00059Z-RT for qemu-devel@archiver.kernel.org; Tue, 18 Aug 2020 14:35:53 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:47728) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k86Ry-0004fv-Be for qemu-devel@nongnu.org; Tue, 18 Aug 2020 14:35:12 -0400 Received: from lizzy.crudebyte.com ([91.194.90.13]:38095) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k86Rv-0007SP-Hm for qemu-devel@nongnu.org; Tue, 18 Aug 2020 14:35:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=crudebyte.com; s=lizzy; h=Content-Type:Content-Transfer-Encoding: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From: Content-ID:Content-Description; bh=jHswqOFl1IQcLDf8WMR19s5FKomkcxXrdfdxRjBNoyc=; b=QDCrLb1Ty4oPvu8yaD49ErZU74 +hfYe7XiuQegt+yyrOHYnaGwJOf2uFjpXB7KLgwM8BYg8tuWIc5d3BYTNqZYUwBKGDeqKmMlGJiP7 wa9LEkb7sg9fFf85lBK5DBk/3N41XUapHIDPWKEcOz5L2stkT7QxpHcBG2VV2hv+5T71YE/+O9RmC kccJO/bNPwk2/96WBBKKozRB2PWxgti4fjMJAj0laM4e4r7Bqg+nTYpemLEmFMTv8DYdFmdWhs4wL ZzpE+kfnJbpVxEEfZNPbB5onnsmT8FiyTRK8AqEy0DTjT0johprUbr4JPt9MwQWHWdlFrMRK6ixPq s/6rGoGw==; From: Christian Schoenebeck To: qemu-devel@nongnu.org Cc: David Vossel , Michal Privoznik , Fabian Deutsch Subject: Re: guest agent public ssh key add/remove support? Date: Tue, 18 Aug 2020 20:35:02 +0200 Message-ID: <2310267.m5nKHIMqSz@silver> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Received-SPF: pass client-ip=91.194.90.13; envelope-from=qemu_oss@crudebyte.com; helo=lizzy.crudebyte.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/18 14:11:17 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Dienstag, 18. August 2020 15:25:56 CEST David Vossel wrote: > - Guest Agent SSH add/remove Support? > > As a PoC, I cobbled together some guest agent exec and file write client > commands which can technically achieve the desired result of > adding/removing entries in a /home//.ssh/authorized_keys file. It's a > little unwieldy, but it works. > > This got me thinking, an officially supported guest agent api for this ssh > key management would be really nice. There's already a somewhat related > precedent with the "guest-set-user-password" guest agent command. > > So here's the question. What would you all think about the guest agent API > being expanded with new commands for adding/removing ssh public keys from > authorized_keys files? There are two pass-through file systems in QEMU: 9pfs and virtiofs. Don't you think they would be sufficient for the use case? Best regards, Christian Schoenebeck