i SSKrSSKr"SS\R5r"SS\R5r"SS\R5rg)Nc@\rSrSrSrSrSrSrSrSr Sr S r S r S r S rS rg) BufferTypezBuffer types to use for an IOVBuffer type. These are the IOVBuffer type flags that can be set for an IOVBuffer. The keys are a generified name for the respective SSPI and GSSAPI flags. r iN)__name__ __module__ __qualname____firstlineno____doc__emptydataheader pkg_paramstrailerpaddingstream sign_only mic_token data_readonly__static_attributes__rD/home/james-whalen/.local/lib/python3.13/site-packages/spnego/iov.pyrrs= E D FJGG FII Mrrch\rSrSr%Sr\\S'\R\R\ \ \ 4\S'Sr g) IOVBufferaA buffer to pass as a list to :meth:`wrap_iov()`. Defines the buffer inside a list that is passed to :meth:`wrap_iov()`. A list of these buffers are also returned in the `IOVUnwrapResult` under the `buffers` attribute. On SSPI only a buffer of the type `header`, `trailer`, or `padding` can be auto allocated. On GSSAPI all buffers can be auto allocated when `data=True` but the behaviour behind this is dependent on the mech it is run for. On the output from the `*_iov` functions the data is the bytes buffer or `None` if the buffer wasn't set. When used as an input to the `*_iov` functions the data can be the buffer bytes, the length of buffer to allocate or a bool to state whether the buffer is auto allocated or not. typerrN)rrrrrr__annotations__typingOptionalUnionbytesintboolrrrr r"r"s.   //&,,uc4'78 99rr"cH\rSrSr%Sr\\S'\R\ \S'Sr g) IOVResBuffer1zResults of an IOV operation. Unlike :class:`IOVBuffer` this limits the value of `data` to just an optionally set bytes. It is used as the return value of an IOV operation to better match what the expected values would be. r$rrN) rrrrrrr%r&r'r)rrrr r-r-1s  //%  rr-)enumr&IntEnumr NamedTupler"r-rrr r2sA .:!!:$ !6$$ !r