Nevermind, I hadn't realized you had filed bug #1851211 already. Let's
continue the discussion there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap]
Christoph, is your device a Yubikey? If not would you mind filing a new
bug report with all the details by running `ubuntu-bug chromium-browser`
?
The relevant denial seems to be:
[ 7049.256201] audit: type=1400 audit(1572541725.870:246):
apparmor="DENIED" operation="open"
I'm still facing this problem. I just switched to 19.10 and the snap package
has been installed. It does not work.
I tried to do the "snap connect chromium:u2f-devices" but this will not solve
the problem.
My dmesg out put shows a lot of DENIED:
audit: type=1107 audit(1572541712.846:243):
This bug was fixed in the package gnome-software -
3.20.5-0ubuntu0.16.04.12
---
gnome-software (3.20.5-0ubuntu0.16.04.12) xenial; urgency=medium
* debian/patches/0001-Fix-potential-crash-when-icons-are-missing.patch:
- Fix crash loading icons (LP: #1778135)
*
Tested gnome-software 3.20.5-0ubuntu0.16.04.12 and the u2f-devices
interface control is shown.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: gnome-software (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
--
You
Hello Olivier, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.5-0ubuntu0.16.04.12 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Changed in: gnome-software (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work
** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work with yubikey
Status
This bug was fixed in the package gnome-software -
3.28.1-0ubuntu4.18.04.9
---
gnome-software (3.28.1-0ubuntu4.18.04.9) bionic; urgency=medium
* debian/rules:
- Disable ubuntu-reviews plugin (use ODRS instead)
* debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch:
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu3
---
gnome-software (3.30.6-2ubuntu3) disco; urgency=medium
* debian/patches/0028-Added-u2f-devices-to-interfaces-UI.patch
- Allow connections on the u2f-devices interface (LP: #1738164)
(the patch has been
Tested gnome-software 3.28.1-0ubuntu4.18.04.9 and the u2f-devices
interface control is shown.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hello Olivier, or anyone else affected,
Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.9 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Description changed:
- (initially reported by Daniel at https://forum.snapcraft.io/t/call-for-
- testing-chromium-62-0-3202-62/2569/50)
+ [Impact]
+ Installing a snap that requires the u2f-devices interface doesn't show a UI
element to enable/disable this in GNOME Software. Initially Chromium
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: chromium-browser (Ubuntu Xenial)
** No longer affects: chromium-browser (Ubuntu Bionic)
** No longer affects: chromium-browser (Ubuntu Cosmic)
--
You received this bug notification
** Changed in: gnome-software (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work with
** Changed in: gnome-software (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work
@robert-ancell, I addition of this interface to the ubuntu-master,
ubuntu-3-30, and ubuntu-3-28 branches as well as snap-store. Can you
please include this in your next round of SRUs for cosmic, bionic and
xenial? I wasn't sure which branch to use for xenial.
** Also affects: gnome-software
Tentative request for auto-connection: https://forum.snapcraft.io/t
/auto-connecting-the-u2f-devices-interface-for-the-chromium-snap/10052
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
I'm not sure whether u2f being auto-connected is acceptable from a
security standpoint, I'll ask Jamie and if it is, I'll request the auto-
connection.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
This works now with core and chromium on the stable branches.
Olivier, I don't see u2f in GNOME Software's Permissions dialog for
Chromium.
Also, are you intending to ask Security if u2f can be auto-connected for
Chromium?
--
You received this bug notification because you are a member of
I used your instructions to successfully authenticate with
https://salsa.debian.org/ using the Chromium snap. Thanks! I believe my
device is also a Yubikey 4.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
I've published revision 579 to the candidate channel with the u2f-devices plug.
To test this you will need to do the following:
snap refresh core --edge
snap refresh chromium --candidate
snap connect chromium:u2f-devices
Then restart chromium and verify that your U2F device is seen
Jamie added a u2f-devices interface to snapd, and I successfully tested
it with chromium and a YubiKey 4 (using
https://demo.yubico.com/webauthn/registration).
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/commit/?id=413294d8a3e7ce271fe050670ab99d43972ce6df
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
This isn’t mentioned in the bug so thought I’d just document it here:
* U2F must be enabled in about:config (security.webauth.u2f;true) before
it will work in Firefox.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
I'm testing with a brand new Yubikey 4, and after adding the rules in
comment #16, I was seeing more denials which prompted me to add the
following two rules:
/run/udev/data/c14:[0-9]* r,
/sys/devices/pci**/usb*/**/report_descriptor r,
With those the denials went away, but U2F
Could the hidraw interface
(https://github.com/snapcore/snapd/blob/master/interfaces/builtin/hidraw.go)
be of any help here?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
jdstrand, I've added those rules, and the denials go away, but I'm
afraid it still doesn't work. There doesn't seem to be any denials, but
it's like chrome just doesn't see it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F
The actual rules would be:
# for U2F yubikey
/run/udev/data/c238:[0-9]* r,
/run/udev/data/c239:[0-9]* r,
/run/udev/data/c240:[0-9]* r,
but using the redundant rules from the previous comment is fine too.
--
You received this bug notification because you are a member of Desktop
Packages, which
We can add this to browser-support:
# for U2F yubikey
/run/udev/data/c238:[0-9]* r,
/run/udev/data/c239:[0-9]* r,
/run/udev/data/c240:[0-9]* r,
/run/udev/data/c240:[0-9]* r,
/run/udev/data/c240:[0-9]* r,
Can someone experiencing this issue adjust
** Changed in: chromium-browser (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work with yubikey
I am experiencing the same thing with both firefox and chromium snap
packages. Google Chrome install works perfectly. Really annoying to
have to revert to .deb if there is a snap package available.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I asked @jdstrand on the snapcraft forum: https://forum.snapcraft.io/t
/fido-u2f-authentication-fails-in-chromium-snap-build/6130/4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Thanks for the feedback Alejandro. So it looks like the raw-usb
interface doesn't help indeed, what chromium needs read access to to
access your key is the following:
/run/udev/data/c238:0
/run/udev/data/c239:0
/run/udev/data/c240:0
/run/udev/data/c240:1
/run/udev/data/c240:2
Sorry forgot
journalctl -f:
-- Logs begin at Sun 2018-08-12 21:54:04 CEST. --
ago 16 19:20:29 Alex thunderbird.desktop[25941]: [Parent 26418, Gecko_IOThread]
WARNING: pipe error (113): Conexión reinicializada por la máquina remota: file
I have the same issue, my Yubikey is the yibikey neo 4 model, it does
support U2F. after installing Ubuntu 18.04.01 I followed yubico's
instructions:
https://support.yubico.com/support/solutions/articles/1506449-using-
your-u2f-yubikey-with-linux
which means I have a udev rule for the device,
@Sami: I have re-opened the candidate/raw-usb-test channel and updated
it to the latest stable release. Please test with the instructions in
comment #3, run chromium with --enable-logging=stderr, and in another
terminal window please run "journalctl -f" and share any relevant
denials. Thanks!
--
I can confirm the bug is still present, tested with 67.0.3396.99 (367)
and 68.0.3440.75 (383). I couldn't test with raw-usb as it seems this
channel doesn't exist anymore.
Anything I could do to help testing or debugging this?
--
You received this bug notification because you are a member of
the proprietary google chrome does find the yubikey / gnubbie
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
[snap] U2F doesn't work with yubikey
Status in
with chromium --enable-logging=stderr
You just see that chromium can not find the device in the log it says:
[14261:14261:0718/202809.157292:INFO:CONSOLE(173)] "0718 20:28:09.156000: []",
source: chrome-extension://kmendfapggjehodndflmmgagdbamhnfd/gnubbies.js (173)
Do you get more useful debug information if you run the snap with the
"--enable-logging=stderr" parameter?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1738164
Title:
It no longer throws an apparmor denied message but it doesn't work.
Bot gmail and github throw a 'Something went wrong' error.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
@Chris: can you try the following, and report whether this addresses the
issue:
snap refresh chromium --channel=candidate/raw-usb-test
snap connect chromium:raw-usb
Thanks!
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in: chromium-browser (Ubuntu)
It looks like the raw-usb interface might help here. I'll rebuild the
snap with it and will post instructions on how to test.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
It appears that apparmor is blocking u2f requests :
[ 5955.568022] audit: type=1400 audit(1526465659.599:92): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/sys/devices/pci:00/:00:14.0/usb3/3-3/3-3:1.0/0003:045E:07B2.0001/report_descriptor"
pid=19386
46 matches
Mail list logo
