[SSSD] [PATCH] Two enhancements for PAM client

Ralf Haferkamp rhafer at suse.de
Fri Apr 23 08:17:23 UTC 2010


Am Donnerstag 22 April 2010 17:03:23 schrieb Sumit Bose:
> On Thu, Apr 22, 2010 at 04:37:36PM +0200, Ralf Haferkamp wrote:
> > Am Donnerstag 22 April 2010 12:08:46 schrieb Sumit Bose:
> > > Hi,
> > > 
> > > the two patches attached should fix #446 and #417 respectively.
> > > 
> > > For #417 a different solution, where the message is generated by
> > > SSSD and send to the client, would be possilbe. But I decided
> > > against it, because with the attached patch it is possilbe to
> > > support localized messages.
> > 
> > Pardon my ignorance, but why can messages generated by the daemon
> > not be localized? Am I overlooking something?
> 
> The messages generated by the daemon can be localized, but I meant the
> localization with respect to the settings of the client.
The client is this case is the PAM module. Which is running as root 
usually (as is sssd). For best localization you'd need to run in the 
locale of the authenticating user. So there is no advantage in generating 
the strings on the client side (at least for the PAM module). It makes 
some things even harder as the messeage are obviously very depened on the 
backend that is used.

I agree that for other clients (!=PAM) the localization could be easier 
handled on the client side.

> We had a
> longer discussion about how to handle localization and came to the
> agreement that this should be done on the client side, because the
> client knows best about this locale settings and the use of gettext()
> is straight forward.
> 
> In this special case it would be possible to let the client send it's
> locale to the SSSD and let the SSSD open the file and send back the
> content. But this would mean that we have to send more data through
> the pipe.

-- 
Ralf



More information about the sssd-devel mailing list