[snap] Personal Certificate Not Migrated to Snap-Based Chromium

Bug #1899478 reported by Gunter Ohrner
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

After upgrade from Ubuntu 18.04 to Ubuntu 20.04, login to web sites requiring client certificates is not possible any more.

The client certificate list in Chromium is empty.

ProblemType: Bug
DistroRelease: KDE neon 20.04
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Oct 12 14:26:40 2020
Snap: chromium 85.0.4183.121 (stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: Upgraded to focal on 2020-10-11 (1 days ago)

Revision history for this message
Gunter Ohrner (gohrner) wrote :
Changed in chromium-browser (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Olivier Tilloy (osomon) wrote :

Thanks for the report Gunter.

Just to make sure I understand correctly the problem: we're talking about certificates that chromium shows at chrome://settings/certificates ?

You had some personal certificates there in Ubuntu 18.04, and after upgrading to 20.04 they are not there any longer?

Were your other chromium settings (current browsing session, history, passwords) correctly imported in the upgrade?

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
summary: - Personal Certificate Not Migrated to Snap-Based Chromium
+ [snap] Personal Certificate Not Migrated to Snap-Based Chromium
Revision history for this message
Gunter Ohrner (gohrner) wrote :

> Just to make sure I understand correctly the problem: we're talking about certificates
> that chromium shows at chrome://settings/certificates ?

Correct.

> You had some personal certificates there in Ubuntu 18.04, and after upgrading to 20.04
> they are not there any longer?

Exactly. One certificate, to be precise.

> Were your other chromium settings (current browsing session, history, passwords)
> correctly imported in the upgrade?

Yes - Bookmarks and also - just checked - history are there. I don't know about Cookies, I configured them to be Session Cookies anyway.

Passwords are stored in KDE Wallet on my system, but they are also still there.

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

I can reliably reproduce the problem: I installed the bionic debs for chromium-browser in a focal VM, launched chromium-browser, imported a personal certificate, then closed chromium, ran "apt update" and "apt dist-upgrade", which installed the snap version of chromium (replacing the deb), and when I ran chromium again, the certificate I had previously imported wasn't there.

Changed in chromium-browser (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Olivier Tilloy (osomon) wrote :

The chromium deb uses the system's NSS store, which is in ~/.pki/nssdb for personal certificates.
This isn't handled by the profile importer in the chromium snap.

Bug #1859643 is closely related.

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.