[snap] SoloKeys not supported by u2f-devices interface

Bug #1851211 reported by Christoph
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
Fix Released
Medium
Jamie Strandboge
chromium-browser (Ubuntu)
Confirmed
Undecided
Unassigned
snapd (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

This affects the current build of the snap version of Chromium.

Although it was marked as fixed in the ticket here: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164

it is still open. No chance to use such a key in the browser.

dmesg output is:

My dmesg out put shows a lot of DENIED:

audit: type=1107 audit(1572541712.846:243): pid=954 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=20568 label="snap.chromium.chromium" peer_pid=946 peer_label="unconfined"
                exe="/usr/bin/dbus-daemon" sauid=106 hostname=? addr=? terminal=?'
[ 7036.430639] audit: type=1400 audit(1572541713.042:244): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 7036.430641] audit: type=1400 audit(1572541713.042:245): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=20568 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor" pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Suggested solutions in the other tickets do not work

System is Ubuntu 19.10 on an Asus UX330
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DRM.card0-HDMI-A-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wAebcxW838CAAYUAQOANR54Cq7FoldKnCUSUFQhCACzAIGAgUABAQEBAQEBAQEBGjaAoHA4H0AwIDUAEyshAAAaAjqAGHE4LUBYLEUAEyshAAAeAAAA/QA4PR5TDwAKICAgICAgAAAA/ABXMjQ0MgogICAgICAgATICAyHxTpAEAwEUEgUfEBMAAAAAIwkHB4MBAABlAwwAEAACOoAYcTgtQFgsRQATKyEAAB4BHYAYcRwWIFgsJQATKyEAAJ4BHQByUdAeIG4oVQATKyEAAB6MCtCKIOAtEBA+lgATKyEAABgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJg==
 modes: 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x960 1280x720 1280x720 1280x720 1280x720 1024x768 800x600 720x576 720x480 720x480 720x480 720x480 640x480 640x480 640x480
DRM.card0-eDP-1:
 enabled: disabled
 dpms: Off
 status: connected
 edid-base64: AP///////wAGry0nAAAAABAZAQSVHRF4ArwFolVMmiUOUFQAAAABAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4AJaUQAAAYAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTMzSEFOMDIuNyAKAII=
 modes: 1920x1080
DiskUsage:
 Filesystem Type Size Used Avail Use% Mounted on
 /dev/sda6 ext4 184G 35G 140G 20% /home
 tmpfs tmpfs 7,8G 152M 7,7G 2% /dev/shm
 /dev/sda6 ext4 184G 35G 140G 20% /home
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-09-30 (766 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp.
 Bus 001 Device 003: ID 0bda:58d1 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX330UAK
Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=33f0c319-6f77-49d2-85ed-236d397fc004 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70 (edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
Tags: eoan snap
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-23 (14 days ago)
UserGroups: adm cdrom daemon dialout dip docker kvm lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 04/19/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX330UAK.315
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX330UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX330UAK.315:bd04/19/2019:svnASUSTeKCOMPUTERINC.:pnUX330UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX330UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: UX330UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Olivier Tilloy (osomon) wrote :

The relevant denial seems to be:

[ 7049.256201] audit: type=1400 audit(1572541725.870:246): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-ELAN1200:00/0018:04F3:3022.0001/report_descriptor" pid=20568 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

Christoph, is your device a Yubikey?

Can you please attach additional debug information to this bug by running the following command in a terminal?

    apport-collect 1851211

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
Christoph (cvboth) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected eoan snap
description: updated
Revision history for this message
Christoph (cvboth) wrote : Dependencies.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Lspci.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : ProcModules.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Snap.ChromiumPrefs.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Snap.Connections.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Snap.Info.chromium.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Snap.Info.core.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Snap.Info.core18.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Snap.Info.gtk-common-themes.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : UdevDb.txt

apport information

Revision history for this message
Christoph (cvboth) wrote : Re: U2F not working in current build

Hi Olivier thanks for your answer.

I executed the command you asked for. Hope you received all necessary information. If not please don't hesitate to contact me.

No it is a SoloKeys (https://solokeys.com):

lsusb: Bus 001 Device 005: ID 0483:a2ca STMicroelectronics Solo 2.5.3

It works perfectly in Firefox or Vivalid-Browser which are not installed as snaps

Thanks again! Cheers

Revision history for this message
Olivier Tilloy (osomon) wrote :

Thanks for the info. The u2f-devices interfaces doesn't support the SoloKeys yet, it will need updating.

Relevant commits:
  https://github.com/Yubico/libu2f-host/commit/bdb4ca33a9ec7683d6f2016cf61f5c8e28d37379
  https://github.com/Yubico/libu2f-host/commit/8d593512998a7df962d6dd0a7c4e641e5fe8b567

Changed in chromium-browser (Ubuntu):
status: Incomplete → Confirmed
summary: - U2F not working in current build
+ [snap] U2F SoloKeys not supported by u2f-devices interface
summary: - [snap] U2F SoloKeys not supported by u2f-devices interface
+ [snap] SoloKeys not supported by u2f-devices interface
Changed in snapd (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
Revision history for this message
Olivier Tilloy (osomon) wrote :

@Jamie, I'm tentatively assigning this to you, feel free to assign back to me if you'd rather I contributed the changes (I don't have the hardware to test with, though).

Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I've added it to my trello card for 2.43 policy updates.

Changed in snapd (Ubuntu):
status: New → Triaged
Changed in snapd (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Jamie Strandboge (jdstrand) wrote :
Changed in snapd:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Jamie Strandboge (jdstrand)
Changed in snapd (Ubuntu):
status: In Progress → Triaged
importance: Undecided → Medium
assignee: Jamie Strandboge (jdstrand) → nobody
Changed in snapd:
milestone: none → 2.42.3
Changed in snapd:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.