From nobody Fri May 20 10:57:41 2022 X-Original-To: chromium@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 659F21AEBC64 for ; Fri, 20 May 2022 10:57:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L4Nwj0vwVz4jvV for ; Fri, 20 May 2022 10:57:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 003AA110D7 for ; Fri, 20 May 2022 10:57:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 24KAveG9096816 for ; Fri, 20 May 2022 10:57:40 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 24KAvewL096815 for chromium@FreeBSD.org; Fri, 20 May 2022 10:57:40 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 263790] www/chromium: Unable to use FIDO U2F Date: Fri, 20 May 2022 10:57:41 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: peterj@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: FreeBSD-specific Chromium issues List-Archive: https://lists.freebsd.org/archives/freebsd-chromium List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-chromium@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1653044261; 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=mP2quvScWErzVOwPiBf4ubk67NC9xss687Y0pf6tIPo=; b=fNlAG1ol8Vt7s4+wmgBD5JtJuH/iDW/TlqXhGD2lHcMvPWiexBMOOHnmPen2IDyM9gOrD4 CEu0fbb7IZe6OQSQJyMWH3jPsQGOcKNAt9+BMpYrmfuqksh8VPEcyM1MY5fOJFcz13mY3Q KrvHJ6PZfGWLErQwiLoWsy5OnY7JqM7eJJv5x1TKiVDOKvddp9ffl9iGdI9weFNGu68nDk 1x2xo/vld/FYba2PosTfDA+TTzH3EctiyX+JoKVWS5OsC9HkuNHaPkzgLzpd2vGug58hcW MZ1TStdLXf1twFcDKlkarbMy7gMLq/KMuWdzOMM+FQHslIu37FynI2gvl5V+Vg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1653044261; a=rsa-sha256; cv=none; b=aTrPlVFPZjX/hQK9ExWO75fjLS1nFSdxpP8mtUKuDfpDSsOEDiAY6Gz2/PptxnsF4mHVry Qqmjarv3i+djJq3cLlQh5ysHJGDSmtxFC6EA+az0RwxHzZ83g2cAzDrl4t+7Gc5ohxnW/d MMcth96zxUopdFhqS/UwjV29qHZceOtoGlg6kNzR3utnpYpdbRg+9MJNbRu/16ec1Nb3GF J5vE0+p5/Rzjvn2iT1Bi4xPQae5cABghkskMLcqb3f5t2ghOSLrBgaL7ddmu6De9+6R57U PniiXYqk4ubH3DDsEXPYrNmWia6Cv3qaFNyDhqr4lMDc+6vyPGuKA3rwQgsABQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263790 Peter Jeremy changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|www/chromium: Unable to |www/chromium: Unable to use |login to Google after |FIDO U2F |upgrade to 101.0.4951.54 | --- Comment #13 from Peter Jeremy --- I've tried disabling my Yubikey and using an alternative 2FA method and I c= an login to Google successfully. This is a regression because Chromium 99.x allowed me to choose a 2FA method whereas Chromium 100.x doesn't bring up t= he menu allowing me to choose an alternative. I've tried attempting to add a security key via Chromium. Working through,= it reaches a popup that just spins, with or without the key installed: " Add a security key You=E2=80=99ll see instructions in your browser window for adding your key = to your account " I do regularly use a security key with Chrome (on Linux) but don't have any non-FreeBSD systems that I can easily test Chromium on. I've tried using my security key to login to Github using Chromium on FreeB= SD and it also fails in a similar way: It spins waiting for the security key. = I'm not sure if this is a regression because I haven't tried it previously. I've tried doing some ktrace'ing and Chromium isn't attempting to even look= for a security key in either case: In my case, the security key appears as /dev/uhid1 but: * in the github login case, there are no accesses to /dev. * in the Google "add a key" case, only /dev/null and /dev/urandom are acces= sed. OTOH: * in both cases, there are a number of access attempts to /sys/class/input/event* - which might make sense on Linux, but not FreeBSD. * during a ktrace of Chromium starting, I did find an unsuccessful access attempt to /dev/fido - despite the name, that's actually the interface to watchdog(4). I couldn't find the code that does that. --=20 You are receiving this mail because: You are the assignee for the bug.=