From nobody Tue Oct 21 22:31:27 2025 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 4crn8Y5yKcz6D7kV for ; Tue, 21 Oct 2025 22:31:41 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-ed1-f43.google.com (mail-ed1-f43.google.com [209.85.208.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4crn8Y3wkxz3Hlr for ; Tue, 21 Oct 2025 22:31:41 +0000 (UTC) (envelope-from asomers@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-f43.google.com with SMTP id 4fb4d7f45d1cf-63c4c346bd9so7399711a12.0 for ; Tue, 21 Oct 2025 15:31:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1761085900; x=1761690700; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Q2HUGododKemPYq62RqlOp86ikF59zkDk11Wr+nTkeY=; b=CORmlI8avOj84+Al8K6VQaw1BH6T8HkJPJkXQ/MNkOmMEQjv2LUYdQZ/nr8RJLwQw4 n8ffJF/YZsNwJJTogQz4Af3eOduRwO4Ww13SEiItfqD/6oQ4BA82OM3i4eb3i/b5yJeH G4kcSrSKR7Y999IMWJyHo/6pZOcaEAm6iakFoxma35Xf9GRvBVzx3qYLG4O7OLpPQDbC dJxhgTUmTsjP9Y3XiBJ0/iKJYk0eNMM+1OvOIwM9QjCejs+GRwZUCr19WLazvL7akk4+ skfdg/sWHmOge4Yt94dncB62sVz84iFwVnAiXZ3L22cOiyOpPAVhfBF+6lq4GFv67GRe hJGQ== X-Gm-Message-State: AOJu0YycmKPTbg3gXSPk2VEREdY3AiU+JzUfV2UCv2dlM+W1mRnotPaJ nFOlRDtFYGrfmJhdCxuMixP6igymp2OHEiwcCY4GLaHXbq7cdLV7ItC3XSD8k1MIuRTXaZHmMPy 1K/igEZ1hossylyNze8ptoiwejZGBEagsPA== X-Gm-Gg: ASbGnctCWpbscKrR5mexk3yM8AgcN4MVFlMnsqvcGpE6ZhfqlxW3xfX6kHKGRqpCGuG /2Ez0dlJ33+qWsnJ0IyHR3JxuxlakaOwa4bLIyYErk0PwExdBPRA2Bc93eXFfTKt5peHgx5JK88 6o2j9rfTz+xLKiOBpDU7E+mtQ5jVUtGsqJnHcfyLYcLqZ3zxk+iyPt4aWFUXozRz5YipVS+DZ84 iUDTEGJcYz1B5LPmUt6hhfbe0MWilJRZJml1RpPqchgTMqI/9oJU6ZJ0wHin0xBUWaZYDg= X-Google-Smtp-Source: AGHT+IG2pd+OYqQKJdSXoSfAb6xtEbyHDxy3dSXMkGtlXGyXWo3yHZPypfCuyt8Z/v89Gt/g6HL3Ro82ElmQnSD3rYs= X-Received: by 2002:a05:6402:2354:b0:639:dd3f:f27f with SMTP id 4fb4d7f45d1cf-63c1f626e94mr16752804a12.4.1761085899545; Tue, 21 Oct 2025 15:31:39 -0700 (PDT) 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 References: <08428s9n-72o9-28r1-22n6-rn0r885n62q0@fncre.vasb> In-Reply-To: <08428s9n-72o9-28r1-22n6-rn0r885n62q0@fncre.vasb> From: Alan Somers Date: Tue, 21 Oct 2025 16:31:27 -0600 X-Gm-Features: AS18NWAs0EaLZITLvYE8llA1gScX5QGT1ssWqsZGaP41BdZp31PeP6juULaHFGw Message-ID: Subject: Re: usbhid(4) breaks passkeys? To: Marcin Cieslak Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="00000000000076209b0641b2c363" X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4crn8Y3wkxz3Hlr --00000000000076209b0641b2c363 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Oct 21, 2025 at 4:25=E2=80=AFPM Marcin Cieslak w= rote: > Hello, > > I've just noticed that for some time that my USB passkey does not work > in my browser (Firefox). Setting sysctl hw.usb.usbhid.enable=3D0 and > re-attaching > the device (so it gets the "uhid" driver) fixes the problem: > > sbhid0: on > usbus0 > hidbus2: on usbhid0 > (** does not work **) > ugen0.4: at usbus0 (disconnected) > usbhid0: at uhub4, port 1, addr 21 (disconnected) > hidbus2: detached > usbhid0: detached > ugen0.4: at usbus0 > uhid0 on uhub4 > uhid0: on usbu= s0 > (** works **) > > This is an oldish FreeBSD 15 from August... > > Is this a known problem? > > Marcin I'm currently using a Yubikey on FreeBSD 14.3 with usbhid and it works fine. But these things have multiple functions. Maybe usbhid only breaks one. Which function are you using? I'm using PIV and GPG. --00000000000076209b0641b2c363 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Oct 21, 2025 at 4:25=E2=80=AFPM Marci= n Cieslak <saper@saper.info> = wrote:
Hello,
I've just noticed that for some time that my USB passkey does not work<= br> in my browser (Firefox). Setting sysctl hw.usb.usbhid.enable=3D0 and re-att= aching
the device (so it gets the "uhid" driver) fixes the problem:

sbhid0: <Nitrokey Nitrokey 3, class 239/2, rev 2.10/1.07, addr 21> on= usbus0
hidbus2: <HID bus> on usbhid0
=C2=A0 (** does not work **)
ugen0.4: <Nitrokey Nitrokey 3> at usbus0 (disconnected)
usbhid0: at uhub4, port 1, addr 21 (disconnected)
hidbus2: detached
usbhid0: detached
ugen0.4: <Nitrokey Nitrokey 3> at usbus0
uhid0 on uhub4
uhid0: <Nitrokey Nitrokey 3, class 239/2, rev 2.10/1.07, addr 22> on = usbus0
=C2=A0 (** works **)

This is an oldish FreeBSD 15 from August...

Is this a known problem?

Marcin

I'm currently using a Yubikey on= FreeBSD 14.3 with usbhid and it works fine.=C2=A0 But these things have mu= ltiple functions.=C2=A0 Maybe usbhid only breaks one.=C2=A0 Which function = are you using?=C2=A0 I'm using PIV and GPG.
--00000000000076209b0641b2c363--