[30344] in Kerberos
Re: Sequence numbering after export and import of context
daemon@ATHENA.MIT.EDU (Tom Yu)
Thu Oct 9 16:08:08 2008
To: "Markus Moeller" <huaraz@moeller.plus.com>
From: Tom Yu <tlyu@MIT.EDU>
Date: Thu, 09 Oct 2008 16:07:09 -0400
In-Reply-To: <gcdo0f$clp$1@ger.gmane.org> (Markus Moeller's message of "Mon,
6 Oct 2008 20:06:13 +0100")
Message-ID: <ldvprm9v8gi.fsf@cathode-dark-space.mit.edu>
MIME-Version: 1.0
Cc: kerberos@MIT.EDU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@MIT.EDU
"Markus Moeller" <huaraz@moeller.plus.com> writes:
> I understand that you need to keep the sequencing and in my case it is the
> case. Child 2 will always start after child 1 has finished. So there is a
> clear flow order which is just handled by different processes, why I thought
> I can re-export/re-import the context. Unfortunately it is an existing
> application and not that easy to completely rewrite.
It sounds like you are experiencing a problem with sequence number
state when you are doing (in serial order):
* Exporting context1 from a parent
* Importing context1 into child1
* Sending wrap token from child1
* Exporting context2 from child1
* Importing context2 into child2
* Sending wrap token from child2
and child2 is producing an incorrect sequence number.
If this is the case, I would consider it to be a bug. Would you be
willing to provide additional details about this problem? What GSS
library and what release?
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
