RE: SASL security layers

[Paul Leach <paulle@xxxxxxxxxxxxx>]

Does the "buffer" include the security mechanism's trailer, or not?

> -----Original Message-----
> From: Chris Newman [mailto:Chris.Newman@xxxxxxxxxxxx]
> Sent: Monday, October 12, 1998 11:35 AM
> To: Paul Leach
> Cc: 'ietf-sasl@xxxxxxx'
> Subject: Re: SASL security layers
> 
> 
> On Fri, 9 Oct 1998, Paul Leach wrote:
> > When applied to GSS mechanisms, the following issue arises. 
> My data stream
> > looks like this:
> > 
> > 	4 byte count
> > 	App protocol data unit (APDU)
> > 	padding to cipher block size
> > 	GSS mechanism trailer
> 
> SASL only specifies that the cipher text buffers begin with a 4-octet
> count (covering the remainder of the buffer).  The structure 
> of the cipher
> text buffers is otherwise entirely defined by the mechanism.
> 
> If you're using the GSSAPI SASL mechanism, the buffer consists of the 
> entire output of a GSS_Wrap operation, with a SASL 
> security-layer buffer
> length prepended.
> 
> 		- Chris
> 
>