openssh unix dev - May 2001 - New kex organisation and user options.

I'm in the process of updating my GSSAPI patches to the 2.9 release.
However,
I've run into a slight problem with managing to get user options to play 
nicely with the way that the kex code is now organised.

With the GSS kex its possible for the user to specify whether they want to 
delegate their credentials to the server or not. This option is used only on 
the client side (and so is specified in the client options structure). 
Previously, when the client and server kex code lived in client/server 
specific files this was fine. With the reorganisation for rekeying, the code 
now lives in generic files which are included by both client and server, 
which appears to make it impossible to use the options structure within the 
key exchange code.

Does anyone have any idea of a clean way to get around this? I must confess, 
I'm a little stumped for a way to do it that doesn't impact majorly on
the
current codebase (and doesn't involve using new global variables to
represent
options items)

Cheers,

Simon
-- 
Simon Wilkinson            <simon at sxw.org.uk>         
http://www.sxw.org.uk
"Men occasionally stumble over the truth, but most pick themselves up and
hurry off as if nothing had happened" -- Winston Churchill

On Tue, May 08, 2001 at 06:16:25PM +0100, Simon Wilkinson
wrote:
> With the GSS kex its possible for the user to specify whether they want to 
> delegate their credentials to the server or not. This option is used only
on
> the client side (and so is specified in the client options structure). 
> Previously, when the client and server kex code lived in client/server 
> specific files this was fine. With the reorganisation for rekeying, the
code
> now lives in generic files which are included by both client and server, 
> which appears to make it impossible to use the options structure within the
> key exchange code.
you still can split your own code into
client and server files and extend struct Kex.

-m