Chromium fails to get data from google end point verification helper app
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
New
|
Low
|
Unassigned |
Bug Description
I am trying out Google end-point verification. This is a system that allows the admins of a Google Workplace env to set information security requirements on the browsers/systems that connect. When using snapped Chromium, it fails to fetch data from the host system.
The details:
Prelude
1. I use the latest Chromium from the snap-store (Version 116.0.5845.110 (Official Build) snap (64-bit))
2. I install the Google end-point verification extension: https:/
3. I install the helper app: https:/
What goes wrong
4. The helper app has a shell script that fetches the details of the host. That works fine. Note that it detects the encrypted disk.
kristofer@
serial_number: "PW00QL5N"
disk_encrypted: ENABLED
os_version: "22.04"
screen_
hostname: "kristofer-
model: "20UN002KMH"
os_firewall: "no"
mac_addresses: "00:d2:b1:d3:c4:42"
mac_addresses: "00:16:3e:00:00:00"
mac_addresses: "00:16:3e:4f:fa:02"
mac_addresses: "a6:8d:49:a8:08:fb"
mac_addresses: "04:56:e5:dc:20:fd"
kristofer@
5. The chromium extension attempts to get this data, but fails. Here are the logs from the extension. Note that it has diskEncrypted set to false.
[230825 08:58:34.05] [ChromeDeviceIn
[230825 08:58:34.05] [ChromeDeviceIn
[230825 08:58:34.06] [ChromeDeviceIn
[230825 08:58:34.06] [NativeDeviceIn
The same extension, on the same machine, running on Chrome is able to detect the data from (4):
[230825 09:00:49.97] [ChromeDeviceIn
[230825 09:00:49.98] [ChromeDeviceIn
I suspect, but I don't know, that the snap confinement prevents it from fetching the data. Should you have any questions or need help to get more detailed logs, please reach out to me.
summary: |
- Chromium fails to get data from google end point verificatin helper app + Chromium fails to get data from google end point verification helper app |
Hi Kristofer, thanks for the bug report.
You are most likely right that the confinement is the cause.
The source code of the extension is not available, is it?