-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2010 04:57 PM, Stephen Gallagher wrote:
> On 12/07/2010 04:30 AM, Sumit Bose wrote:
>> On Mon, Dec 06, 2010 at 09:18:56AM -0500, Stephen Gallagher wrote:
>
>
>> Ok, I will do that. However, please modify the current patch so that we
>> just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2010 04:30 AM, Sumit Bose wrote:
> On Mon, Dec 06, 2010 at 09:18:56AM -0500, Stephen Gallagher wrote:
>
>
> Ok, I will do that. However, please modify the current patch so that we
> just fail if we don't find the principal we expect.
>
>> o
On Mon, Dec 06, 2010 at 09:18:56AM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/06/2010 09:07 AM, Sumit Bose wrote:
> > On Mon, Dec 06, 2010 at 08:38:54AM -0500, Stephen Gallagher wrote:
> > On 12/03/2010 03:56 PM, Sumit Bose wrote:
> > Although i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/2010 09:07 AM, Sumit Bose wrote:
> On Mon, Dec 06, 2010 at 08:38:54AM -0500, Stephen Gallagher wrote:
> On 12/03/2010 03:56 PM, Sumit Bose wrote:
> Although it might be recommended it is not necessary that the keytab
> entry for FAST o
On Mon, Dec 06, 2010 at 08:38:54AM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/03/2010 03:56 PM, Sumit Bose wrote:
> >> Although it might be recommended it is not necessary that the keytab
> >> entry for FAST or the TGT validation comes from the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/03/2010 03:56 PM, Sumit Bose wrote:
>> Although it might be recommended it is not necessary that the keytab
>> entry for FAST or the TGT validation comes from the same REALM, only the
>> KDC needs to know how the create tickets for the principal.
On Fri, Dec 03, 2010 at 10:28:19AM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/03/2010 05:12 AM, Sumit Bose wrote:
> > On Wed, Dec 01, 2010 at 03:12:02PM -0500, Stephen Gallagher wrote:
> > Patch 0001: Ack.
> > Patch 0002: This patch won't apply. Is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/03/2010 05:12 AM, Sumit Bose wrote:
> On Wed, Dec 01, 2010 at 03:12:02PM -0500, Stephen Gallagher wrote:
> Patch 0001: Ack.
> Patch 0002: This patch won't apply. Is it dependent on another patch
> currently in review? I tried atop master and atop
On Wed, Dec 01, 2010 at 03:12:02PM -0500, Stephen Gallagher wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/18/2010 08:15 AM, Sumit Bose wrote:
> > Hi,
> >
> > these two patches add support for FAST to the Kerberos provider as
> > requested in trac ticket #237. The first patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/18/2010 08:15 AM, Sumit Bose wrote:
> Hi,
>
> these two patches add support for FAST to the Kerberos provider as
> requested in trac ticket #237. The first patch just modifies some helper
> functions in krb5_child so that they can be used by the
Hi,
these two patches add support for FAST to the Kerberos provider as
requested in trac ticket #237. The first patch just modifies some helper
functions in krb5_child so that they can be used by the second patch.
We support FAST only with MIT Kerberos 1.8 or later, because with 1.7 it
is not pos
11 matches
Mail list logo