Re: A possible small bug in SPNEGO handling when dealing with NETAPP servers

2020-06-29 Thread Richard Sharpe
On Mon, Jun 29, 2020 at 4:29 PM Greg Hudson wrote: > > On 6/29/20 6:22 PM, Richard Sharpe wrote: > > The code was directly extracting the length from the buffer but (as > > you can see from the capture attached in the Session Setup Response) > > NetApp encodes the length of the OID in a longer for

Re: A possible small bug in SPNEGO handling when dealing with NETAPP servers

2020-06-29 Thread Greg Hudson
On 6/29/20 6:22 PM, Richard Sharpe wrote: > The code was directly extracting the length from the buffer but (as > you can see from the capture attached in the Session Setup Response) > NetApp encodes the length of the OID in a longer form as 0x82 0x00 > 0x09 instead of the short-form 0x09. RFC 417

Re: A possible small bug in SPNEGO handling when dealing with NETAPP servers

2020-06-29 Thread Benjamin Kaduk
On Mon, Jun 29, 2020 at 03:22:22PM -0700, Richard Sharpe wrote: > Hi folks, > > I have recently had to deal with a problem when calling > gss_init_sec_context after receiving an SPNEGO negTokenTarg from > NetApp C-Mode and 7-Mode servers. > > After some investigation, I tracked it down to > src/l

A possible small bug in SPNEGO handling when dealing with NETAPP servers

2020-06-29 Thread Richard Sharpe
Hi folks, I have recently had to deal with a problem when calling gss_init_sec_context after receiving an SPNEGO negTokenTarg from NetApp C-Mode and 7-Mode servers. After some investigation, I tracked it down to src/lib/gssapi/spnego/spnego_mech.c in get_mech_oid when handling the supportedMech O