Thanks for the report Timo. I'm not sure what's happening here. I tested this like so in a VM:
- generated a custom root CA (e.g. using instructions at https://help.f-secure.com/product.html?business/threatshield/latest/en/task_50407934989D4923AB76367EA0E627CA-threatshield-latest-en) - imported it into chromium through chrome://settings/certificates - closed chromium, verified that the certificate was persisted in the snap's own NSSÂ db in ~/snap/chromium/current/.pki/nssdb/cert9.db (grepping on a distinctive string that's in the certificate) - refreshed the snap to a newer version (e.g. the edge channel) - launched chromium, and verified that the custom CA is still there Where are custom CAs stored in your setup, if not under ~/snap/chromium/current/ ? ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905010 Title: [snap] chromium forgets custom root certificates after each update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1905010/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
