[33716] in Kerberos

home help back first fref pref prev next nref lref last post

Re: (mk|rd)_(priv|safe) and NAT

daemon@ATHENA.MIT.EDU (Chris Hecker)
Wed Aug 3 18:20:39 2011

Message-ID: <4E39C9B0.7080202@d6.com>
Date: Wed, 03 Aug 2011 15:20:32 -0700
From: Chris Hecker <checker@d6.com>
MIME-Version: 1.0
To: "kerberos@mit.edu" <kerberos@mit.edu>
In-Reply-To: <1312409591.23877.301.camel@t410>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu


> Yes, you will need separate auth contexts if you want to use
> sequence numbers on some messages but not others.

That's what I figured.  I'll have to mk_req/rd_req/mk_rep/rd_rep both on 
the ordered and unordered channels (which, sadly, are on the same UDP 
socket, so it's kind of silly...) to generate the auth_contexts 
correctly, right?

Chris




On 2011/08/03 15:13, Greg Hudson wrote:
> On Wed, 2011-08-03 at 17:47 -0400, Chris Hecker wrote:
>> Right, but I'm going to force the replay cache off and use subkeys like
>> we discussed in the other thread.  I assume I can't use the do-sequence
>> flag on an unordered/unreliable channel?  So, if I want to mk_priv/safe
>> on that channel, will I need another auth_context?
>
> Yes, you will need separate auth contexts if you want to use sequence
> numbers on some messages but not others.
>
> For the unordered messages, since you are using neither sequence numbers
> nor a replay cache, you'll need to address replays at the application
> protocol layer.
>
>
>
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post