> It wouldn't have to be a supplementary status code, but it seems more
> consistent that way. I guess we're not at risk of running out of
> supplementary status code bits...
The only risk with supplementary status code is that applications that check for GSS_ERROR()/GSS_S_COMPLETE (rather than GSS_S_CONTINUE_NEEDED/GSS_S_COMPLETE) may go into an infinite loop. But I think logically supplementary makes more sense. It's just a matter of perhaps (like on Windows) only propagating that error past the mechglue when NegoEx is being used. That gives you a line in the sand.
-- Luke
|