pam keyring issues

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

pam keyring issues

takisd
Hi

a recent upgrade of evolution deps (evolution-data-server, libcamel,
libebook, libecal, libedata-book etc) has resulted in evolution asking
to unlock the gnome keyring. thats fine, but annoying so i dug around
for a way to have this done automatically on login.

i found that installing libpam-gnome-keyring does this. following
instructions from numerous sites and the readme.debian file i tried the
following appended to the end of /etc/pam.d/gdm

---
auth    optional        pam_gnome_keyring.so
session optional        pam_gnome_keyring.so  auto_start

that didn;t work and actually didn't let me log in at all - it would
just keep going back to the user name field in gdm
---

---
auth optional pam_keyring.so try_first_pass
session optional pam_keyring.so

that did nothing.
---

@include common-pamkeyring

this resulted in a dialog that would not close as if stuck in an
authentication loop - image of the gdm screen with this is here:
http://executequery.org/temp/images/gnome-keyring-gdm-error.png

any suggestions on how to get this to work would be appreciated.

thanks
Takis



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: pam keyring issues

Sam Morris
On Wed, 19 Dec 2007 11:08:23 +1100, Takis Diakoumis wrote:

> Hi
>
> a recent upgrade of evolution deps (evolution-data-server, libcamel,
> libebook, libecal, libedata-book etc) has resulted in evolution asking
> to unlock the gnome keyring. thats fine, but annoying so i dug around
> for a way to have this done automatically on login.
>
> i found that installing libpam-gnome-keyring does this. following
> instructions from numerous sites and the readme.debian file i tried the
> following appended to the end of /etc/pam.d/gdm
>
> ---
> auth    optional        pam_gnome_keyring.so session optional      
> pam_gnome_keyring.so  auto_start
>
> that didn;t work and actually didn't let me log in at all - it would
> just keep going back to the user name field in gdm ---
>
> ---
> auth optional pam_keyring.so try_first_pass session optional
> pam_keyring.so
>
> that did nothing.
> ---
>
> @include common-pamkeyring
>
> this resulted in a dialog that would not close as if stuck in an
> authentication loop - image of the gdm screen with this is here:
> http://executequery.org/temp/images/gnome-keyring-gdm-error.png
>
> any suggestions on how to get this to work would be appreciated.
>
> thanks
> Takis

pam 2.20.2-1 (currently in unstable) includes PAM configuration for using
pam_gnome_keyring.so. Could you try again after upgrading to that
version? Make sure that you replace your version of the config file with
a fresh copy when prompted by dpkg.

--
Sam Morris
http://robots.org.uk/
 
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: pam keyring issues

takisd
hi
thanks for replying.

i actually forgot to mention, i'm running lenny and the version of
libpam-gnome-keyring is the same in sid 2.20.2-1. i downloaded and
installed that one anyway - no change. libpam-modules is the same
version in lenny as in sid.

i also noticed that /etc/pam.d/gdm is provided by gdm. did you perhaps
mean for me to upgrade gdm from sid? this has caused some other
conflicts dependency issues - but not nearly what i expected so i'm
running with it anyway, and i'll post how it goes.

thanks
Takis


On Wed, 2007-12-19 at 00:19 +0000, Sam Morris wrote:

> On Wed, 19 Dec 2007 11:08:23 +1100, Takis Diakoumis wrote:
>
> > Hi
> >
> > a recent upgrade of evolution deps (evolution-data-server, libcamel,
> > libebook, libecal, libedata-book etc) has resulted in evolution asking
> > to unlock the gnome keyring. thats fine, but annoying so i dug around
> > for a way to have this done automatically on login.
> >
> > i found that installing libpam-gnome-keyring does this. following
> > instructions from numerous sites and the readme.debian file i tried the
> > following appended to the end of /etc/pam.d/gdm
> >
> > ---
> > auth    optional        pam_gnome_keyring.so session optional      
> > pam_gnome_keyring.so  auto_start
> >
> > that didn;t work and actually didn't let me log in at all - it would
> > just keep going back to the user name field in gdm ---
> >
> > ---
> > auth optional pam_keyring.so try_first_pass session optional
> > pam_keyring.so
> >
> > that did nothing.
> > ---
> >
> > @include common-pamkeyring
> >
> > this resulted in a dialog that would not close as if stuck in an
> > authentication loop - image of the gdm screen with this is here:
> > http://executequery.org/temp/images/gnome-keyring-gdm-error.png
> >
> > any suggestions on how to get this to work would be appreciated.
> >
> > thanks
> > Takis
>
> pam 2.20.2-1 (currently in unstable) includes PAM configuration for using
> pam_gnome_keyring.so. Could you try again after upgrading to that
> version? Make sure that you replace your version of the config file with
> a fresh copy when prompted by dpkg.
>
> --
> Sam Morris
> http://robots.org.uk/
>  
> PGP key id 1024D/5EA01078
> 3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078
>
>


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: pam keyring issues

takisd
In reply to this post by Sam Morris
ok, i upgraded gdm to 2.20.2-1 and it seems to have fixed the problem.
it did prompt me the first time but the new keyring dialog also has a
checkbox to do it automatically on login and this seems to have worked.

the only other noticeable thing with the upgrade was that the shutdown
menu item is no longer available from the gnome-menu under system. i
assume this is a new permissions thing so i'll dig around.

the gdm upgrade from sid brought in the following with it:
capplets-data (1:2.18.1-1) to 1:2.20.1-2
gdm (2.18.4-1) to 2.20.2-1
gnome-control-center (1:2.18.1-1) to 1:2.20.1-2
gnome-session (2.18.3-1) to 2.20.2-1
libgnome-window-settings1 (1:2.18.1-1) to 1:2.20.1-2
libpanel-applet2-0 (2.18.3-2) to 2.20.2-2

thanks
Takis


On Wed, 2007-12-19 at 00:19 +0000, Sam Morris wrote:

> On Wed, 19 Dec 2007 11:08:23 +1100, Takis Diakoumis wrote:
>
> > Hi
> >
> > a recent upgrade of evolution deps (evolution-data-server, libcamel,
> > libebook, libecal, libedata-book etc) has resulted in evolution asking
> > to unlock the gnome keyring. thats fine, but annoying so i dug around
> > for a way to have this done automatically on login.
> >
> > i found that installing libpam-gnome-keyring does this. following
> > instructions from numerous sites and the readme.debian file i tried the
> > following appended to the end of /etc/pam.d/gdm
> >
> > ---
> > auth    optional        pam_gnome_keyring.so session optional      
> > pam_gnome_keyring.so  auto_start
> >
> > that didn;t work and actually didn't let me log in at all - it would
> > just keep going back to the user name field in gdm ---
> >
> > ---
> > auth optional pam_keyring.so try_first_pass session optional
> > pam_keyring.so
> >
> > that did nothing.
> > ---
> >
> > @include common-pamkeyring
> >
> > this resulted in a dialog that would not close as if stuck in an
> > authentication loop - image of the gdm screen with this is here:
> > http://executequery.org/temp/images/gnome-keyring-gdm-error.png
> >
> > any suggestions on how to get this to work would be appreciated.
> >
> > thanks
> > Takis
>
> pam 2.20.2-1 (currently in unstable) includes PAM configuration for using
> pam_gnome_keyring.so. Could you try again after upgrading to that
> version? Make sure that you replace your version of the config file with
> a fresh copy when prompted by dpkg.
>
> --
> Sam Morris
> http://robots.org.uk/
>  
> PGP key id 1024D/5EA01078
> 3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078
>
>


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]