
RFC 4178 4.2.2 uses the field name negState rather than negResult in NegTokenResp, to denote the negotiation state. Harmonize with this, also replacing the underscores in accept-completed and accepet-incomplete to match the RFC.
67 lines
1.6 KiB
Groff
67 lines
1.6 KiB
Groff
-- $Id$
|
|
|
|
SPNEGO DEFINITIONS ::=
|
|
BEGIN
|
|
|
|
MechType::= OBJECT IDENTIFIER
|
|
|
|
MechTypeList ::= SEQUENCE OF MechType
|
|
|
|
ContextFlags ::= BIT STRING {
|
|
delegFlag (0),
|
|
mutualFlag (1),
|
|
replayFlag (2),
|
|
sequenceFlag (3),
|
|
anonFlag (4),
|
|
confFlag (5),
|
|
integFlag (6)
|
|
}
|
|
|
|
NegHints ::= SEQUENCE {
|
|
hintName [0] GeneralString OPTIONAL,
|
|
hintAddress [1] OCTET STRING OPTIONAL
|
|
}
|
|
|
|
NegTokenInit2 ::= SEQUENCE {
|
|
mechTypes [0] MechTypeList,
|
|
reqFlags [1] ContextFlags OPTIONAL,
|
|
mechToken [2] OCTET STRING OPTIONAL,
|
|
negHints [3] NegHints OPTIONAL
|
|
}
|
|
|
|
NegTokenInit ::= SEQUENCE {
|
|
mechTypes [0] MechTypeList,
|
|
reqFlags [1] ContextFlags OPTIONAL,
|
|
mechToken [2] OCTET STRING OPTIONAL,
|
|
mechListMIC [3] OCTET STRING OPTIONAL,
|
|
...
|
|
}
|
|
|
|
NegStateEnum ::= ENUMERATED {
|
|
accept-completed(0),
|
|
accept-incomplete(1),
|
|
reject(2),
|
|
request-mic(3)
|
|
}
|
|
|
|
-- NB: negState is not OPTIONAL in the new SPNEGO spec but
|
|
-- Windows clients do not always send it
|
|
NegTokenResp ::= SEQUENCE {
|
|
negState [0] NegStateEnum OPTIONAL,
|
|
supportedMech [1] MechType OPTIONAL,
|
|
responseToken [2] OCTET STRING OPTIONAL,
|
|
mechListMIC [3] OCTET STRING OPTIONAL,
|
|
...
|
|
}
|
|
|
|
NegotiationToken ::= CHOICE {
|
|
negTokenInit[0] NegTokenInit,
|
|
negTokenResp[1] NegTokenResp
|
|
}
|
|
|
|
NegotiationToken2 ::= CHOICE {
|
|
negTokenInit[0] NegTokenInit2
|
|
}
|
|
|
|
END
|