[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
** Tags added: password-storage -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Released Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin/chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
This results in a regression as seen in bug 1838821. -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Released Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin /chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
This bug was fixed in the package chromium-browser - 75.0.3770.142-0ubuntu1~snap1 --- chromium-browser (75.0.3770.142-0ubuntu1~snap1) eoan; urgency=medium * debian/apport/chromium-browser.py: update hook to call 'snap connections' instead of the deprecated 'snap interfaces' * debian/chromium-browser.preinst: connect the password-manager-service interface for package upgrades only (LP: #1836616) -- Olivier Tilloy Wed, 24 Jul 2019 14:21:16 +0200 ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Released Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin /chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
** Branch linked: lp:~chromium-team/chromium-browser/eoan-stable -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Committed Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin /chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
Implemented with https://bazaar.launchpad.net/~chromium-team/chromium- browser/eoan-stable/revision/1509 and https://bazaar.launchpad.net /~chromium-team/chromium-browser/eoan-stable/revision/1510. ** Changed in: chromium-browser (Ubuntu) Status: In Progress => 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: Fix Committed Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin /chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836616] Re: [snap] Upgrade from deb to snap forgets saved passwords
Kyle and Jamie kindly provided their opinion on the matter at https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592/8 and https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592/9. I'm going ahead with connecting the interface in the deb's pre-install script, on package upgrades only. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- 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/1836616 Title: [snap] Upgrade from deb to snap forgets saved passwords Status in chromium-browser package in Ubuntu: In Progress Bug description: On Ubuntu 19.10, when upgrading from the deb package to the snap¹, the password-manager-service interface is not auto-connected. As a result, chromium is unable to talk to org.freedesktop.Secret.Service over D-Bus, and it falls back to the basic unencrypted stored. See https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and- password-manager-service-interfaces-for-the-chromium-snap/4592 for why auto-connection was denied for the password-manager-service interface. This is bad user experience, as the transition should be seamless. Aside of auto-connection, one possible solution would be to do the connection in the deb’s pre-install script (which installs the snap from the store, and is executed as root). That has pretty much the same security implications though, so it requires input from the security team before proceeding. Yet another solution would be for the wrapper script (/usr/bin /chromium-browser) to extract the stored passwords from the keyring and import them into the basic unencrypted sqlite store for the snap, but that feels clunky and fragile. Or a log message / dialog box at startup to inform the user that they should connect the interface manually. But that's not great UX, and doesn't provide a seamless transition. ¹ https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-to-snap-transition/11179 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1836616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
