*** This bug is a duplicate of bug 1996267 ***
https://bugs.launchpad.net/bugs/1996267
I don't think this is an exact dupe but it's pretty damn close. That
issue is about passwords; this one cookies. That issue is being mega
distracted by whether or not passwords are stored clear, or through
s
*** This bug is a duplicate of bug 1996267 ***
https://bugs.launchpad.net/bugs/1996267
That is a good target for a duplicate, marking it accordingly, thanks
for the heads-up.
** This bug has been marked a duplicate of bug 1996267
[snap] Doesn't store encrypted passwords unless interface is
This appears to be related with Bug LP:1996267.
--
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/2038875
Title:
Snap uses hardcoded key and salt for password and cookie encrypt
That's a truly bizarre argument, but I've responded to it there.
--
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/2038875
Title:
Snap uses hardcoded key and salt for password a
Well true, I'm removing the duplicate mark, however it does explain why
we cannot do this:
https://forum.snapcraft.io/t/auto-connecting-the-cups-control-and-
password-manager-service-interfaces-for-the-chromium-snap/4592/6
** This bug is no longer a duplicate of bug 1836616
[snap] Upgrade from
*** This bug is a duplicate of bug 1836616 ***
https://bugs.launchpad.net/bugs/1836616
@Nathan That's not the same bug from my reading. That's about an
upgrade. I'm saying on a totally fresh install the default behavior is
not to use the OS keyring, despite it being available.
--
You receive
*** This bug is a duplicate of bug 1836616 ***
https://bugs.launchpad.net/bugs/1836616
Found the duplicate target; See there that the interface auto-connection
was denied by Snap Store.
** This bug has been marked a duplicate of bug 1836616
[snap] Upgrade from deb to snap forgets saved pas
I'm pointing that when I add chromium on a fresh Ubuntu install it does
not do configure itself to use the libsecret keyring. When I add
chromium on a fresh Debian/Gnome Desktop install it does. This
difference is in packaging, and presumably came when chromium was
migrated to use snap. But I would
** 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/2038875
Title:
Snap uses hardcoded key and salt for password and cookie encryption
Status in c
If password-manager-service is connected with
snap connect chromium:password-manager-service
then it uses the operating system's key ring.
So are you pointing out that Chromium ought to use gnome-libcrypt
instead of basic when no key ring is detected?
--
You received this bug notification
The Chrome password manager does not mean it uses the Operating System's
key ring. If the key ring is not available or the configuration doesn't
detect it (as in the case of the snap) it will use key "peanuts" with
salt "saltysalt".
--
You received this bug notification because you are a member o
Hi Evan, thank you for the thorough report.
Are you aware of Chromium having the password-manager-interface? Then it
will use the keyring.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpa
You know if you're using the insecure v10 cookies by looking at the
first three bytes of encrypted data in the sqlite database. If it reads
\x76\x31\x30 you've got v10.. literally. if the third byte is \x31
you've got v11 the desirable variant.
--
You received this bug notification because you ar
13 matches
Mail list logo
