Updated NAT fixes

[Nicolas Williams]

The flag would have to be named something less mech-specific, like
GSS_C_CHANNEL_BINDINGS__FOLLOW_CREDS, say, to keep most of the name you
suggest.

Nico

On Wed, Apr 10, 2002 at 08:05:56PM -0500, Steven Michaud wrote:
> > But now I've found a way to tie address checking to the presence or
> > absence of addresses in the service ticket contained in
> > gss_accept_context()'s input_token parameter.  This is better, but it
> > requires yet another change to gss_accept_context(), and possibly a
> > revision to the GSSAPI RFC.  (I add a definition of
> > GSS_C_CHANNEL_BINDINGS_FOLLOW_TICKET to gssapi.h, and use it as a
> > signal (in the application_data field of gss_accept_context()'s
> > input_chan_bindings parameter) that gss_accept_context() should ignore
> > channel bindings.)
> 
> I dropped a part of the last sentence.  It should read:
> 
> (I add a definition of GSS_C_CHANNEL_BINDINGS_FOLLOW_TICKET to
> gssapi.h, and use it as a signal (in the application_data field of
> gss_accept_context()'s input_chan_bindings parameter) that
> gss_accept_context() should ignore channel bindings when the service
> ticket contained in its input_token parameter has no addresses.)
> 
> 
> _______________________________________________
> krbdev mailing list             krbdev at mit.edu
> http://mailman.mit.edu/mailman/listinfo/krbdev
-- 
-DISCLAIMER: an automatically appended disclaimer may follow. By posting-
-to a public e-mail mailing list I hereby grant permission to distribute-
-and copy this message.-

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.