From nobody Mon Jan 08 16:35:03 2024 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T80610Frtz56Ggs for ; Mon, 8 Jan 2024 16:35:05 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T80606xJgz4ZWk for ; Mon, 8 Jan 2024 16:35:04 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704731705; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CAT/0q2wb1BRQw1OoVfsiBGcWHvKkVofeAOq5ajY9jY=; b=xnHswkXt1LnUo+kqbxOwU2/yYhLJiNYjz2kFVa5khkm1uXoSWIL+fVulAbMKUc0q7fihud gKb4CIHurCjCVWgKdKctb3ew9jTjZ8//tEJ7nUyzgqZj397m1rG5qy8BVmUYbSxq/TgS9R iudEYtJPZ8qnCCgcJ3nM0wtYU0T7qaweKK1XGU08qkaEW7v/rYYhe0JcVWqIMXpZovU53M LOBxK+p83aWAv1E9xMS00NEx5o8FPQQaj2owcwIyPogJ6WrC2Qd0OkhhJOcLO87kA4rDTc 2HdPv0ZYcf51mr0Wv2iA4UO9J4+vp/6ivTAZ0OkTGp5CPcMF4NP9LluWkypRFw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704731705; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CAT/0q2wb1BRQw1OoVfsiBGcWHvKkVofeAOq5ajY9jY=; b=BeYZymkyaNR4OG7Q9nNLK3Vuhy7GvcT2Ae1TXwJ/HKKfF74Lly7wqaoVZYSsYoAOuBzZFi 0LSHFhJE7ojgp+abz/dpineYni2SPNjND1br1+t7o85xKkijJypmwoOs/OlA8erFRXvs06 p+IGYLHERZg4PuDGK+3cTTHfGXOtSmZ7HNTLSU7G9bvpbJbNzVfgoi/7L+mveHJcSWtH/P iO8/vFEez2OQQPPqXEckEM+IgJvgZ4Pengex6kmAl7T8uOExkkMwvTgkuTQJCnIAq2hf+s Z9CpNU9MIfjUkfAk96u4BZNa+ypeps95rTNdYU5ooZQATFn2mA2oSjHpsMPzBA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1704731705; a=rsa-sha256; cv=none; b=aAaZEO8P48v9ezutWCvowJrWZ91dwaebVZIqGe9T4CrzdjNUIhwvrb1FnKVYmEVY3icCg9 CD0vXPAFsZ368l7yAwICCTttXdfWnALuA0ZrnhDolTNfLtVfSB7iHTg2gRfy/nw+05/r/t X/Pnkgl6TFJbW7HmQGxLKDzRou8E+uxRoz51tZqj2z+WSP4rVXk3RtYowS0xwtC7nshryg X9D9Kdj9da+dzaXlknr+5J1zYM9GbamcJdE/FZIpgE4vBT9eTaOBIkCPehCcbUTLu/Uwvu eyu+yKONZkwVbW1SfeWPfpbKXjAJ16PD8wRCI4K5+oGTdvxZcrRvzQEx+6rxJQ== Received: from [10.9.4.95] (unknown [209.182.120.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4T80603z8dz19rB for ; Mon, 8 Jan 2024 16:35:04 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: Date: Mon, 8 Jan 2024 10:35:03 -0600 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Move u2f-devd into base? Content-Language: en-US To: freebsd-current@freebsd.org References: <20240109013058.22807f3816603829316cef4c@dec.sakura.ne.jp> From: Kyle Evans In-Reply-To: <20240109013058.22807f3816603829316cef4c@dec.sakura.ne.jp> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 1/8/24 10:30, Tomoaki AOKI wrote: > On Mon, 8 Jan 2024 08:18:38 -0700 > Warner Losh wrote: > >> On Mon, Jan 8, 2024, 7:55〓AM Christian Weisgerber >> wrote: >> >>> We have FIDO/U2F support for SSH in base. >>> >>> We also have a group "u2f", 116, in the default /etc/group file. >>> >>> Why do we keep the devd configuration (to chgrp the device nodes) >>> in a port, security/u2f-devd? Can't we just add this to base, too? >>> It's just another devd configuration file. >>> >> >> This properly belongs to devfs.conf no? Otherwise it's a race... >> >> Warner >> >> -- >>> Christian "naddy" Weisgerber naddy@mips.inka.de > > It's devd.conf materials. It actually is security/usf-devd/files > u2f.conf and its contents is sets of notify 100 { match "vendor" ... > match "product" ... action "chgrpy u2f ..." };. > Some hase more items in it, though. > > So it should be in ports to adapt for latest products more quickly than > in base, I think. > I don't see any obvious reason that we can't compromise and have a baseline of products in base and just use the port for new products not yet known to base. These vendors presumably aren't going to quickly repurpose some PID for a non-u2f thing, much less in a way that we care about. Thanks, Kyle Evans