On Sat, Sep 12, 2009 at 09:02:34PM -0400, Simo Sorce wrote:
On Sat, 2009-09-12 at 10:11 +0200, Sumit Bose wrote:
On Fri, Sep 11, 2009 at 05:46:24PM -0400, Simo Sorce wrote:
On Fri, 2009-09-11 at 17:10 +0200, Sumit Bose wrote:
Most of items are not mandatory at the protocol level. If e.g.
On Fri, Sep 11, 2009 at 05:46:24PM -0400, Simo Sorce wrote:
On Fri, 2009-09-11 at 17:10 +0200, Sumit Bose wrote:
Most of items are not mandatory at the protocol level. If e.g. the
remote host is not known to the client it is not sent to the server
and
the server complains if he really
On Sat, 2009-09-12 at 10:11 +0200, Sumit Bose wrote:
On Fri, Sep 11, 2009 at 05:46:24PM -0400, Simo Sorce wrote:
On Fri, 2009-09-11 at 17:10 +0200, Sumit Bose wrote:
Most of items are not mandatory at the protocol level. If e.g. the
remote host is not known to the client it is not sent to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2009 06:13 AM, Sumit Bose wrote:
Hi,
with this patch the client sends its PID to sssd. This is at least
needed by the krb5 provider if the client PID should be part of the
credential cache file.
bye,
Sumit
On Fri, Sep 11, 2009 at 09:07:01AM -0400, Stephen Gallagher wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2009 06:13 AM, Sumit Bose wrote:
Hi,
with this patch the client sends its PID to sssd. This is at least
needed by the krb5 provider if the client PID should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/2009 10:29 AM, Sumit Bose wrote:
On Fri, Sep 11, 2009 at 09:07:01AM -0400, Stephen Gallagher wrote:
On 09/11/2009 06:13 AM, Sumit Bose wrote:
Hi,
with this patch the client sends its PID to sssd. This is at least
needed by the krb5
