Re: Big problems with keyring and Seahorse
- From: Adam Schreiber <sadam gnome org>
- To: "Karl F. Larsen" <klarsen1 gmail com>
- Cc: Seahorse mailing list <seahorse-list gnome org>
- Subject: Re: Big problems with keyring and Seahorse
- Date: Sat, 23 May 2009 16:16:48 -0400
On Sat, May 23, 2009 at 2:30 PM, Karl F. Larsen <klarsen1 gmail com> wrote:
> Adam Schreiber wrote:
>> I don't know what to tell you about the inherent brokeness you claim.
>> I'm running everything fine without problem in Jaunty
>
> What is without a problem? Do you need to give your password to the
> keyring EVERY time you bring up WiFi? This is silly on any computer since
> the password never leaves my computer and can't protect me from a thing.
I'm never prompted for a password to unlock the keyring. It's
unlocked when I login or unlock the screensaver. It's not silly in a
situation where it's not your personal laptop and it contains secrets
related to secured networks.
> As I recall when I first turned on Jaunty it asked for the WiFi password
> and then asked me to make a password for the keyring and I used my first
> name karl as the password. This worked for about a week and then it came up
> with a new demand for my main Ubuntu password. This is where I am now.
That sounds like there may be a bug with auto-creation of the login
keyring or there needs to be a better prompt to make sure the user
enters their login password. You should file a bug against
gnome-keyring in the PAM component if there is one.
> Where I work we use Red Hat and there is no keyring there.
I suppose that depends on what version of RH they run and how your
admin has chosen to deploy it.
>> and was in Ibex
>> too before upgrading. I also develop in Ubuntu. If you discover
>> genuine bugs, they should be filed in launchpad to go upstream or in
>> GNOME's bugzilla.
>
> I do have a bug filed with many others against keyring and seahorse due to
> problems with WiFi. That was how I was lead to learn so many others are
> having similar problems.
Can you provide a link to this bug?
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]