Sebastien Bacher wrote on 2008-06-23: (permalink)
did you read the previous comments? the previous setup was not really
secure, you can set a blank password for your gnome-keyring if you don't
care about security though but ubuntu is not going to change back to a
non secure default
What an
did you read the previous comments? the previous setup was not really
secure, you can set a blank password for your gnome-keyring if you don't
care about security though but ubuntu is not going to change back to a
non secure default
--
Evolution asks my pasword to unlock the default keyring
I strongly agree. It is difficult to understand why this is not a bug.
Clearly, this only changed since the last
update. Ubuntu users using automatic login did not have to enter a password
for evolution before the
last update and now they do. It would make sense to regard this as a bug and
This still is a bug for those users with automatic logon. Someone
logging on automatically is not generally going to want to enter a
password to get to their email. At least, if they do they should have
to switch it on.
My wife doesn't even know the password (my choice to reduce the risk of
you can create a gnome-keyring not using a password to store your
evolution logins if you don't care about security, we are not going to
change the default to this non security setting though
--
Evolution asks my pasword to unlock the default keyring since last update
login in gdm entering a password should automatically unlock the gnome-
keyring, if it doesn't that's a bug. Could be the bug about the gnome-
keyring password not changing automatically when you change your system
password which leads to incorrect gnome-keyring credentials
--
Evolution asks my
I had this problem and I do NOT have auto login enabled, I use a
password just like I always have.
How can this not be considered a bug? Installing routine package
updates on a stable distro should not cause bizarre, inexplicable
behavior that I have to search the forums to understand. I'm a
thank you for your bug report, that's not a bug though, using the gnome-
keyring gives extra security to the passwords storage
you can set an empty password to the gnome-keyring so it'll be
automatically unblock without asking for a password, you can also create
an extra gnome-keyring to store
Thank you for this fast answer.
After I read your advices, I created a new keyring for evolution using
seahorse-preferences, but how can I assign the evolution passwords to this
keyring ?
Another (silly) question : why isn't the default keyring unlocked after
automatic connection ?
Thank you
to store the password in a different gnome-keyring change the default
one in seahorse so the next password stored will be written in this one,
you need to remove those stored in the other gnome-keyring before doing
that though
the automatic login doesn't ask for a password so it can't give that
I think these will be my last questions :
- now that I'm using a keyring which hasn't got a password, is it less secured
than the way my email passwords were stocked before the update ?
- will the fact that there are users using automatic connection be taken in
care on next updates (a way of
- now that I'm using a keyring which hasn't got a password, is it less
secured than the way my email passwords were stocked before the update ?
no, the situation is similar, it's easy to read the passwords for
anybody having access to the user directory
- will the fact that there are users
12 matches
Mail list logo
