RFC1509 日本語訳
1509 Generic Security Service API : C-bindings. J. Wray. September 1993. (Format: TXT=99608 bytes) (Obsoleted by RFC2744) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
RFC一覧
英語原文
Network Working Group J. Wray
Request for Comments: 1509 Digital Equipment Corporation
September 1993
Network Working Group J. Wray Request for Comments: 1509 Digital Equipment Corporation September 1993
Generic Security Service API : C-bindings
Generic Security Service API : C-bindings
Status of this Memo
Status of this Memo
This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.
This RFC specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Abstract
Abstract
This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents.
This document specifies C language bindings for the Generic Security Service Application Program Interface (GSS-API), which is described at a language-independent conceptual level in other documents.
The Generic Security Service Application Programming Interface (GSS- API) provides security services to its callers, and is intended for implementation atop alternative underlying cryptographic mechanisms. Typically, GSS-API callers will be application protocols into which security enhancements are integrated through invocation of services provided by the GSS-API. The GSS-API allows a caller application to authenticate a principal identity associated with a peer application, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis.
The Generic Security Service Application Programming Interface (GSS- API) provides security services to its callers, and is intended for implementation atop alternative underlying cryptographic mechanisms. Typically, GSS-API callers will be application protocols into which security enhancements are integrated through invocation of services provided by the GSS-API. The GSS-API allows a caller application to authenticate a principal identity associated with a peer application, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis.
1. INTRODUCTION
1. INTRODUCTION
The Generic Security Service Application Programming Interface [1] provides security services to calling applications. It allows a communicating application to authenticate the user associated with another application, to delegate rights to another application, and to apply security services such as confidentiality and integrity on a per-message basis.
The Generic Security Service Application Programming Interface [1] provides security services to calling applications. It allows a communicating application to authenticate the user associated with another application, to delegate rights to another application, and to apply security services such as confidentiality and integrity on a per-message basis.
There are four stages to using the GSSAPI:
There are four stages to using the GSSAPI:
(a) The application acquires a set of credentials with which it may
prove its identity to other processes. The application's
credentials vouch for its global identity, which may or may not
be related to the local username under which it is running.
(a) The application acquires a set of credentials with which it may prove its identity to other processes. The application's credentials vouch for its global identity, which may or may not be related to the local username under which it is running.
Wray [Page 1] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 1] RFC 1509 GSSAPI - Overview and C bindings September 1993
(b) A pair of communicating applications establish a joint security
context using their credentials. The security context is a
pair of GSSAPI data structures that contain shared state
information, which is required in order that per-message
security services may be provided. As part of the
establishment of a security context, the context initiator is
authenticated to the responder, and may require that the
responder is authenticated in turn. The initiator may
optionally give the responder the right to initiate further
security contexts. This transfer of rights is termed
delegation, and is achieved by creating a set of credentials,
similar to those used by the originating application, but which
may be used by the responder. To establish and maintain the
shared information that makes up the security context, certain
GSSAPI calls will return a token data structure, which is a
cryptographically protected opaque data type. The caller of
such a GSSAPI routine is responsible for transferring the token
to the peer application, which should then pass it to a
corresponding GSSAPI routine which will decode it and extract
the information.
(b) A pair of communicating applications establish a joint security context using their credentials. The security context is a pair of GSSAPI data structures that contain shared state information, which is required in order that per-message security services may be provided. As part of the establishment of a security context, the context initiator is authenticated to the responder, and may require that the responder is authenticated in turn. The initiator may optionally give the responder the right to initiate further security contexts. This transfer of rights is termed delegation, and is achieved by creating a set of credentials, similar to those used by the originating application, but which may be used by the responder. To establish and maintain the shared information that makes up the security context, certain GSSAPI calls will return a token data structure, which is a cryptographically protected opaque data type. The caller of such a GSSAPI routine is responsible for transferring the token to the peer application, which should then pass it to a corresponding GSSAPI routine which will decode it and extract the information.
(c) Per-message services are invoked to apply either:
(c) Per-message services are invoked to apply either:
(i) integrity and data origin authentication, or
(i) integrity and data origin authentication, or
(ii) confidentiality, integrity and data origin authentication
to application data, which are treated by GSSAPI as
arbitrary octet-strings. The application transmitting a
message that it wishes to protect will call the appropriate
GSSAPI routine (sign or seal) to apply protection, specifying
the appropriate security context, and send the result to the
receiving application. The receiver will pass the received
data to the corresponding decoding routine (verify or unseal)
to remove the protection and validate the data.
(ii) confidentiality, integrity and data origin authentication to application data, which are treated by GSSAPI as arbitrary octet-strings. The application transmitting a message that it wishes to protect will call the appropriate GSSAPI routine (sign or seal) to apply protection, specifying the appropriate security context, and send the result to the receiving application. The receiver will pass the received data to the corresponding decoding routine (verify or unseal) to remove the protection and validate the data.
(d) At the completion of a communications session (which may extend
across several connections), the peer applications call GSSAPI
routines to delete the security context. Multiple contexts may
also be used (either successively or simultaneously) within a
single communications association.
(d) At the completion of a communications session (which may extend across several connections), the peer applications call GSSAPI routines to delete the security context. Multiple contexts may also be used (either successively or simultaneously) within a single communications association.
2. GSSAPI Routines
2. GSSAPI Routines
This section lists the functions performed by each of the GSSAPI routines and discusses their major parameters, describing how they are to be passed to the routines. The routines are listed in figure 4-1.
This section lists the functions performed by each of the GSSAPI routines and discusses their major parameters, describing how they are to be passed to the routines. The routines are listed in figure 4-1.
Wray [Page 2] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 2] RFC 1509 GSSAPI - Overview and C bindings September 1993
Figure 4-1 GSSAPI Routines
Figure 4-1 GSSAPI Routines
Routine Function
Routine Function
gss_acquire_cred Assume a global identity
gss_acquire_cred Assume a global identity
gss_release_cred Discard credentials
gss_release_cred Discard credentials
gss_init_sec_context Initiate a security context
with a peer application
gss_init_sec_context Initiate a security context with a peer application
gss_accept_sec_context Accept a security context
initiated by a peer
application
gss_accept_sec_context Accept a security context initiated by a peer application
gss_process_context_token Process a token on a security
context from a peer
application
gss_process_context_token Process a token on a security context from a peer application
gss_delete_sec_context Discard a security context
gss_delete_sec_context Discard a security context
gss_context_time Determine for how long a
context will remain valid
gss_context_time Determine for how long a context will remain valid
gss_sign Sign a message; integrity
service
gss_sign Sign a message; integrity service
gss_verify Check signature on a message
gss_verify Check signature on a message
gss_seal Sign (optionally encrypt) a
message; confidentiality
service
gss_seal Sign (optionally encrypt) a message; confidentiality service
gss_unseal Verify (optionally decrypt)
message
gss_unseal Verify (optionally decrypt) message
gss_display_status Convert an API status code
to text
gss_display_status Convert an API status code to text
gss_indicate_mechs Determine underlying
authentication mechanism
gss_indicate_mechs Determine underlying authentication mechanism
gss_compare_name Compare two internal-form
names
gss_compare_name Compare two internal-form names
gss_display_name Convert opaque name to text
gss_display_name Convert opaque name to text
Wray [Page 3] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 3] RFC 1509 GSSAPI - Overview and C bindings September 1993
gss_import_name Convert a textual name to
internal-form
gss_import_name Convert a textual name to internal-form
gss_release_name Discard an internal-form
name
gss_release_name Discard an internal-form name
gss_release_buffer Discard a buffer
gss_release_buffer Discard a buffer
gss_release_oid_set Discard a set of object
identifiers
gss_release_oid_set Discard a set of object identifiers
gss_inquire_cred Determine information about
a credential
gss_inquire_cred Determine information about a credential
Individual GSSAPI implementations may augment these routines by providing additional mechanism-specific routines if required functionality is not available from the generic forms. Applications are encouraged to use the generic routines wherever possible on portability grounds.
Individual GSSAPI implementations may augment these routines by providing additional mechanism-specific routines if required functionality is not available from the generic forms. Applications are encouraged to use the generic routines wherever possible on portability grounds.
2.1. Data Types and Calling Conventions
2.1. Data Types and Calling Conventions
The following conventions are used by the GSSAPI:
The following conventions are used by the GSSAPI:
2.1.1. Structured data types
2.1.1. Structured data types
Wherever these GSSAPI C-bindings describe structured data, only fields that must be provided by all GSSAPI implementation are documented. Individual implementations may provide additional fields, either for internal use within GSSAPI routines, or for use by non-portable applications.
Wherever these GSSAPI C-bindings describe structured data, only fields that must be provided by all GSSAPI implementation are documented. Individual implementations may provide additional fields, either for internal use within GSSAPI routines, or for use by non-portable applications.
2.1.2. Integer types
2.1.2. Integer types
GSSAPI defines the following integer data type:
GSSAPI defines the following integer data type:
OM_uint32 32-bit unsigned integer
OM_uint32 32-bit unsigned integer
Where guaranteed minimum bit-count is important, this portable data type is used by the GSSAPI routine definitions. Individual GSSAPI implementations will include appropriate typedef definitions to map this type onto a built-in data type.
Where guaranteed minimum bit-count is important, this portable data type is used by the GSSAPI routine definitions. Individual GSSAPI implementations will include appropriate typedef definitions to map this type onto a built-in data type.
2.1.3. String and similar data
2.1.3. String and similar data
Many of the GSSAPI routines take arguments and return values that describe contiguous multiple-byte data. All such data is passed between the GSSAPI and the caller using the gss_buffer_t data type.
Many of the GSSAPI routines take arguments and return values that describe contiguous multiple-byte data. All such data is passed between the GSSAPI and the caller using the gss_buffer_t data type.
Wray [Page 4] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 4] RFC 1509 GSSAPI - Overview and C bindings September 1993
This data type is a pointer to a buffer descriptor, which consists of a length field that contains the total number of bytes in the datum, and a value field which contains a pointer to the actual datum:
This data type is a pointer to a buffer descriptor, which consists of a length field that contains the total number of bytes in the datum, and a value field which contains a pointer to the actual datum:
typedef struct gss_buffer_desc_struct {
size_t length;
void *value;
} gss_buffer_desc, *gss_buffer_t;
typedef struct gss_buffer_desc_struct { size_t length; void *value; } gss_buffer_desc, *gss_buffer_t;
Storage for data passed to the application by a GSSAPI routine using the gss_buffer_t conventions is allocated by the GSSAPI routine. The application may free this storage by invoking the gss_release_buffer routine. Allocation of the gss_buffer_desc object is always the responsibility of the application; Unused gss_buffer_desc objects may be initialized to the value GSS_C_EMPTY_BUFFER.
Storage for data passed to the application by a GSSAPI routine using the gss_buffer_t conventions is allocated by the GSSAPI routine. The application may free this storage by invoking the gss_release_buffer routine. Allocation of the gss_buffer_desc object is always the responsibility of the application; Unused gss_buffer_desc objects may be initialized to the value GSS_C_EMPTY_BUFFER.
2.1.3.1. Opaque data types
2.1.3.1. Opaque data types
Certain multiple-word data items are considered opaque data types at the GSSAPI, because their internal structure has no significance either to the GSSAPI or to the caller. Examples of such opaque data types are the input_token parameter to gss_init_sec_context (which is opaque to the caller), and the input_message parameter to gss_seal (which is opaque to the GSSAPI). Opaque data is passed between the GSSAPI and the application using the gss_buffer_t datatype.
Certain multiple-word data items are considered opaque data types at the GSSAPI, because their internal structure has no significance either to the GSSAPI or to the caller. Examples of such opaque data types are the input_token parameter to gss_init_sec_context (which is opaque to the caller), and the input_message parameter to gss_seal (which is opaque to the GSSAPI). Opaque data is passed between the GSSAPI and the application using the gss_buffer_t datatype.
2.1.3.2. Character strings
2.1.3.2. Character strings
Certain multiple-word data items may be regarded as simple ISO Latin-1 character strings. An example of this is the input_name_buffer parameter to gss_import_name. Some GSSAPI routines also return character strings. Character strings are passed between the application and the GSSAPI using the gss_buffer_t datatype, defined earlier.
Certain multiple-word data items may be regarded as simple ISO Latin-1 character strings. An example of this is the input_name_buffer parameter to gss_import_name. Some GSSAPI routines also return character strings. Character strings are passed between the application and the GSSAPI using the gss_buffer_t datatype, defined earlier.
2.1.4. Object Identifiers
2.1.4. Object Identifiers
Certain GSSAPI procedures take parameters of the type gss_OID, or Object identifier. This is a type containing ISO-defined tree- structured values, and is used by the GSSAPI caller to select an underlying security mechanism. A value of type gss_OID has the following structure:
Certain GSSAPI procedures take parameters of the type gss_OID, or Object identifier. This is a type containing ISO-defined tree- structured values, and is used by the GSSAPI caller to select an underlying security mechanism. A value of type gss_OID has the following structure:
typedef struct gss_OID_desc_struct {
OM_uint32 length;
void *elements;
} gss_OID_desc, *gss_OID;
typedef struct gss_OID_desc_struct { OM_uint32 length; void *elements; } gss_OID_desc, *gss_OID;
Wray [Page 5] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 5] RFC 1509 GSSAPI - Overview and C bindings September 1993
The elements field of this structure points to the first byte of an
octet string containing the ASN.1 BER encoding of the value of the
gss_OID. The length field contains the number of bytes in this
value. For example, the gss_OID value corresponding to {iso(1)
identified- oganization(3) icd-ecma(12) member-company(2) dec(1011)
cryptoAlgorithms(7) SPX(5)} meaning SPX (Digital's X.509
authentication mechanism) has a length field of 7 and an elements
field pointing to seven octets containing the following octal values:
53,14,2,207,163,7,5. GSSAPI implementations should provide constant
gss_OID values to allow callers to request any supported mechanism,
although applications are encouraged on portability grounds to accept
the default mechanism. gss_OID values should also be provided to
allow applications to specify particular name types (see section
2.1.10). Applications should treat gss_OID_desc values returned by
GSSAPI routines as read-only. In particular, the application should
not attempt to deallocate them. The gss_OID_desc datatype is
equivalent to the X/Open OM_object_identifier datatype [2].
The elements field of this structure points to the first byte of an octet string containing the ASN.1 BER encoding of the value of the gss_OID. The length field contains the number of bytes in this value. For example, the gss_OID value corresponding to {iso(1) identified- oganization(3) icd-ecma(12) member-company(2) dec(1011) cryptoAlgorithms(7) SPX(5)} meaning SPX (Digital's X.509 authentication mechanism) has a length field of 7 and an elements field pointing to seven octets containing the following octal values: 53,14,2,207,163,7,5. GSSAPI implementations should provide constant gss_OID values to allow callers to request any supported mechanism, although applications are encouraged on portability grounds to accept the default mechanism. gss_OID values should also be provided to allow applications to specify particular name types (see section 2.1.10). Applications should treat gss_OID_desc values returned by GSSAPI routines as read-only. In particular, the application should not attempt to deallocate them. The gss_OID_desc datatype is equivalent to the X/Open OM_object_identifier datatype [2].
2.1.5. Object Identifier Sets
2.1.5. Object Identifier Sets
Certain GSSAPI procedures take parameters of the type gss_OID_set. This type represents one or more object identifiers (section 2.1.4). A gss_OID_set object has the following structure:
Certain GSSAPI procedures take parameters of the type gss_OID_set. This type represents one or more object identifiers (section 2.1.4). A gss_OID_set object has the following structure:
typedef struct gss_OID_set_desc_struct {
int count;
gss_OID elements;
} gss_OID_set_desc, *gss_OID_set;
typedef struct gss_OID_set_desc_struct { int count; gss_OID elements; } gss_OID_set_desc, *gss_OID_set;
The count field contains the number of OIDs within the set. The elements field is a pointer to an array of gss_OID_desc objects, each of which describes a single OID. gss_OID_set values are used to name the available mechanisms supported by the GSSAPI, to request the use of specific mechanisms, and to indicate which mechanisms a given credential supports. Storage associated with gss_OID_set values returned to the application by the GSSAPI may be deallocated by the gss_release_oid_set routine.
The count field contains the number of OIDs within the set. The elements field is a pointer to an array of gss_OID_desc objects, each of which describes a single OID. gss_OID_set values are used to name the available mechanisms supported by the GSSAPI, to request the use of specific mechanisms, and to indicate which mechanisms a given credential supports. Storage associated with gss_OID_set values returned to the application by the GSSAPI may be deallocated by the gss_release_oid_set routine.
2.1.6. Credentials
2.1.6. Credentials
A credential handle is a caller-opaque atomic datum that identifies a GSSAPI credential data structure. It is represented by the caller- opaque type gss_cred_id_t, which may be implemented as either an arithmetic or a pointer type. Credentials describe a principal, and they give their holder the ability to act as that principal. The GSSAPI does not make the actual credentials available to applications; instead the credential handle is used to identify a particular credential, held internally by GSSAPI or underlying
A credential handle is a caller-opaque atomic datum that identifies a GSSAPI credential data structure. It is represented by the caller- opaque type gss_cred_id_t, which may be implemented as either an arithmetic or a pointer type. Credentials describe a principal, and they give their holder the ability to act as that principal. The GSSAPI does not make the actual credentials available to applications; instead the credential handle is used to identify a particular credential, held internally by GSSAPI or underlying
Wray [Page 6] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 6] RFC 1509 GSSAPI - Overview and C bindings September 1993
mechanism. Thus the credential handle contains no security-relavent information, and requires no special protection by the application. Depending on the implementation, a given credential handle may refer to different credentials when presented to the GSSAPI by different callers. Individual GSSAPI implementations should define both the scope of a credential handle and the scope of a credential itself (which must be at least as wide as that of a handle). Possibilities for credential handle scope include the process that acquired the handle, the acquiring process and its children, or all processes sharing some local identification information (e.g., UID). If no handles exist by which a given credential may be reached, the GSSAPI may delete the credential.
mechanism. Thus the credential handle contains no security-relavent information, and requires no special protection by the application. Depending on the implementation, a given credential handle may refer to different credentials when presented to the GSSAPI by different callers. Individual GSSAPI implementations should define both the scope of a credential handle and the scope of a credential itself (which must be at least as wide as that of a handle). Possibilities for credential handle scope include the process that acquired the handle, the acquiring process and its children, or all processes sharing some local identification information (e.g., UID). If no handles exist by which a given credential may be reached, the GSSAPI may delete the credential.
Certain routines allow credential handle parameters to be omitted to indicate the use of a default credential. The mechanism by which a default credential is established and its scope should be defined by the individual GSSAPI implementation.
Certain routines allow credential handle parameters to be omitted to indicate the use of a default credential. The mechanism by which a default credential is established and its scope should be defined by the individual GSSAPI implementation.
2.1.7. Contexts
2.1.7. Contexts
The gss_ctx_id_t data type contains a caller-opaque atomic value that identifies one end of a GSSAPI security context. It may be implemented as either an arithmetic or a pointer type. Depending on the implementation, a given gss_ctx_id_t value may refer to different GSSAPI security contexts when presented to the GSSAPI by different callers. The security context holds state information about each end of a peer communication, including cryptographic state information. Individual GSSAPI implementations should define the scope of a context. Since no way is provided by which a new gss_ctx_id_t value may be obtained for an existing context, the scope of a context should be the same as the scope of a gss_ctx_id_t.
The gss_ctx_id_t data type contains a caller-opaque atomic value that identifies one end of a GSSAPI security context. It may be implemented as either an arithmetic or a pointer type. Depending on the implementation, a given gss_ctx_id_t value may refer to different GSSAPI security contexts when presented to the GSSAPI by different callers. The security context holds state information about each end of a peer communication, including cryptographic state information. Individual GSSAPI implementations should define the scope of a context. Since no way is provided by which a new gss_ctx_id_t value may be obtained for an existing context, the scope of a context should be the same as the scope of a gss_ctx_id_t.
2.1.8. Authentication tokens
2.1.8. Authentication tokens
A token is a caller-opaque type that GSSAPI uses to maintain synchronization between the context data structures at each end of a GSSAPI security context. The token is a cryptographically protected bit-string, generated by the underlying mechanism at one end of a GSSAPI security context for use by the peer mechanism at the other end. Encapsulation (if required) and transfer of the token are the responsibility of the peer applications. A token is passed between the GSSAPI and the application using the gss_buffer_t conventions.
A token is a caller-opaque type that GSSAPI uses to maintain synchronization between the context data structures at each end of a GSSAPI security context. The token is a cryptographically protected bit-string, generated by the underlying mechanism at one end of a GSSAPI security context for use by the peer mechanism at the other end. Encapsulation (if required) and transfer of the token are the responsibility of the peer applications. A token is passed between the GSSAPI and the application using the gss_buffer_t conventions.
2.1.9. Status values
2.1.9. Status values
One or more status codes are returned by each GSSAPI routine. Two distinct sorts of status codes are returned. These are termed GSS status codes and Mechanism status codes.
One or more status codes are returned by each GSSAPI routine. Two distinct sorts of status codes are returned. These are termed GSS status codes and Mechanism status codes.
Wray [Page 7] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 7] RFC 1509 GSSAPI - Overview and C bindings September 1993
2.1.9.1. GSS status codes
2.1.9.1. GSS status codes
GSSAPI routines return GSS status codes as their OM_uint32 function value. These codes indicate errors that are independent of the underlying mechanism used to provide the security service. The errors that can be indicated via a GSS status code are either generic API routine errors (errors that are defined in the GSSAPI specification) or calling errors (errors that are specific to these bindings).
GSSAPI routines return GSS status codes as their OM_uint32 function value. These codes indicate errors that are independent of the underlying mechanism used to provide the security service. The errors that can be indicated via a GSS status code are either generic API routine errors (errors that are defined in the GSSAPI specification) or calling errors (errors that are specific to these bindings).
A GSS status code can indicate a single fatal generic API error from the routine and a single calling error. In addition, supplementary status information may be indicated via the setting of bits in the supplementary info field of a GSS status code.
A GSS status code can indicate a single fatal generic API error from the routine and a single calling error. In addition, supplementary status information may be indicated via the setting of bits in the supplementary info field of a GSS status code.
These errors are encoded into the 32-bit GSS status code as follows:
These errors are encoded into the 32-bit GSS status code as follows:
MSB LSB
|------------------------------------------------------------|
| Calling Error | Routine Error | Supplementary Info |
|------------------------------------------------------------|
Bit 31 24 23 16 15 0
MSB LSB |------------------------------------------------------------| | Calling Error | Routine Error | Supplementary Info | |------------------------------------------------------------| Bit 31 24 23 16 15 0
Hence if a GSSAPI routine returns a GSS status code whose upper 16 bits contain a non-zero value, the call failed. If the calling error field is non-zero, the invoking application's call of the routine was erroneous. Calling errors are defined in table 5-1. If the routine error field is non-zero, the routine failed for one of the routine- specific reasons listed below in table 5-2. Whether or not the upper 16 bits indicate a failure or a success, the routine may indicate additional information by setting bits in the supplementary info field of the status code. The meaning of individual bits is listed below in table 5-3.
Hence if a GSSAPI routine returns a GSS status code whose upper 16 bits contain a non-zero value, the call failed. If the calling error field is non-zero, the invoking application's call of the routine was erroneous. Calling errors are defined in table 5-1. If the routine error field is non-zero, the routine failed for one of the routine- specific reasons listed below in table 5-2. Whether or not the upper 16 bits indicate a failure or a success, the routine may indicate additional information by setting bits in the supplementary info field of the status code. The meaning of individual bits is listed below in table 5-3.
Table 5-1 Calling Errors
Table 5-1 Calling Errors
Name Value in Meaning
Field
GSS_S_CALL_INACCESSIBLE_READ 1 A required input
parameter could
not be read.
GSS_S_CALL_INACCESSIBLE_WRITE 2 A required output
parameter could
not be written.
GSS_S_CALL_BAD_STRUCTURE 3 A parameter was
malformed
Name Value in Meaning Field GSS_S_CALL_INACCESSIBLE_READ 1 A required input parameter could not be read. GSS_S_CALL_INACCESSIBLE_WRITE 2 A required output parameter could not be written. GSS_S_CALL_BAD_STRUCTURE 3 A parameter was malformed
Wray [Page 8] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 8] RFC 1509 GSSAPI - Overview and C bindings September 1993
Table 5-2 Routine Errors
Table 5-2 Routine Errors
Name Value in Meaning
Field
Name Value in Meaning Field
GSS_S_BAD_MECH 1 An unsupported mechanism was
requested
GSS_S_BAD_NAME 2 An invalid name was supplied
GSS_S_BAD_NAMETYPE 3 A supplied name was of an
unsupported type
GSS_S_BAD_BINDINGS 4 Incorrect channel bindings
were supplied
GSS_S_BAD_STATUS 5 An invalid status code was
supplied
GSS_S_BAD_MECH 1 An unsupported mechanism was requested GSS_S_BAD_NAME 2 An invalid name was supplied GSS_S_BAD_NAMETYPE 3 A supplied name was of an unsupported type GSS_S_BAD_BINDINGS 4 Incorrect channel bindings were supplied GSS_S_BAD_STATUS 5 An invalid status code was supplied
GSS_S_BAD_SIG 6 A token had an invalid
signature
GSS_S_NO_CRED 7 No credentials were supplied
GSS_S_NO_CONTEXT 8 No context has been
established
GSS_S_DEFECTIVE_TOKEN 9 A token was invalid
GSS_S_DEFECTIVE_CREDENTIAL 10 A credential was invalid
GSS_S_CREDENTIALS_EXPIRED 11 The referenced credentials
have expired
GSS_S_CONTEXT_EXPIRED 12 The context has expired
GSS_S_FAILURE 13 Miscellaneous failure
(see text)
GSS_S_BAD_SIG 6 A token had an invalid signature GSS_S_NO_CRED 7 No credentials were supplied GSS_S_NO_CONTEXT 8 No context has been established GSS_S_DEFECTIVE_TOKEN 9 A token was invalid GSS_S_DEFECTIVE_CREDENTIAL 10 A credential was invalid GSS_S_CREDENTIALS_EXPIRED 11 The referenced credentials have expired GSS_S_CONTEXT_EXPIRED 12 The context has expired GSS_S_FAILURE 13 Miscellaneous failure (see text)
Table 5-3 Supplementary Status Bits
Table 5-3 Supplementary Status Bits
Name Bit Number Meaning
GSS_S_CONTINUE_NEEDED 0 (LSB) The routine must be called
again to complete its
function.
See routine documentation for
detailed description.
GSS_S_DUPLICATE_TOKEN 1 The token was a duplicate of
an earlier token
GSS_S_OLD_TOKEN 2 The token's validity period
has expired
GSS_S_UNSEQ_TOKEN 3 A later token has already been
processed
Name Bit Number Meaning GSS_S_CONTINUE_NEEDED 0 (LSB) The routine must be called again to complete its function. See routine documentation for detailed description. GSS_S_DUPLICATE_TOKEN 1 The token was a duplicate of an earlier token GSS_S_OLD_TOKEN 2 The token's validity period has expired GSS_S_UNSEQ_TOKEN 3 A later token has already been processed
The routine documentation also uses the name GSS_S_COMPLETE, which is a zero value, to indicate an absence of any API errors or supplementary information bits.
The routine documentation also uses the name GSS_S_COMPLETE, which is a zero value, to indicate an absence of any API errors or supplementary information bits.
Wray [Page 9] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 9] RFC 1509 GSSAPI - Overview and C bindings September 1993
All GSS_S_xxx symbols equate to complete OM_uint32 status codes, rather than to bitfield values. For example, the actual value of the symbol GSS_S_BAD_NAMETYPE (value 3 in the routine error field) is 3 << 16.
All GSS_S_xxx symbols equate to complete OM_uint32 status codes, rather than to bitfield values. For example, the actual value of the symbol GSS_S_BAD_NAMETYPE (value 3 in the routine error field) is 3 << 16.
The macros GSS_CALLING_ERROR(), GSS_ROUTINE_ERROR() and GSS_SUPPLEMENTARY_INFO() are provided, each of which takes a GSS status code and removes all but the relevant field. For example, the value obtained by applying GSS_ROUTINE_ERROR to a status code removes the calling errors and supplementary info fields, leaving only the routine errors field. The values delivered by these macros may be directly compared with a GSS_S_xxx symbol of the appropriate type. The macro GSS_ERROR() is also provided, which when applied to a GSS status code returns a non-zero value if the status code indicated a calling or routine error, and a zero value otherwise.
The macros GSS_CALLING_ERROR(), GSS_ROUTINE_ERROR() and GSS_SUPPLEMENTARY_INFO() are provided, each of which takes a GSS status code and removes all but the relevant field. For example, the value obtained by applying GSS_ROUTINE_ERROR to a status code removes the calling errors and supplementary info fields, leaving only the routine errors field. The values delivered by these macros may be directly compared with a GSS_S_xxx symbol of the appropriate type. The macro GSS_ERROR() is also provided, which when applied to a GSS status code returns a non-zero value if the status code indicated a calling or routine error, and a zero value otherwise.
A GSSAPI implementation may choose to signal calling errors in a platform-specific manner instead of, or in addition to the routine value; routine errors and supplementary info should be returned via routine status values only.
A GSSAPI implementation may choose to signal calling errors in a platform-specific manner instead of, or in addition to the routine value; routine errors and supplementary info should be returned via routine status values only.
2.1.9.2. Mechanism-specific status codes
2.1.9.2. Mechanism-specific status codes
GSSAPI routines return a minor_status parameter, which is used to indicate specialized errors from the underlying security mechanism. This parameter may contain a single mechanism-specific error, indicated by a OM_uint32 value.
GSSAPI routines return a minor_status parameter, which is used to indicate specialized errors from the underlying security mechanism. This parameter may contain a single mechanism-specific error, indicated by a OM_uint32 value.
The minor_status parameter will always be set by a GSSAPI routine, even if it returns a calling error or one of the generic API errors indicated above as fatal, although other output parameters may remain unset in such cases. However, output parameters that are expected to return pointers to storage allocated by a routine must always set set by the routine, even in the event of an error, although in such cases the GSSAPI routine may elect to set the returned parameter value to NULL to indicate that no storage was actually allocated. Any length field associated with such pointers (as in a gss_buffer_desc structure) should also be set to zero in such cases.
The minor_status parameter will always be set by a GSSAPI routine, even if it returns a calling error or one of the generic API errors indicated above as fatal, although other output parameters may remain unset in such cases. However, output parameters that are expected to return pointers to storage allocated by a routine must always set set by the routine, even in the event of an error, although in such cases the GSSAPI routine may elect to set the returned parameter value to NULL to indicate that no storage was actually allocated. Any length field associated with such pointers (as in a gss_buffer_desc structure) should also be set to zero in such cases.
The GSS status code GSS_S_FAILURE is used to indicate that the underlying mechanism detected an error for which no specific GSS status code is defined. The mechanism status code will provide more details about the error.
The GSS status code GSS_S_FAILURE is used to indicate that the underlying mechanism detected an error for which no specific GSS status code is defined. The mechanism status code will provide more details about the error.
2.1.10. Names
2.1.10. Names
A name is used to identify a person or entity. GSSAPI authenticates the relationship between a name and the entity claiming the name.
A name is used to identify a person or entity. GSSAPI authenticates the relationship between a name and the entity claiming the name.
Wray [Page 10] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 10] RFC 1509 GSSAPI - Overview and C bindings September 1993
Two distinct representations are defined for names:
Two distinct representations are defined for names:
(a) A printable form, for presentation to a user
(a) A printable form, for presentation to a user
(b) An internal form, for presentation at the API
(b) An internal form, for presentation at the API
The syntax of a printable name is defined by the GSSAPI implementation, and may be dependent on local system configuration, or on individual user preference. The internal form provides a canonical representation of the name that is independent of configuration.
The syntax of a printable name is defined by the GSSAPI implementation, and may be dependent on local system configuration, or on individual user preference. The internal form provides a canonical representation of the name that is independent of configuration.
A given GSSAPI implementation may support names drawn from multiple namespaces. In such an implementation, the internal form of the name must include fields that identify the namespace from which the name is drawn. The namespace from which a printable name is drawn is specified by an accompanying object identifier.
A given GSSAPI implementation may support names drawn from multiple namespaces. In such an implementation, the internal form of the name must include fields that identify the namespace from which the name is drawn. The namespace from which a printable name is drawn is specified by an accompanying object identifier.
Routines (gss_import_name and gss_display_name) are provided to convert names between their printable representations and the gss_name_t type. gss_import_name may support multiple syntaxes for each supported namespace, allowing users the freedom to choose a preferred name representation. gss_display_name should use an implementation-chosen preferred syntax for each supported name-type.
Routines (gss_import_name and gss_display_name) are provided to convert names between their printable representations and the gss_name_t type. gss_import_name may support multiple syntaxes for each supported namespace, allowing users the freedom to choose a preferred name representation. gss_display_name should use an implementation-chosen preferred syntax for each supported name-type.
Comparison of internal-form names is accomplished via the gss_compare_names routine. This removes the need for the application program to understand the syntaxes of the various printable names that a given GSSAPI implementation may support.
Comparison of internal-form names is accomplished via the gss_compare_names routine. This removes the need for the application program to understand the syntaxes of the various printable names that a given GSSAPI implementation may support.
Storage is allocated by routines that return gss_name_t values. A procedure, gss_release_name, is provided to free storage associated with a name.
Storage is allocated by routines that return gss_name_t values. A procedure, gss_release_name, is provided to free storage associated with a name.
2.1.11. Channel Bindings
2.1.11. Channel Bindings
GSSAPI supports the use of user-specified tags to identify a given context to the peer application. These tags are used to identify the particular communications channel that carries the context. Channel bindings are communicated to the GSSAPI using the following structure:
GSSAPI supports the use of user-specified tags to identify a given context to the peer application. These tags are used to identify the particular communications channel that carries the context. Channel bindings are communicated to the GSSAPI using the following structure:
Wray [Page 11] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 11] RFC 1509 GSSAPI - Overview and C bindings September 1993
typedef struct gss_channel_bindings_struct {
OM_uint32 initiator_addrtype;
gss_buffer_desc initiator_address;
OM_uint32 acceptor_addrtype;
gss_buffer_desc acceptor_address;
gss_buffer_desc application_data;
} *gss_channel_bindings_t;
typedef struct gss_channel_bindings_struct { OM_uint32 initiator_addrtype; gss_buffer_desc initiator_address; OM_uint32 acceptor_addrtype; gss_buffer_desc acceptor_address; gss_buffer_desc application_data; } *gss_channel_bindings_t;
The initiator_addrtype and acceptor_addrtype fields denote the type of addresses contained in the initiator_address and acceptor_address buffers. The address type should be one of the following:
The initiator_addrtype and acceptor_addrtype fields denote the type of addresses contained in the initiator_address and acceptor_address buffers. The address type should be one of the following:
GSS_C_AF_UNSPEC Unspecified address type
GSS_C_AF_LOCAL Host-local address type
GSS_C_AF_INET DARPA Internet address type
GSS_C_AF_IMPLINK ARPAnet IMP address type (eg IP)
GSS_C_AF_PUP pup protocols (eg BSP) address type
GSS_C_AF_CHAOS MIT CHAOS protocol address type
GSS_C_AF_NS XEROX NS address type
GSS_C_AF_NBS nbs address type
GSS_C_AF_ECMA ECMA address type
GSS_C_AF_DATAKIT datakit protocols address type
GSS_C_AF_CCITT CCITT protocols (eg X.25)
GSS_C_AF_SNA IBM SNA address type
GSS_C_AF_DECnet DECnet address type
GSS_C_AF_DLI Direct data link interface address type
GSS_C_AF_LAT LAT address type
GSS_C_AF_HYLINK NSC Hyperchannel address type
GSS_C_AF_APPLETALK AppleTalk address type
GSS_C_AF_BSC BISYNC 2780/3780 address type
GSS_C_AF_DSS Distributed system services address type
GSS_C_AF_OSI OSI TP4 address type
GSS_C_AF_X25 X25
GSS_C_AF_NULLADDR No address specified
GSS_C_AF_UNSPEC Unspecified address type GSS_C_AF_LOCAL Host-local address type GSS_C_AF_INET DARPA Internet address type GSS_C_AF_IMPLINK ARPAnet IMP address type (eg IP) GSS_C_AF_PUP pup protocols (eg BSP) address type GSS_C_AF_CHAOS MIT CHAOS protocol address type GSS_C_AF_NS XEROX NS address type GSS_C_AF_NBS nbs address type GSS_C_AF_ECMA ECMA address type GSS_C_AF_DATAKIT datakit protocols address type GSS_C_AF_CCITT CCITT protocols (eg X.25) GSS_C_AF_SNA IBM SNA address type GSS_C_AF_DECnet DECnet address type GSS_C_AF_DLI Direct data link interface address type GSS_C_AF_LAT LAT address type GSS_C_AF_HYLINK NSC Hyperchannel address type GSS_C_AF_APPLETALK AppleTalk address type GSS_C_AF_BSC BISYNC 2780/3780 address type GSS_C_AF_DSS Distributed system services address type GSS_C_AF_OSI OSI TP4 address type GSS_C_AF_X25 X25 GSS_C_AF_NULLADDR No address specified
Note that these name address families rather than specific addressing formats. For address families that contain several alternative address forms, the initiator_address and acceptor_address fields must contain sufficient information to determine which address form is used. When not otherwise specified, addresses should be specified in network byte-order.
これらが特定のアドレス指定形式よりむしろファミリーとアドレスを命名することに注意してください。 いくつかの代替アドレスフォームを含むアドレスファミリーのために、創始者_アドレスとアクセプタ_アドレス・フィールドはどのアドレスフォームが使用されているかを決定できるくらいの情報を含まなければなりません。 別の方法で指定されないと、アドレスはネットワークバイトオーダーで指定されるべきです。
Conceptually, the GSSAPI concatenates the initiator_addrtype, initiator_address, acceptor_addrtype, acceptor_address and application_data to form an octet string. The mechanism signs this octet string, and binds the signature to the context establishment token emitted by gss_init_sec_context. The same bindings are presented by the context acceptor to gss_accept_sec_context, and a
概念的に、GSSAPIは八重奏ストリングを形成する創始者_addrtype、創始者_アドレス、アクセプタ_addrtype、アクセプタ_アドレス、およびアプリケーション_データを連結します。 メカニズムは、gss_イニット_秒_文脈によって放たれた文脈設立トークンに、この八重奏ストリングに署名して、署名を縛ります。 結合がgss_への文脈アクセプタによって提示される同じくらいは_秒_文脈、およびaを受け入れます。
Wray [Page 12] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[12ページ]RFC1509GSSAPI--概要とC結合1993年9月
signature is calculated in the same way. The calculated signature is compared with that found in the token, and if the signatures differ, gss_accept_sec_context will return a GSS_S_BAD_BINDINGS error, and the context will not be established. Some mechanisms may include the actual channel binding data in the token (rather than just a signature); applications should therefore not use confidential data as channel-binding components. Individual mechanisms may impose additional constraints on addresses and address types that may appear in channel bindings. For example, a mechanism may verify that the initiator_address field of the channel bindings presented to gss_init_sec_context contains the correct network address of the host system.
同様に、署名は計算されます。 計算された署名はトークンで見つけられるそれと比較されます、そして、署名が異なるなら、gss_は_文脈がGSS_S_BAD_BINDINGS誤りを返す_秒を受け入れます、そして、文脈は確立されないでしょう。 いくつかのメカニズムがトークン(まさしく署名よりむしろ)にデータを縛る実際のチャンネルを含むかもしれません。 したがって、アプリケーションはチャンネルを拘束力があるコンポーネントとして秘密のデータを使用するべきではありません。 個々のメカニズムはチャンネル結合に現れるかもしれないアドレスとアドレスタイプに追加規制を課すかもしれません。 例えば、メカニズムは、gss_イニット_秒_文脈に提示されたチャンネル結合の創始者_アドレス・フィールドがホストシステムの正しいネットワーク・アドレスを含むことを確かめるかもしれません。
2.1.12. Optional parameters
2.1.12. 任意のパラメタ
Various parameters are described as optional. This means that they follow a convention whereby a default value may be requested. The following conventions are used for omitted parameters. These conventions apply only to those parameters that are explicitly documented as optional.
様々なパラメタは任意であると記述されています。 これは、デフォルト値が要求されているかもしれないコンベンションに続くことを意味します。 以下のコンベンションは省略されたパラメタに使用されます。 これらのコンベンションは任意であるとして明らかに記録されるそれらのパラメタだけに適用されます。
2.1.12.1. gss_buffer_t types
2.1.12.1. gss_バッファ_tはタイプされます。
Specify GSS_C_NO_BUFFER as a value. For an input parameter this signifies that default behavior is requested, while for an output parameter it indicates that the information that would be returned via the parameter is not required by the application.
値として_GSS_Cいいえ_BUFFERを指定してください。 入力パラメタに関しては、これは、デフォルトの振舞いが要求されているのを意味します、出力パラメタに関してパラメタで返される情報はアプリケーションで必要でないことを示しますが。
2.1.12.2. Integer types (input)
2.1.12.2. 整数型(入力)
Individual parameter documentation lists values to be used to indicate default actions.
個々のパラメタドキュメンテーションは、デフォルト動作を示すのに使用されるために値を記載します。
2.1.12.3. Integer types (output)
2.1.12.3. 整数型(出力)
Specify NULL as the value for the pointer.
指針のための値としてNULLを指定してください。
2.1.12.4. Pointer types
2.1.12.4. ポインター型
Specify NULL as the value.
値としてNULLを指定してください。
2.1.12.5. Object IDs
2.1.12.5. オブジェクトID
Specify GSS_C_NULL_OID as the value.
値として_GSS_C NULL_OIDを指定してください。
2.1.12.6. Object ID Sets
2.1.12.6. オブジェクトIDセット
Specify GSS_C_NULL_OID_SET as the value.
値として_GSS_C NULL_OID_SETを指定してください。
Wray [Page 13] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[13ページ]RFC1509GSSAPI--概要とC結合1993年9月
2.1.12.7. Credentials
2.1.12.7. 資格証明書
Specify GSS_C_NO_CREDENTIAL to use the default credential handle.
_GSS_Cいいえ_CREDENTIALを指定して、デフォルト資格証明書ハンドルを使用してください。
2.1.12.8. Channel Bindings
2.1.12.8. チャンネル結合
Specify GSS_C_NO_CHANNEL_BINDINGS to indicate that channel bindings are not to be used.
_GSS_Cいいえ_CHANNEL_BINDINGSを指定して、チャンネル結合が使用されていないことであることを示してください。
3. GSSAPI routine descriptions
3. GSSAPIの通常の記述
2.1. gss_acquire_cred
2.1. gss_は_信用を取得します。
OM_uint32 gss_acquire_cred (
OM_uint32 * minor_status,
gss_name_t desired_name,
OM_uint32 time_req,
gss_OID_set desired_mechs,
int cred_usage,
gss_cred_id_t * output_cred_handle,
gss_OID_set * actual_mechs,
OM_int32 * time_rec)
Purpose:
OM_uint32 gss_は_信用(OM_uint32*小さい方の_状態、gssの_の名前_t必要な_名、OM_uint32時間_req、OID_が設定したgss_は_mechsを望んでいました、int信用_用法、gss_信用_イド_t*出力_信用_ハンドル、gss_OID_セット*の実際の_mechs、OM_int32*時間_rec)目的を帯びます:
Allows an application to acquire a handle for a pre-existing credential by name. GSSAPI implementations must impose a local access-control policy on callers of this routine to prevent unauthorized callers from acquiring credentials to which they are not entitled. This routine is not intended to provide a "login to the network" function, as such a function would result in the creation of new credentials rather than merely acquiring a handle to existing credentials. Such functions, if required, should be defined in implementation-specific extensions to the API.
アプリケーションが名前の先在の資格証明書のためにハンドルを入手するのを許容します。 GSSAPI実装は、権限のない訪問者がそれらが権利を与えられない資格証明書を取得するのを防ぐためにローカルのアクセス制御方針をこのルーチンの訪問者に課さなければなりません。 このルーチンが「ネットワークへのログイン」機能を提供することを意図しません、そのような機能が単に既存の資格証明書にハンドルを入手するよりむしろ新しい資格証明書の作成をもたらしているだろうという間。 必要なら、そのような機能は実装特有の拡大でAPIと定義されるべきです。
If credential acquisition is time-consuming for a mechanism, the mechanism may chooses to delay the actual acquisition until the credential is required (e.g., by gss_init_sec_context or gss_accept_sec_context). Such mechanism-specific implementation decisions should be invisible to the calling application; thus a call of gss_inquire_cred immediately following the call of gss_acquire_cred must return valid credential data, and may therefore incur the overhead of a deferred credential acquisition.
メカニズムにおいて、資格証明書獲得が手間がかかっているなら、メカニズムは手間がかかっています。資格証明書が必要になるまで(例えば、gss_イニットの_秒_文脈かgss_で、_秒_文脈を受け入れてください)実際の獲得を遅らせるのを選びます。 そのようなメカニズム特有の実装決定は呼ぶアプリケーションに目に見えないはずです。 したがって、gss_の呼び出しは、すぐに_が入手するgssでは、_信用が有効な資格証明データを返さなければならないという要求に続いて、_信用について問い合わせて、したがって、延期された資格証明獲得のオーバーヘッドを被るかもしれません。
Parameters:
パラメタ:
desired_name gss_name_t, read
Name of principal whose credential
should be acquired
必要な_名前gss_名前_t資格証明書が取得されるべきである主体のNameが読まれて、
Wray [Page 14] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[14ページ]RFC1509GSSAPI--概要とC結合1993年9月
time_req integer, read
number of seconds that credentials
should remain valid
時間_req整数、資格証明書が有効なままで残るべきである秒の読み出し回数
desired_mechs Set of Object IDs, read
set of underlying security mechanisms that
may be used. GSS_C_NULL_OID_SET may be used
to obtain an implementation-specific default.
使用されるかもしれない基本的なセキュリティー対策のセットに読み込まれて、_Object IDのmechs Setを望んでいました。 GSS_C_NULL_OID_SETは、実装特有のデフォルトを得るのに使用されるかもしれません。
cred_usage integer, read
GSS_C_BOTH - Credentials may be used
either to initiate or accept
security contexts.
GSS_C_INITIATE - Credentials will only be
used to initiate security
contexts.
GSS_C_ACCEPT - Credentials will only be used to
accept security contexts.
信用_用法整数、--_GSS_C BOTHが読まれて、資格証明書は、セキュリティ文脈を開始するか、または受け入れるのに使用されるかもしれません。 GSS_C_INITIATE--資格証明書は、セキュリティ文脈を開始するのに使用されるだけでしょう。 GSS_C_ACCEPT--資格証明書は、セキュリティ文脈を受け入れるのに使用されるだけでしょう。
output_cred_handle gss_cred_id_t, modify
The returned credential handle.
_信用_ハンドルgss_信用_イド_tを出力してください、そして、返された資格証明ハンドルを変更してください。
actual_mechs Set of Object IDs, modify, optional
The set of mechanisms for which the
credential is valid. Specify NULL
if not required.
実際、_Object IDのmechs Set、変更、任意である、資格証明書が有効であるメカニズムのセット。 必要でないなら、NULLを指定してください。
time_rec Integer, modify, optional
Actual number of seconds for which the
returned credentials will remain valid. If the
implementation does not support expiration of
credentials, the value GSS_C_INDEFINITE will
be returned. Specify NULL if not required
時間_rec Integer、変更、返された資格証明書が有効なままで残っている任意のActual秒数。 実装が資格証明書の満了をサポートしないと、値GSS_Cの_INDEFINITEを返すでしょう。 必要でないなら、NULLを指定してください。
minor_status Integer, modify
Mechanism specific status code.
Function value:
小さい方の_状態Integer、Mechanismの特定のステータスコードを変更してください。 機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_BAD_MECH Unavailable mechanism requested
BAD_MECH Unavailableメカニズムが要求したGSS_S_
GSS_S_BAD_NAMETYPE Type contained within desired_name parameter is
not supported
BAD_NAMETYPE Typeが必要な_名前パラメタの中に含んだGSS_S_はサポートされません。
GSS_S_BAD_NAME Value supplied for desired_name parameter is
BAD_NAME Valueが必要な_名前パラメタに供給したGSS_S_はそうです。
Wray [Page 15] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[15ページ]RFC1509GSSAPI--概要とC結合1993年9月
ill-formed.
不適格。
GSS_S_FAILURE Unspecified failure. The minor_status parameter
contains more detailed information
GSS_S_FAILURE Unspecifiedの故障。 小さい方の_ステータスパラメタは、より詳細な情報を含んでいます。
3.2. gss_release_cred
3.2. gss_リリース_信用
OM_uint32 gss_release_cred (
OM_uint32 * minor_status,
gss_cred_id_t * cred_handle)
OM_uint32 gss_リリース_信用(OM_uint32*小さい方の_状態、gss_信用_イド_t*信用_ハンドル)
Purpose:
目的:
Informs GSSAPI that the specified credential handle is no longer required by the process. When all processes have released a credential, it will be deleted.
指定された資格証明ハンドルがもうプロセスによって必要とされないことをGSSAPIに知らせます。 すべてのプロセスが資格証明書をリリースしたとき、それは削除されるでしょう。
Parameters:
パラメタ:
cred_handle gss_cred_id_t, modify, optional
buffer containing opaque credential
handle. If GSS_C_NO_CREDENTIAL is supplied,
the default credential will be released
信用_ハンドルgss_信用_イド_t、変更、任意のバッファ含有不透明な資格証明ハンドル。 GSS_C_いいえ_CREDENTIALを供給すると、デフォルト資格証明書をリリースするでしょう。
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_NO_CRED Credentials could not be accessed.
GSS_S_いいえ_CRED Credentialsにアクセスできませんでした。
Wray [Page 16] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[16ページ]RFC1509GSSAPI--概要とC結合1993年9月
3.3. gss_init_sec_context
3.3. gss_イニット_秒_文脈
OM_uint32 gss_init_sec_context (
OM_uint32 * minor_status,
gss_cred_id_t claimant_cred_handle,
gss_ctx_id_t * context_handle,
gss_name_t target_name,
gss_OID mech_type,
int req_flags,
int time_req,
gss_channel_bindings_t
input_chan_bindings,
gss_buffer_t input_token
gss_OID * actual_mech_type,
gss_buffer_t output_token,
int * ret_flags,
OM_uint32 * time_rec )
OM_uint32 gss_イニット_秒_文脈小さい方..状態..信用..イド..主張者..信用..ハンドル..イド..文脈..ハンドル..名前..目標..名前..タイプ..旗..時間..チャンネル..結合..入力..結合..バッファ..入力..トークン..実際..タイプ..バッファ..出力..トークン..浸水..旗..時間
Purpose:
目的:
Initiates the establishment of a security context between the application and a remote peer. Initially, the input_token parameter should be specified as GSS_C_NO_BUFFER. The routine may return a output_token which should be transferred to the peer application, where the peer application will present it to gss_accept_sec_context. If no token need be sent, gss_init_sec_context will indicate this by setting the length field of the output_token argument to zero. To complete the context establishment, one or more reply tokens may be required from the peer application; if so, gss_init_sec_context will return a status indicating GSS_S_CONTINUE_NEEDED in which case it should be called again when the reply token is received from the peer application, passing the token to gss_init_sec_context via the input_token parameters.
アプリケーションとリモート同輩の間のセキュリティ文脈の確立を開始します。 初めは、入力_トークンパラメタは_GSS_Cいいえ_BUFFERとして指定されるべきです。 ルーチンは同輩アプリケーションに移されるべきである出力_トークンを返すかもしれなくて、同輩アプリケーションがどこにgss_にそれを提示するかが_秒_文脈を受け入れます。 トークンを全く送る必要はないと、gss_イニット_秒_文脈は、出力_トークン議論の長さの分野をゼロに設定することによって、これを示すでしょう。 文脈設立を終了するために、1つ以上の回答トークンが同輩アプリケーションから必要であるかもしれません。 そうだとすれば、gss_イニット_秒_文脈は同輩アプリケーションから回答トークンを受け取るときそれが再びどのケースに呼ばれるべきであるかでCONTINUE_が必要としたGSS_S_を示す状態を返すでしょう、入力_トークンパラメタでgss_イニット_秒_文脈にトークンを通過して。
The values returned via the ret_flags and time_rec parameters are not defined unless the routine returns GSS_S_COMPLETE.
を通して値が戻った、_旗とルーチンが_GSS_S COMPLETEを返さない場合recパラメタが定義されない時間_を浸水させてください。
Parameters:
パラメタ:
claimant_cred_handle gss_cred_id_t, read, optional
handle for credentials claimed. Supply
GSS_C_NO_CREDENTIAL to use default
credentials.
gss_信用_イド_tを扱って、読まれた主張者_信用_、要求された資格証明書のための任意のハンドル。 _GSS_Cいいえ_CREDENTIALを供給して、デフォルト資格証明書を使用してください。
context_handle gss_ctx_id_t, read/modify
context handle for new context. Supply
GSS_C_NO_CONTEXT for first call; use value
returned by first call in continuation calls.
新しい関係のために文脈ハンドルを文脈_はgss_ctx_イド_tを扱って、読むか、または変更してください。 _GSS_Cいいえ_CONTEXTを準備ラッパに供給してください。 継続における準備ラッパで返された使用価値は呼びます。
Wray [Page 17] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[17ページ]RFC1509GSSAPI--概要とC結合1993年9月
target_name gss_name_t, read
Name of target
_名前gss_名前_tを狙ってください、そして、目標のNameを読んでください。
mech_type OID, read, optional
Object ID of desired mechanism. Supply
GSS_C_NULL_OID to obtain an implementation
specific default
mech_はOIDをタイプして、読んで、任意のObjectは必要なメカニズムのIDです。 _GSS_C NULL_OIDを供給して、実装の特定のデフォルトを得てください。
req_flags bit-mask, read
Contains four independent flags, each of
which requests that the context support a
specific service option. Symbolic
names are provided for each flag, and the
symbolic names corresponding to the required
flags should be logically-ORed
together to form the bit-mask value. The
flags are:
独立者が旗を揚げさせるContains four(それのそれぞれが、文脈が特定のサービスオプションをサポートするよう要求します)は、req_がビットマスクに旗を揚げさせると読みます。 各旗に英字名を提供して、必要な旗に対応する英字名が提供するべきである、論理的である、-、ORed、ビットマスク値を形成するために、一緒にいます。 旗は以下の通りです。
GSS_C_DELEG_FLAG
True - Delegate credentials to remote peer
False - Don't delegate
GSS_C_MUTUAL_FLAG
True - Request that remote peer
authenticate itself
False - Authenticate self to remote peer
only
GSS_C_REPLAY_FLAG
True - Enable replay detection for signed
or sealed messages
False - Don't attempt to detect
replayed messages
GSS_C_SEQUENCE_FLAG
True - Enable detection of out-of-sequence
signed or sealed messages
False - Don't attempt to detect
out-of-sequence messages
_GSS_C DELEG_FLAG True(リモート同輩Falseへの代表資格証明書)は_GSS_C MUTUAL_FLAG Trueを代表として派遣しません--リモート同輩自身がFalseを認証するよう要求してください--自己を_リモート同輩GSS_CだけREPLAY_FLAG Trueまで認証してください--署名しているか密封されたメッセージFalseのために再生検出を可能にしてください--_再演されたメッセージGSS_C SEQUENCE_FLAG Trueを検出するのを試みないでください--順序が狂って署名しているか、密封されたメッセージFalseの検出を可能にしてください--順序が狂ってメッセージを検出するのを試みないでください。
time_req integer, read
Desired number of seconds for which context
should remain valid. Supply 0 to request a
default validity period.
時間_req整数文脈が有効なままで残るべきであるDesired秒数が読まれて。 0を供給して、デフォルト有効期間を要求してください。
input_chan_bindings channel bindings, read
Application-specified bindings. Allows
application to securely bind channel
identification information to the security
context.
Applicationによって指定された結合が読まれて、入力_chan_結合は結合を向けます。 アプリケーションがしっかりとセキュリティ文脈にチャネル識別情報を縛るのを許容します。
Wray [Page 18] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[18ページ]RFC1509GSSAPI--概要とC結合1993年9月
input_token buffer, opaque, read, optional (see text)
Token received from peer application.
Supply GSS_C_NO_BUFFER on initial call.
任意(テキストを見る)のトークンは、同輩アプリケーションから不明瞭な入力_トークンバッファが読んだのを受けました。 初期の呼び出しのときに_GSS_Cいいえ_BUFFERを供給してください。
actual_mech_type OID, modify
actual mechanism used.
実際の_mech_タイプOID、使用される実際のメカニズムを変更してください。
output_token buffer, opaque, modify
token to be sent to peer application. If
the length field of the returned buffer is
zero, no token need be sent to the peer
application.
出力_トークンバッファ、不透明なものは同輩アプリケーションに送られるトークンを変更します。 返されたバッファの長さの分野がゼロであるなら、トークンを全く同輩アプリケーションに送る必要はありません。
ret_flags bit-mask, modify
Contains six independent flags, each of which
indicates that the context supports a specific
service option. Symbolic names are provided
for each flag, and the symbolic names
corresponding to the required flags should be
logically-ANDed with the ret_flags value to test
whether a given option is supported by the
context. The flags are:
_旗のビットマスクを浸水させてください、そして、独立者が旗を揚げさせるContains sixを変更してください。それは、文脈が特定のサービスオプションをサポートするのをそれぞれ示します。 各旗に英字名を提供して、必要な旗に対応する英字名が提供するべきである、論理的である、-、ANDed、旗が与えられたオプションが文脈で後押しされているか否かに関係なく、テストするために評価する_を浸水させてください。 旗は以下の通りです。
GSS_C_DELEG_FLAG
True - Credentials were delegated to
the remote peer
False - No credentials were delegated
GSS_C_MUTUAL_FLAG
True - Remote peer has been asked to
authenticated itself
False - Remote peer has not been asked to
authenticate itself
GSS_C_REPLAY_FLAG
True - replay of signed or sealed messages
will be detected
False - replayed messages will not be
detected
GSS_C_SEQUENCE_FLAG
True - out-of-sequence signed or sealed
messages will be detected
False - out-of-sequence messages will not
be detected
GSS_C_CONF_FLAG
True - Confidentiality service may be
invoked by calling seal routine
False - No confidentiality service (via
seal) available. seal will provide
message encapsulation, data-origin
信任状が委任されて、どんな信任状も代表として派遣された_GSS_C MUTUAL_FLAG Trueでなかったというリモート同輩が尋ねられたリモート同輩False自身はFalseを認証しました--リモート同輩自身が_GSS_C REPLAY_FLAG Trueを認証するように頼まれていないということであったというDELEG_FLAG Trueが再演するサインされたか密封されたメッセージのGSS_C_は検出されるでしょう; 再演されたメッセージは虚偽、検出された_GSS_C FLAG TrueにSEQUENCE_ならないでしょう--順序が狂ってサインされたか、密封されたメッセージは検出されたFalseになるでしょう--順序が狂ってメッセージは検出された_GSS_C FLAG TrueにCONF_ならないでしょう--シールルーチンFalseと呼ぶことによって、秘密性サービスは呼び出されるかもしれません--利用可能な秘密性サービスがありません(シールを通した); アザラシはメッセージカプセル化、データ起源を提供するでしょう。
Wray [Page 19] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[19ページ]RFC1509GSSAPI--概観とC結合1993年9月
authentication and integrity
services only.
GSS_C_INTEG_FLAG
True - Integrity service may be invoked by
calling either gss_sign or gss_seal
routines.
False - Per-message integrity service
unavailable.
認証と保全サービス専用。 GSS_C_INTEG_FLAG True--gss_サインかgss_シールルーチンのどちらかと呼ぶことによって、保全サービスは呼び出されるかもしれません。 偽--入手できない1メッセージの保全あたりのサービス。
time_rec integer, modify, optional
number of seconds for which the context
will remain valid. If the implementation does
not support credential expiration, the value
GSS_C_INDEFINITE will be returned. Specify
NULL if not required.
時間_rec整数、変更、文脈が有効なままで残っている任意の秒数。 実現が信任している満了を支持しないと、値GSS_Cの_INDEFINITEを返すでしょう。 必要でないなら、NULLを指定してください。
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_CONTINUE_NEEDED Indicates that a token from the peer
application is required to complete thecontext, and
that gss_init_sec_context must be called again with
that token.
同輩アプリケーションからの象徴がIndicatesですが、CONTINUE_が必要としたGSS_S_がthecontextを完成するのが必要であり、再びその象徴でそのgss_イニット_秒_文脈を呼ばなければなりません。
GSS_S_DEFECTIVE_TOKEN Indicates that consistency checks performed on
the input_token failed
_GSS_S DEFECTIVE_TOKEN Indicatesはチェックが失敗された入力_象徴に実行したその一貫性です。
GSS_S_DEFECTIVE_CREDENTIAL Indicates that consistency checks
performed on the credential failed.
GSS_S、_一貫性チェックが信任状に実行したDEFECTIVE_CREDENTIAL Indicatesは失敗しました。
GSS_S_NO_CRED The supplied credentials were not valid for context
initiation, or the credential handle did not
reference any credentials.
__いいえ、CRED。GSS_S、文脈開始には、供給された信任状が有効でなかったか、または信任状ハンドルはどんな参照にもどんな信任状もしませんでした。
GSS_S_CREDENTIALS_EXPIRED The referenced credentials have expired
_GSS_S CREDENTIALS_EXPIREDは信任状が吐き出した参照箇所です。
GSS_S_BAD_BINDINGS The input_token contains different channel
bindings to those specified via the
input_chan_bindings parameter
_GSS_S BAD_BINDINGS、入力_象徴は入力_chan_結合パラメタで指定されたものに異なったチャンネル結合を含んでいます。
GSS_S_BAD_SIG The input_token contains an invalid signature, or a
signature that could not be verified
GSS_S_BAD_SIG、入力_象徴は無効の署名、または確かめることができなかった署名を含んでいます。
Wray [Page 20] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[20ページ]RFC1509GSSAPI--概観とC結合1993年9月
GSS_S_OLD_TOKEN The input_token was too old. This is a fatal error
during context establishment
_GSS_S OLD_TOKEN、入力_象徴は古過ぎました。 文脈設立の間、これは致命的な誤りです。
GSS_S_DUPLICATE_TOKEN The input_token is valid, but is a duplicate of
a token already processed. This is a fatal error
during context establishment.
_GSS_S DUPLICATE_TOKEN、入力_象徴は、有効ですが、既に処理された象徴の写しです。 文脈設立の間、これは致命的な誤りです。
GSS_S_NO_CONTEXT Indicates that the supplied context handle did not
refer to a valid context
_供給された文脈が扱ういいえ_CONTEXT IndicatesがそうするGSS_Sは有効な文脈を示しません。
GSS_S_BAD_NAMETYPE The provided target_name parameter contained an
invalid or unsupported type of name
_GSS_S BAD_NAMETYPE、パラメタという提供された目標_名前は無効の、または、サポートされないタイプの名前を含みました。
GSS_S_BAD_NAME The provided target_name parameter was ill-formed.
_GSS_S BAD_NAME、パラメタという提供された目標_名前は不適格でした。
GSS_S_FAILURE Failure. See minor_status for more information
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
3.4. gss_accept_sec_context
3.4. gss_は_秒_文脈を受け入れます。
OM_uint32 gss_accept_sec_context (
OM_uint32 * minor_status,
gss_ctx_id_t * context_handle,
gss_cred_id_t verifier_cred_handle,
gss_buffer_t input_token_buffer
gss_channel_bindings_t
input_chan_bindings,
gss_name_t * src_name,
gss_OID * mech_type,
gss_buffer_t output_token,
int * ret_flags,
OM_uint32 * time_rec,
gss_cred_id_t * delegated_cred_handle)
OM_uint32 gss_は_秒_文脈を受け入れます。小さい方..状態..イド..文脈..ハンドル..信用..イド..検証..信用..ハンドル..バッファ..入力..象徴..バッファ..チャンネル..結合..入力..結合..名前..名前..タイプ..バッファ..出力..象徴..浸水..旗..時間..信用..イド..代表として派遣する..信用..ハンドル
Purpose:
目的:
Allows a remotely initiated security context between the application and a remote peer to be established. The routine may return a output_token which should be transferred to the peer application, where the peer application will present it to gss_init_sec_context. If no token need be sent, gss_accept_sec_context will indicate this by setting the length field of the output_token argument to zero. To complete the context establishment, one or more reply tokens may be required from the peer application; if so, gss_accept_sec_context will return a status flag of GSS_S_CONTINUE_NEEDED, in which case it should be called again when the reply token is received from the peer application, passing the token to gss_accept_sec_context via the input_token parameters.
アプリケーションとリモート同輩の間の離れて開始しているセキュリティ文脈が確立されるのを許容します。 ルーチンは同輩アプリケーションに移されるべきである出力_象徴を返すかもしれません。そこでは、同輩アプリケーションがgss_イニット_秒_文脈にそれを示すでしょう。 どんな象徴も送られたgss_である必要はないなら、_文脈がゼロに合わせるために出力_象徴議論の長さの分野を設定することによってこれを示す_秒を受け入れてください。 文脈設立を終了するために、1つ以上の回答象徴が同輩アプリケーションから必要であるかもしれません。 そうだとすれば、_文脈がCONTINUE_が必要としたGSS_S_の状態旗を返す_秒はgss_は受け入れられて、gss_に象徴を渡すと、同輩アプリケーションから回答象徴を受け取るとき、再びどのケースにそれを呼ぶべきであるかで、_秒_文脈は入力_象徴パラメタで受け入れられます。
Wray [Page 21] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[21ページ]RFC1509GSSAPI--概観とC結合1993年9月
The values returned via the src_name, ret_flags, time_rec, and delegated_cred_handle parameters are not defined unless the routine returns GSS_S_COMPLETE.
src_名前で値を返して、__旗、時間recを浸水させてください。そうすれば、ルーチンが_GSS_S COMPLETEを返さない場合、代表として派遣された_信用_ハンドルパラメタは定義されません。
Parameters:
パラメタ:
context_handle gss_ctx_id_t, read/modify
context handle for new context. Supply
GSS_C_NO_CONTEXT for first call; use value
returned in subsequent calls.
新しい関係のために文脈ハンドルを文脈_はgss_ctx_イド_tを扱って、読むか、または変更してください。 _GSS_Cいいえ_CONTEXTを準備ラッパに供給してください。 使用価値はその後の呼び出しで戻りました。
verifier_cred_handle gss_cred_id_t, read, optional
Credential handle claimed by context
acceptor.
Specify GSS_C_NO_CREDENTIAL to use default
credentials. If GSS_C_NO_CREDENTIAL is
specified, but the caller has no default
credentials established, an
implementation-defined default credential
may be used.
gss_信用_イド_tを扱って、読まれた検証_信用_、文脈アクセプタによって要求された任意のCredentialハンドル。 _GSS_Cいいえ_CREDENTIALを指定して、デフォルト信任状を使用してください。 GSS_C_いいえ_CREDENTIALが指定されますが、訪問者がデフォルト信任状を全く確立させないなら、実現で定義されたデフォルト信任状は使用されるかもしれません。
input_token_buffer buffer, opaque, read
token obtained from remote application
不明瞭な入力_象徴_バッファバッファはリモートアプリケーションから入手された象徴を読みました。
input_chan_bindings channel bindings, read
Application-specified bindings. Allows
application to securely bind channel
identification information to the security
context.
Applicationによって指定された結合が読まれて、入力_chan_結合は結合を向けます。 アプリケーションがしっかりとセキュリティ文脈にチャネル識別情報を縛るのを許容します。
src_name gss_name_t, modify, optional
Authenticated name of context initiator.
After use, this name should be deallocated by
passing it to gss_release_name. If not required,
specify NULL.
src_名前gss_名前_t、変更、文脈創始者の任意のAuthenticated名。 使用の後に、この名前は、gss_リリース_名にそれを通過することによって、「反-割り当て」られるべきです。 必要でないなら、NULLを指定してください。
mech_type Object ID, modify
Security mechanism used. The returned
OID value will be a pointer into static
storage, and should be treated as read-only
by the caller.
mech_タイプObject ID、使用されるSecurityメカニズムを変更してください。 返されたOID値は、スタティックストレージへのポインタであり、訪問者によって書き込み禁止として扱われるべきです。
output_token buffer, opaque, modify
Token to be passed to peer application. If the
length field of the returned token buffer is 0,
then no token need be passed to the peer
application.
出力_象徴バッファ、不透明なものは、同輩アプリケーションに通過されるようにTokenを変更します。 返された象徴バッファの長さの分野が0であるなら、象徴は全く同輩アプリケーションに渡される必要はありません。
Wray [Page 22] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[22ページ]RFC1509GSSAPI--概観とC結合1993年9月
ret_flags bit-mask, modify
Contains six independent flags, each of
which indicates that the context supports a
specific service option. Symbolic names are
provided for each flag, and the symbolic names
corresponding to the required flags
should be logically-ANDed with the ret_flags
value to test whether a given option is
supported by the context. The flags are:
GSS_C_DELEG_FLAG
True - Delegated credentials are available
via the delegated_cred_handle
parameter
False - No credentials were delegated
GSS_C_MUTUAL_FLAG
True - Remote peer asked for mutual
authentication
False - Remote peer did not ask for mutual
authentication
GSS_C_REPLAY_FLAG
True - replay of signed or sealed messages
will be detected
False - replayed messages will not be
detected
GSS_C_SEQUENCE_FLAG
True - out-of-sequence signed or sealed
messages will be detected
False - out-of-sequence messages will not
be detected
GSS_C_CONF_FLAG
True - Confidentiality service may be
invoked by calling seal routine
False - No confidentiality service (via
seal) available. seal will
provide message encapsulation,
data-origin authentication and
integrity services only.
GSS_C_INTEG_FLAG
True - Integrity service may be invoked
by calling either gss_sign or
gss_seal routines.
False - Per-message integrity service
unavailable.
_旗のビットマスクを浸水させてください、そして、独立者が旗を揚げさせるContains sixを変更してください。それは、文脈が特定のサービスオプションをサポートするのをそれぞれ示します。 各旗に英字名を提供して、必要な旗に対応する英字名が提供するべきである、論理的である、-、ANDed、旗が与えられたオプションが文脈で後押しされているか否かに関係なく、テストするために評価する_を浸水させてください。 旗は以下の通りです。 代表として派遣された信任状は代表として派遣された_信用_ハンドルパラメタFalseを通して利用可能です--どんな信任状も代表として派遣された_GSS_C MUTUAL_FLAG Trueではありませんでした--リモート同輩は互いの認証Falseを求めました--リモート同輩が_互いの認証GSS_C REPLAY_FLAG Trueを求めなかったというDELEG_FLAG Trueが再演するサインされたか密封されたメッセージのGSS_C_はそうでしょう; 検出されたFalse--再演されたメッセージは検出された_GSS_C FLAG TrueにSEQUENCE_ならないでしょう--順序が狂ってサインされたか、密封されたメッセージは検出されたFalseになるでしょう--順序が狂ってメッセージは検出された_GSS_C FLAG TrueにCONF_ならないでしょう--シールルーチンFalseと呼ぶことによって、秘密性サービスは呼び出されるかもしれません--利用可能な秘密性サービスがありません(シールを通した); アザラシはメッセージカプセル化、データ起源認証、および保全サービスだけを提供するでしょう。 GSS_C_INTEG_FLAG True--gss_サインかgss_シールルーチンのどちらかと呼ぶことによって、保全サービスは呼び出されるかもしれません。 偽--入手できない1メッセージの保全あたりのサービス。
time_rec integer, modify, optional
number of seconds for which the context
will remain valid. Specify NULL if not required.
時間_rec整数、変更、文脈が有効なままで残っている任意の秒数。 必要でないなら、NULLを指定してください。
Wray [Page 23] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[23ページ]RFC1509GSSAPI--概観とC結合1993年9月
delegated_cred_handle
gss_cred_id_t, modify
credential handle for credentials received from
context initiator. Only valid if deleg_flag in
ret_flags is true.
代表として派遣された_信用_はgss_信用_イド_tを扱って、文脈創始者から受け取られた信任状のために信任しているハンドルを変更してください。 有効な、しかし、delegな_旗だけが中で浸水します。_旗は本当です。
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_CONTINUE_NEEDED Indicates that a token from the peer
application is required to complete the context,
and that gss_accept_sec_context must be called
again with that token.
同輩アプリケーションからの象徴がIndicatesですが、CONTINUE_が必要としたGSS_S_が文脈を完成するのが必要であり、再びその象徴でgss_が_秒_文脈を受け入れるのを呼ばなければなりません。
GSS_S_DEFECTIVE_TOKEN Indicates that consistency checks
performed on the input_token failed.
GSS_S、_一貫性チェックが入力_象徴に実行したDEFECTIVE_TOKEN Indicatesは失敗しました。
GSS_S_DEFECTIVE_CREDENTIAL Indicates that consistency checks
performed on the credential failed.
GSS_S、_一貫性チェックが信任状に実行したDEFECTIVE_CREDENTIAL Indicatesは失敗しました。
GSS_S_NO_CRED The supplied credentials were not valid for
context acceptance, or the credential handle
did not reference any credentials.
__いいえ、CRED。GSS_S、文脈承認には、供給された信任状が有効でなかったか、または信任状ハンドルはどんな参照にもどんな信任状もしませんでした。
GSS_S_CREDENTIALS_EXPIRED The referenced credentials have
expired.
_GSS_S CREDENTIALS_EXPIRED、参照をつけられた信任状は期限が切れました。
GSS_S_BAD_BINDINGS The input_token contains different channel
bindings to those specified via the
input_chan_bindings parameter.
_GSS_S BAD_BINDINGS、入力_象徴は入力_chan_結合パラメタで指定されたものに異なったチャンネル結合を含んでいます。
GSS_S_NO_CONTEXT Indicates that the supplied context handle did
not refer to a valid context.
_供給された文脈が扱ういいえ_CONTEXT IndicatesがそうするGSS_Sは有効な文脈を示しません。
GSS_S_BAD_SIG The input_token contains an invalid signature.
入力_象徴が含むGSS_S_BAD_SIG、無効の署名。
GSS_S_OLD_TOKEN The input_token was too old. This is a fatal
error during context establishment.
_GSS_S OLD_TOKEN、入力_象徴は古過ぎました。 文脈設立の間、これは致命的な誤りです。
GSS_S_DUPLICATE_TOKEN The input_token is valid, but is a
duplicate of a token already processed. This
is a fatal error during context establishment.
_GSS_S DUPLICATE_TOKEN、入力_象徴は、有効ですが、既に処理された象徴の写しです。 文脈設立の間、これは致命的な誤りです。
Wray [Page 24] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[24ページ]RFC1509GSSAPI--概観とC結合1993年9月
GSS_S_FAILURE Failure. See minor_status for more information.
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
3.5. gss_process_context_token
3.5. gss_過程_文脈_象徴
OM_uint32 gss_process_context_token (
OM_uint32 * minor_status,
gss_ctx_id_t context_handle,
gss_buffer_t token_buffer)
OM_uint32 gss_過程_文脈_象徴(OM_uint32*小さい方の_状態、gss_ctx_イド_t文脈_ハンドル、gss_バッファ_t象徴_バッファ)
Purpose:
目的:
Provides a way to pass a token to the security service. Usually, tokens are associated either with context establishment (when they would be passed to gss_init_sec_context or gss_accept_sec_context) or with per-message security service (when they would be passed to gss_verify or gss_unseal). Occasionally, tokens may be received at other times, and gss_process_context_token allows such tokens to be passed to the underlying security service for processing. At present, such additional tokens may only be generated by gss_delete_sec_context. GSSAPI implementation may use this service to implement deletion of the security context.
象徴をセキュリティー・サービスに渡す方法を提供します。 通常、象徴は文脈設立(_それらがgss_イニット_秒_文脈かgssに通過されるだろうというとき、_秒_文脈を受け入れる)か1メッセージあたりのセキュリティー・サービスに関連しています(_それらが_が確かめるgssかgssに通過されるだろうというとき、開いてください)。 時折、他の時に象徴を受け取るかもしれません、そして、gss_過程_文脈_象徴はそのような象徴が処理のための基本的なセキュリティー・サービスに渡されるのを許容します。 プレゼント、追加象徴が発生するだけであるかもしれないそのようなものでは、gss_は_秒_文脈を削除します。 GSSAPI実現は、セキュリティ文脈の削除を実行するのにこのサービスを利用するかもしれません。
Parameters:
パラメタ:
context_handle gss_ctx_id_t, read
context handle of context on which token is to
be processed
文脈_ハンドルgss_ctx_イド_tどの象徴が処理されることになっていたらよいかの文脈の文脈ハンドルが読まれて、
token_buffer buffer, opaque, read
pointer to first byte of token to process
不明瞭な象徴_バッファバッファは、処理するためにポインタを象徴の最初のバイトまで読みました。
minor_status integer, modify
Implementation specific status code.
小さい方の_状態整数、Implementationの特定のステータスコードを変更してください。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_DEFECTIVE_TOKEN Indicates that consistency checks
performed on the token failed
_GSS_S DEFECTIVE_TOKEN Indicatesはチェックが失敗されたトークンに実行したその一貫性です。
GSS_S_FAILURE Failure. See minor_status for more information
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
GSS_S_NO_CONTEXT The context_handle did not refer to a valid
context
GSS_S、_文脈_ハンドルがしたいいえ_CONTEXTは有効な文脈を示しません。
Wray [Page 25] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[25ページ]RFC1509GSSAPI--概要とC結合1993年9月
3.6. gss_delete_sec_context
3.6. gss_は_秒_文脈を削除します。
OM_uint32 gss_delete_sec_context (
OM_uint32 * minor_status,
gss_ctx_id_t * context_handle,
gss_buffer_t output_token)
OM_uint32 gss_は_秒_文脈を削除します。(OM_uint32*小さい方の_状態、gss_ctx_イド_t*文脈_ハンドル、gss_バッファ_t出力_トークン)
Purpose:
目的:
Delete a security context. gss_delete_sec_context will delete the local data structures associated with the specified security context, and generate an output_token, which when passed to the peer gss_process_context_token will instruct it to do likewise. No further security services may be obtained using the context specified by context_handle.
セキュリティ文脈を削除してください。gss_は_文脈が指定されたセキュリティ文脈に関連しているローカルのデータ構造を削除する_秒を削除して、出力_トークンを生成します。(同輩gss_プロセス_文脈_トークンに通過されると、それは、同様にそうするようそれに命令するでしょう)。 文脈_ハンドルによって指定された文脈を使用することでさらなるセキュリティー・サービスを全く得ないかもしれません。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
context_handle gss_ctx_id_t, modify
context handle identifying context to delete.
文脈_はgss_ctx_イド_tを扱って、削除する文脈を特定する文脈ハンドルを変更してください。
output_token buffer, opaque, modify
token to be sent to remote application to
instruct it to also delete the context
出力_トークンバッファ、不透明なものは、また、文脈を削除するようそれに命令するようにリモートアプリケーションに送られるトークンを変更します。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_FAILURE Failure, see minor_status for more information
_GSS_S FAILURE Failure、詳しい情報に関して小さい方の_状態を見てください。
GSS_S_NO_CONTEXT No valid context was supplied
どんな_のCONTEXTのいいえの有効な文脈も提供されなかったGSS_S_
3.7. gss_context_time
3.7.gss_文脈_時間
OM_uint32 gss_context_time (
OM_uint32 * minor_status,
gss_ctx_id_t context_handle,
OM_uint32 * time_rec)
Purpose:
OM_uint32 gss_文脈_時間(OM_uint32*小さい方の_状態、gss_ctx_イド_t文脈_ハンドル、OM_uint32*時間_rec)目的:
Determines the number of seconds for which the specified context will remain valid.
指定された文脈が有効なままで残っている秒数を測定します。
Wray [Page 26] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[26ページ]RFC1509GSSAPI--概要とC結合1993年9月
Parameters:
パラメタ:
minor_status integer, modify
Implementation specific status code.
小さい方の_状態整数、Implementationの特定のステータスコードを変更してください。
context_handle gss_ctx_id_t, read
Identifies the context to be interrogated.
文脈_は、gss_ctx_イド_tを扱って、査問されるために文脈をIdentifiesに読み込みました。
time_rec integer, modify
Number of seconds that the context will remain
valid. If the context has already expired,
zero will be returned.
Function value:
_rec整数を調節してください、そして、文脈が有効なままで残る秒のNumberを変更してください。 文脈が既に期限が切れたなら、ゼロは返されるでしょう。 機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_CONTEXT_EXPIRED The context has already expired
_GSS_S CONTEXT_EXPIRED、文脈は既に期限が切れました。
GSS_S_CREDENTIALS_EXPIRED The context is recognized, but
associated credentials have expired
_GSS_S CREDENTIALS_EXPIRED、文脈は認識されますが、関連資格証明書は期限が切れました。
GSS_S_NO_CONTEXT The context_handle parameter did not identify a
valid context
GSS_S、_文脈_ハンドルパラメタがしたいいえ_CONTEXTは有効な文脈を特定しません。
3.8. gss_sign
3.8. gss_サイン
OM_uint32 gss_sign (
OM_uint32 * minor_status,
gss_ctx_id_t context_handle,
int qop_req,
gss_buffer_t message_buffer,
gss_buffer_t msg_token)
Purpose:
OM_uint32 gss_サイン(OM_uint32*小さい方の_状態、gss_ctx_イド_t文脈_ハンドル、int qop_req、gss_バッファ_tメッセージ_バッファ、gss_バッファ_t msg_トークン)目的:
Generates a cryptographic signature for the supplied message, and places the signature in a token for transfer to the peer application. The qop_req parameter allows a choice between several cryptographic algorithms, if supported by the chosen mechanism.
供給されたメッセージのために暗号の署名を生成して、同輩アプリケーションへの転送のために署名をトークンに置きます。 選ばれたメカニズムによってサポートされるなら、qop_reqパラメタはいくつかの暗号アルゴリズムの選択を許します。
Parameters:
パラメタ:
minor_status integer, modify
Implementation specific status code.
小さい方の_状態整数、Implementationの特定のステータスコードを変更してください。
context_handle gss_ctx_id_t, read
identifies the context on which the message
読書が、文脈_ハンドルgss_が_イド_tをctxするのを文脈を特定する、どれ、メッセージ
Wray [Page 27] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[27ページ]RFC1509GSSAPI--概要とC結合1993年9月
will be sent
送るでしょう。
qop_req integer, read, optional
Specifies requested quality of protection.
Callers are encouraged, on portability grounds,
to accept the default quality of protection
offered by the chosen mechanism, which may be
requested by specifying GSS_C_QOP_DEFAULT for
this parameter. If an unsupported protection
strength is requested, gss_sign will return a
major_status of GSS_S_FAILURE.
qop_req整数、読書、任意のSpecifiesは保護の品質を要求しました。 移植性の根拠では、訪問者が_GSS_C QOP_DEFAULTをこのパラメタに指定することによって要求されているかもしれない選ばれたメカニズムによって提供された保護のデフォルト品質を受け入れるよう奨励されます。 サポートされない保護の強さが要求されると、gss_サインは_GSS_S FAILUREの主要な_状態を返すでしょう。
message_buffer buffer, opaque, read
message to be signed
不明瞭なメッセージ_バッファバッファは署名するべきメッセージを読みました。
msg_token buffer, opaque, modify
buffer to receive token
msg_トークンバッファ、不透明なものは、トークンを受けるようにバッファを変更します。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_CONTEXT_EXPIRED The context has already expired
_GSS_S CONTEXT_EXPIRED、文脈は既に期限が切れました。
GSS_S_CREDENTIALS_EXPIRED The context is recognized, but
associated credentials have expired
_GSS_S CREDENTIALS_EXPIRED、文脈は認識されますが、関連資格証明書は期限が切れました。
GSS_S_NO_CONTEXT The context_handle parameter did not identify a
valid context
GSS_S、_文脈_ハンドルパラメタがしたいいえ_CONTEXTは有効な文脈を特定しません。
GSS_S_FAILURE Failure. See minor_status for more information.
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
3.9. gss_verify
3.9. _が確かめるgss
OM_uint32 gss_verify (
OM_uint32 * minor_status,
gss_ctx_id_t context_handle,
gss_buffer_t message_buffer,
gss_buffer_t token_buffer,
int * qop_state)
Purpose:
OM_uint32 gss_は目的について確かめます(OM_uint32*小さい方の_状態、gss_ctx_イド_t文脈_ハンドル、gss_バッファ_tメッセージ_バッファ、gss_バッファ_tトークン_バッファ、int*qop_状態):
Verifies that a cryptographic signature, contained in the token parameter, fits the supplied message. The qop_state parameter allows a message recipient to determine the strength of protection that was applied to the message.
暗号のトークンパラメタに含まれた署名が供給されたメッセージに合うことを確かめます。 qop_州のパラメタで、メッセージ受取人はメッセージに適用された保護の強さを測定できます。
Wray [Page 28] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[28ページ]RFC1509GSSAPI--概要とC結合1993年9月
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
context_handle gss_ctx_id_t, read
identifies the context on which the message
arrived
gss_ctx_イド_tを扱って、読まれた文脈_はメッセージが到着した文脈を特定します。
message_buffer buffer, opaque, read
message to be verified
不明瞭なメッセージ_バッファバッファは確かめられるべきメッセージを読みました。
token_buffer buffer, opaque, read
token associated with message
不明瞭なトークン_バッファバッファはメッセージに関連しているトークンを読みました。
qop_state integer, modify
quality of protection gained from signature
qop_は整数を述べて、署名から獲得された保護の品質を変更してください。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_DEFECTIVE_TOKEN The token failed consistency checks
_GSS_S DEFECTIVE_TOKENはトークンの失敗した一貫性チェックです。
GSS_S_BAD_SIG The signature was incorrect
GSS_S_BAD_SIG、署名は不正確でした。
GSS_S_DUPLICATE_TOKEN The token was valid, and contained a correct
signature for the message, but it had already
been processed
_GSS_S DUPLICATE_TOKEN、トークンは、有効であり、メッセージのための正しい署名を含みましたが、既にそれを処理してありました。
GSS_S_OLD_TOKEN The token was valid, and contained a correct
signature for the message, but it is too old
_GSS_S OLD_TOKEN、トークンは、有効であり、メッセージのための正しい署名を含みましたが、それは古過ぎます。
GSS_S_UNSEQ_TOKEN The token was valid, and contained a correct
signature for the message, but has been
verified out of sequence; an earlier token has
been signed or sealed by the remote
application, but not yet been processed
locally.
_GSS_S UNSEQ_TOKEN、トークンは、有効であり、メッセージのための正しい署名を含んでいますが、順序が狂って確かめられました。 以前のトークンは、リモートアプリケーションで署名されるか、または封をされますが、まだ局所的に処理されていません。
GSS_S_CONTEXT_EXPIRED The context has already expired
_GSS_S CONTEXT_EXPIRED、文脈は既に期限が切れました。
GSS_S_CREDENTIALS_EXPIRED The context is recognized, but
associated credentials have expired
_GSS_S CREDENTIALS_EXPIRED、文脈は認識されますが、関連資格証明書は期限が切れました。
Wray [Page 29] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[29ページ]RFC1509GSSAPI--概要とC結合1993年9月
GSS_S_NO_CONTEXT The context_handle parameter did not identify a
valid context
GSS_S、_文脈_ハンドルパラメタがしたいいえ_CONTEXTは有効な文脈を特定しません。
GSS_S_FAILURE Failure. See minor_status for more information.
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
3.10. gss_seal
3.10. gss_シール
OM_uint32 gss_seal (
OM_uint32 * minor_status,
gss_ctx_id_t context_handle,
int conf_req_flag,
int qop_req
gss_buffer_t input_message_buffer,
int * conf_state,
gss_buffer_t output_message_buffer)
OM_uint32 gss_シール(OM_uint32*小さい方の_状態、gss_ctx_イド_t文脈_ハンドル、int conf_req_旗、int qop_req gss_バッファ_t入力_メッセージ_バッファ、int*conf_状態、gss_バッファ_t出力_メッセージ_バッファ)
Purpose:
目的:
Cryptographically signs and optionally encrypts the specified input_message. The output_message contains both the signature and the message. The qop_req parameter allows a choice between several cryptographic algorithms, if supported by the chosen mechanism.
暗号で署名して、任意に指定された入力_メッセージを暗号化します。 出力_メッセージは署名とメッセージの両方を含んでいます。 選ばれたメカニズムによってサポートされるなら、qop_reqパラメタはいくつかの暗号アルゴリズムの選択を許します。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
context_handle gss_ctx_id_t, read
identifies the context on which the message
will be sent
gss_ctx_イド_tを扱って、読まれた文脈_はメッセージが送られる文脈を特定します。
conf_req_flag boolean, read
True - Both confidentiality and integrity
services are requested
False - Only integrity service is requested
Trueは、conf_req_が論理演算子に旗を揚げさせると読みます--秘密性と保全サービスの両方が要求されたFalseです--保全サービスだけが要求されています。
qop_req integer, read, optional
Specifies required quality of protection. A
mechanism-specific default may be requested by
setting qop_req to GSS_C_QOP_DEFAULT. If an
unsupported protection strength is requested,
gss_seal will return a major_status of
GSS_S_FAILURE.
qop_req整数、読書、保護の任意のSpecifies必要な品質。 メカニズム特有のデフォルトは、_GSS_C QOP_DEFAULTにqop_reqを設定することによって、要求されているかもしれません。 サポートされない保護の強さが要求されると、gss_アザラシは_GSS_S FAILUREの主要な_状態を返すでしょう。
input_message_buffer buffer, opaque, read
message to be sealed
不明瞭な入力_メッセージ_バッファバッファは封ををされるべきメッセージを読みました。
Wray [Page 30] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[30ページ]RFC1509GSSAPI--概要とC結合1993年9月
conf_state boolean, modify
True - Confidentiality, data origin
authentication and integrity services
have been applied
False - Integrity and data origin services only
has been applied.
Trueを変更してください--秘密性、データ発生源認証、および保全サービスは適用されたFalseです--conf_は論理演算子を述べて、保全とデータ発生源サービスは適用されるだけでした。
output_message_buffer buffer, opaque, modify
buffer to receive sealed message
出力_メッセージ_バッファバッファ、不透明なものは、密封されたメッセージを受け取るようにバッファを変更します。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_CONTEXT_EXPIRED The context has already expired
_GSS_S CONTEXT_EXPIRED、文脈は既に期限が切れました。
GSS_S_CREDENTIALS_EXPIRED The context is recognized, but
associated credentials have expired
_GSS_S CREDENTIALS_EXPIRED、文脈は認識されますが、関連資格証明書は期限が切れました。
GSS_S_NO_CONTEXT The context_handle parameter did not identify a
valid context
GSS_S、_文脈_ハンドルパラメタがしたいいえ_CONTEXTは有効な文脈を特定しません。
GSS_S_FAILURE Failure. See minor_status for more information.
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
3.11. gss_unseal
3.11. gss_は開かれます。
OM_uint32 gss_unseal (
OM_uint32 * minor_status,
gss_ctx_id_t context_handle,
gss_buffer_t input_message_buffer,
gss_buffer_t output_message_buffer,
int * conf_state,
int * qop_state)
OM_uint32 gss_は開かれます。(OM_uint32*小さい方の_状態、gss_ctx_イド_t文脈_ハンドル、gss_バッファ_t入力_メッセージ_バッファ、gss_バッファ_t出力_メッセージ_バッファ、int*conf_状態、int*qop_状態)
Purpose:
目的:
Converts a previously sealed message back to a usable form, verifying the embedded signature. The conf_state parameter indicates whether the message was encrypted; the qop_state parameter indicates the strength of protection that was used to provide the confidentiality and integrity services.
埋め込まれた署名について確かめて、以前に密封されたメッセージを使用可能なフォームに変換して戻します。 conf_州のパラメタは、メッセージが暗号化されたかどうかを示します。 qop_州のパラメタは秘密性と保全にサービスを提供するのに使用された保護の強さを示します。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
Wray [Page 31] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[31ページ]RFC1509GSSAPI--概要とC結合1993年9月
context_handle gss_ctx_id_t, read
identifies the context on which the message
arrived
gss_ctx_イド_tを扱って、読まれた文脈_はメッセージが到着した文脈を特定します。
input_message_buffer buffer, opaque, read
sealed message
不明瞭な入力_メッセージ_バッファバッファは密封されたメッセージを読みました。
output_message_buffer buffer, opaque, modify
buffer to receive unsealed message
出力_メッセージ_バッファバッファ、不透明なものは、開かれたメッセージを受け取るようにバッファを変更します。
conf_state boolean, modify
True - Confidentiality and integrity protection
were used
False - Inteegrity service only was used
Trueを変更してください--秘密性と保全保護は中古のFalseでした--conf_は論理演算子を述べて、Inteegrityサービスだけが利用されました。
qop_state integer, modify
quality of protection gained from signature
qop_は整数を述べて、署名から獲得された保護の品質を変更してください。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_DEFECTIVE_TOKEN The token failed consistency checks
_GSS_S DEFECTIVE_TOKENはトークンの失敗した一貫性チェックです。
GSS_S_BAD_SIG The signature was incorrect
GSS_S_BAD_SIG、署名は不正確でした。
GSS_S_DUPLICATE_TOKEN The token was valid, and contained a
correct signature for the message, but it had
already been processed
_GSS_S DUPLICATE_TOKEN、トークンは、有効であり、メッセージのための正しい署名を含みましたが、既にそれを処理してありました。
GSS_S_OLD_TOKEN The token was valid, and contained a correct
signature for the message, but it is too old
_GSS_S OLD_TOKEN、トークンは、有効であり、メッセージのための正しい署名を含みましたが、それは古過ぎます。
GSS_S_UNSEQ_TOKEN The token was valid, and contained a correct
signature for the message, but has been
verified out of sequence; an earlier token has
been signed or sealed by the remote
application, but not yet been processed
locally.
_GSS_S UNSEQ_TOKEN、トークンは、有効であり、メッセージのための正しい署名を含んでいますが、順序が狂って確かめられました。 以前のトークンは、リモートアプリケーションで署名されるか、または封をされますが、まだ局所的に処理されていません。
GSS_S_CONTEXT_EXPIRED The context has already expired
_GSS_S CONTEXT_EXPIRED、文脈は既に期限が切れました。
GSS_S_CREDENTIALS_EXPIRED The context is recognized, but
associated credentials have expired
_GSS_S CREDENTIALS_EXPIRED、文脈は認識されますが、関連資格証明書は期限が切れました。
Wray [Page 32] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[32ページ]RFC1509GSSAPI--概要とC結合1993年9月
GSS_S_NO_CONTEXT The context_handle parameter did not identify a
valid context
GSS_S、_文脈_ハンドルパラメタがしたいいえ_CONTEXTは有効な文脈を特定しません。
GSS_S_FAILURE Failure. See minor_status for more information.
GSS_S_失敗の故障。 詳しい情報に関して小さい方の_状態を見てください。
3.12. gss_display_status
3.12. gss_ディスプレイ_状態
OM_uint32 gss_display_status (
OM_uint32 * minor_status,
int status_value,
int status_type,
gss_OID mech_type,
int * message_context,
gss_buffer_t status_string)
OM_uint32 gss_ディスプレイ_状態(OM_uint32*小さい方の_状態、int状態_値、int状態_タイプ、gss_OID mech_タイプ、int*メッセージ_文脈、gss_バッファ_t状態_ストリング)
Purpose:
目的:
Allows an application to obtain a textual representation of a GSSAPI status code, for display to the user or for logging purposes. Since some status values may indicate multiple errors, applications may need to call gss_display_status multiple times, each call generating a single text string. The message_context parameter is used to indicate which error message should be extracted from a given status_value; message_context should be initialized to 0, and gss_display_status will return a non-zero value if there are further messages to extract.
アプリケーションがGSSAPIステータスコードの原文の表現をユーザへのディスプレイか伐採目的として得るのを許容します。 いくつかの状態値が複数の誤りを示すかもしれないので、アプリケーションは、gss_を複数の回(ただ一つのテキスト文字列を生成する各呼び出し)ディスプレイ_状態と呼ぶ必要があるかもしれません。 メッセージ_文脈パラメタはどのエラーメッセージが与えられた状態_値から抜粋されるべきであるかを示すのに使用されます。 メッセージ_文脈は0に初期化されるべきです、そして、抜粋するメッセージがさらにあると、gss_ディスプレイ_状態は非ゼロ値を返すでしょう。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
status_value integer, read
Status value to be converted
Status値が変換されるために読まれた状態_値の整数
status_type integer, read
GSS_C_GSS_CODE - status_value is a GSS status
code
GSS_C_MECH_CODE - status_value is a mechanism
status code
状態_タイプ整数_GSS_CODE--_が_GSSステータスコードGSS_C MECH_CODEであることを評価する状態--状態_が、評価するメカニズムステータスコードであるGSS_Cが読まれて、
mech_type Object ID, read, optional
Underlying mechanism (used to interpret a
minor status value) Supply GSS_C_NULL_OID to
obtain the system default.
_mech_タイプObject ID、読んでください、システム・デフォルトを得る任意のUnderlyingメカニズム(以前はよく小さい方の状態値を解釈していた)供給GSS_C NULL_OID。
message_context integer, read/modify
Should be initialized to zero by caller
Shouldを_文脈整数を通信させてくださいといって、読むか、または変更してください、訪問者によってゼロに初期化されてください。
Wray [Page 33] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[33ページ]RFC1509GSSAPI--概要とC結合1993年9月
on first call. If further messages are
contained in the status_value parameter,
message_context will be non-zero on return,
and this value should be passed back to
subsequent calls, along with the same
status_value, status_type and mech_type
parameters.
まず最初に、電話をしてください。 さらなるメッセージが状態_値のパラメタに含まれていると、メッセージ_文脈はリターンで非ゼロになるでしょう、そして、この値はその後の呼び出しに戻されるべきです、同じ状態_価値、状態_タイプ、およびmech_型引数と共に。
status_string buffer, character string, modify
textual interpretation of the status_value
状態_ストリングバッファ、文字列は状態_価値の原文の解釈を変更します。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_BAD_MECH Indicates that translation in accordance with
an unsupported mechanism type was requested
GSS_S_BAD_MECH Indicatesは要求されましたサポートされないメカニズムに従ったその翻訳が、タイプする。
GSS_S_BAD_STATUS The status value was not recognized, or the
status type was neither GSS_C_GSS_CODE nor
GSS_C_MECH_CODE.
_GSS_S BAD_STATUS、状態タイプは、状態値が認識されなかったか、_GSS_C GSS_CODEでなくてまたGSS_C_MECH_CODEではありませんでした。
3.13. gss_indicate_mechs
3.13. gss_は_mechsを示します。
OM_uint32 gss_indicate_mechs (
OM_uint32 * minor_status,
gss_OID_set * mech_set)
OM_uint32 gss_は_mechsを示します。(OM_uint32*小さい方の_状態、_が設定したgss_OID_セット*mech)
Purpose:
目的:
Allows an application to determine which underlying security
mechanisms are available.
アプリケーションが、どの基本的なセキュリティー対策が利用可能であるかを決定するのを許容します。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
mech_set set of Object IDs, modify
set of implementation-supported mechanisms.
The returned gss_OID_set value will be a
pointer into static storage, and should be
treated as read-only by the caller.
実装でサポートしているメカニズムのセットを変更してください。Object IDのmech_セットセット、返されたgss_OID_設定値は、スタティックストレージへの指針であり、訪問者によって書き込み禁止として扱われるべきです。
Wray [Page 34] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[34ページ]RFC1509GSSAPI--概要とC結合1993年9月
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
3.14. gss_compare_name
3.14. gss_は_名前を比較します。
OM_uint32 gss_compare_name (
OM_uint32 * minor_status,
gss_name_t name1,
gss_name_t name2,
int * name_equal)
OM_uint32 gss_は_名前を比較します。(OM_uint32*小さい方の_状態、_gss_名前t name1、_gss_名前t name2、int*名前_同輩)
Purpose:
目的:
Allows an application to compare two internal-form names to determine whether they refer to the same entity.
アプリケーションが彼らが同じ実体について言及するかどうか決定するために2つの内部のフォーム名を比較するのを許容します。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
name1 gss_name_t, read
internal-form name
name1 gss_名前_t、内部のフォーム名を読んでください。
name2 gss_name_t, read
internal-form name
name2 gss_名前_t、内部のフォーム名を読んでください。
name_equal boolean, modify
True - names refer to same entity
False - names refer to different entities
(strictly, the names are not known to
refer to the same identity).
Function value:
Trueを変更してください--名前は同じ実体Falseについて言及します--等しい論理演算子と_を命名してください、そして、名前は異なった実体を呼びます(厳密に、名前が同じアイデンティティについて言及するのが知られません)。 機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_BAD_NAMETYPE The type contained within either name1 or
name2 was unrecognized, or the names were of
incomparable types.
タイプのBAD_NAMETYPEがname1かname2のどちらかの中に含んだGSS_S_が認識されていなかったか、または比較にならないほどタイプには名前がありました。
GSS_S_BAD_NAME One or both of name1 or name2 was ill-formed
GSS_S_BAD_NAME Oneかname1かname2の両方が不適格でした。
Wray [Page 35] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[35ページ]RFC1509GSSAPI--概要とC結合1993年9月
3.15. gss_display_name
3.15. gss_ディスプレイ_名
OM_uint32 gss_display_name (
OM_uint32 * minor_status,
gss_name_t input_name,
gss_buffer_t output_name_buffer,
gss_OID * output_name_type)
OM_uint32 gss_ディスプレイ_名(OM_uint32*小さい方の_状態、gss_名前_t入力_名、gss_バッファ_t出力_名前_バッファ、gss_OID*出力_名前_タイプ)
Purpose:
目的:
Allows an application to obtain a textual representation of an opaque internal-form name for display purposes. The syntax of a printable name is defined by the GSSAPI implementation.
アプリケーションが不明瞭な内部のフォーム名の原文の表現をディスプレイ目的として得るのを許容します。 印刷可能な名前の構文はGSSAPI実装によって定義されます。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code.
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
input_name gss_name_t, read
name to be displayed
名前が表示するために読まれた入力_名前gss_名前_t
output_name_buffer buffer, character-string, modify
buffer to receive textual name string
出力_名前_バッファバッファ、文字列は、原文の名前ストリングを受け取るようにバッファを変更します。
output_name_type Object ID, modify
The type of the returned name. The returned
gss_OID will be a pointer into static storage,
and should be treated as read-only by the caller
_名前_タイプObject IDを出力してください、そして、返された名前のタイプを変更してください。 返されたgss_OIDはスタティックストレージへの指針であり、訪問者によって書き込み禁止として扱われるべきです。
Function value:
機能値:
GSS status code:
GSSステータスコード:
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_BAD_NAMETYPE The type of input_name was not recognized
入力_名前のタイプのGSS_S_BAD_NAMETYPEは認識されませんでした。
GSS_S_BAD_NAME input_name was ill-formed
GSS_S_BAD_NAME入力_名は不適格でした。
3.16. gss_import_name
3.16. gss_輸入_名
OM_uint32 gss_import_name (
OM_uint32 * minor_status,
gss_buffer_t input_name_buffer,
gss_OID input_name_type,
gss_name_t * output_name)
OM_uint32 gss_輸入_名(OM_uint32*小さい方の_状態、gss_バッファ_t入力_名前_バッファ、gss_OID入力_名前_タイプ、gss_名前_t*出力_名)
Wray [Page 36] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[36ページ]RFC1509GSSAPI--概要とC結合1993年9月
Purpose:
目的:
Convert a printable name to internal form.
印刷可能な名前を内部のフォームに変換してください。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
input_name_buffer buffer, character-string, read
buffer containing printable name to convert
入力_名前_バッファバッファ(文字列)は、変換するために印刷可能な名前を含むバッファを読みました。
input_name_type Object ID, read, optional
Object Id specifying type of printable
name. Applications may specify either
GSS_C_NULL_OID to use a local system-specific
printable syntax, or an OID registered by the
GSSAPI implementation to name a particular
namespace.
任意のObject Idが印刷可能な名前のタイプを指定して、_名前_タイプObject IDを入力してください、そして、読んでください。 アプリケーションがローカルのシステム特有の印刷可能な構文を使用するために_GSS_C NULL_OIDを指定するかもしれませんか、またはOIDは、特定の名前空間を命名するためにGSSAPI実装で登録しました。
output_name gss_name_t, modify
returned name in internal form
_名前gss_名前_tを出力してください、そして、内部のフォームで返された名前を変更してください。
Function value:
機能値:
GSS status code
GSSステータスコード
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_BAD_NAMETYPE The input_name_type was unrecognized
入力_名前_タイプのGSS_S_BAD_NAMETYPEは認識されていませんでした。
GSS_S_BAD_NAME The input_name parameter could not be
interpreted as a name of the specified type
_GSS_S BAD_NAME、入力_名前パラメタは指定されたタイプの名前として解釈されないかもしれません。
3.17. gss_release_name
3.17. gss_リリース_名
OM_uint32 gss_release_name (
OM_uint32 * minor_status,
gss_name_t * name)
OM_uint32 gss_リリース_名(OM_uint32*小さい方の_状態、gss_名前_t*名)
Purpose:
目的:
Free GSSAPI-allocated storage associated with an internal form name.
無料のGSSAPIによって割り当てられたストレージは内部のフォーム名と交際しました。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
Wray [Page 37] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[37ページ]RFC1509GSSAPI--概要とC結合1993年9月
name gss_name_t, modify
The name to be deleted
_名前_tとgssを命名してください、そして、名前を変更して、削除されてください。
Function value:
機能値:
GSS status code
GSSステータスコード
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_BAD_NAME The name parameter did not contain a valid name
GSS_S、_名前パラメタがしたBAD_NAMEは妥当な名前を含んでいません。
3.18. gss_release_buffer
3.18. gss_リリース_バッファ
OM_uint32 gss_release_buffer (
OM_uint32 * minor_status,
gss_buffer_t buffer)
OM_uint32 gss_リリース_バッファ(OM_uint32*小さい方の_状態、gss_バッファ_tバッファ)
Purpose:
目的:
Free storage associated with a buffer format name. The storage must have been allocated by a GSSAPI routine. In addition to freeing the associated storage, the routine will zero the length field in the buffer parameter.
フリーストレージはバッファ形式名と交際しました。 GSSAPIルーチンでストレージを割り当てたに違いありません。 関連ストレージを解放することに加えて、ルーチンはバッファパラメタの長さの分野のゼロに合うでしょう。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
buffer buffer, modify
The storage associated with the buffer will be
deleted. The gss_buffer_desc object will not
be freed, but its length field will be zeroed.
バッファをバッファリングしてください、そして、削除されるよりもみ皮製の意志に関連しているストレージを変更してください。 gss_バッファ_descオブジェクトは解放されないでしょうが、長さの分野のゼロは合わせられるでしょう。
Function value:
機能値:
GSS status code
GSSステータスコード
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
3.19. gss_release_oid_set
3.19. oid_が設定したgss_リリース_
OM_uint32 gss_release_oid_set (
OM_uint32 * minor_status,
gss_OID_set * set)
OM_uint32 gss_リリース_oid_セット(OM_uint32*小さい方の_状態、OID_セット*が設定したgss_)
Purpose:
目的:
Wray [Page 38] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[38ページ]RFC1509GSSAPI--概要とC結合1993年9月
Free storage associated with a gss_OID_set object. The storage must have been allocated by a GSSAPI routine.
フリーストレージはgss_OID_セットオブジェクトと交際しました。 GSSAPIルーチンでストレージを割り当てたに違いありません。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
set Set of Object IDs, modify
The storage associated with the gss_OID_set
will be deleted.
Object IDのSetを設定してください、そして、削除されるgss_OID_設定している意志に関連しているストレージを変更してください。
Function value:
機能値:
GSS status code
GSSステータスコード
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
3.20. gss_inquire_cred
3.20. gss_は_信用について問い合わせます。
OM_uint32 gss_inquire_cred (
OM_uint32 * minor_status,
gss_cred_id_t cred_handle,
gss_name_t * name,
OM_uint32 * lifetime,
int * cred_usage,
gss_OID_set * mechanisms )
OM_uint32 gss_は_信用について問い合わせます。(OM_uint32*小さい方の_状態、gss_信用_イド_t信用_ハンドル、gss_名前_t*名、OM_uint32*生涯、int*信用_用法、gss_OID_セット*メカニズム)
Purpose:
目的:
Obtains information about a credential. The caller must already have obtained a handle that refers to the credential.
資格証明書の情報を得ます。 訪問者は既に資格証明書について言及するハンドルを入手したに違いありません。
Parameters:
パラメタ:
minor_status integer, modify
Mechanism specific status code
小さい方の_状態整数、Mechanismの特定のステータスコードを変更してください。
cred_handle gss_cred_id_t, read
A handle that refers to the target credential.
Specify GSS_C_NO_CREDENTIAL to inquire about
the default credential.
信用_ハンドルgss_信用_イド_t目標資格証明書について言及するAハンドルが読まれて。 _GSS_Cいいえ_CREDENTIALを指定して、デフォルト資格証明書について問い合わせをしてください。
name gss_name_t, modify
The name whose identity the credential asserts.
Specify NULL if not required.
_名前_tとgssを命名してください、そして、資格証明書がアイデンティティについて断言する名前を変更してください。 必要でないなら、NULLを指定してください。
lifetime Integer, modify
生涯Integer、変更
Wray [Page 39] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[39ページ]RFC1509GSSAPI--概要とC結合1993年9月
The number of seconds for which the credential
will remain valid. If the credential has
expired, this parameter will be set to zero.
If the implementation does not support
credential expiration, the value
GSS_C_INDEFINITE will be returned. Specify
NULL if not required.
資格証明書が有効なままで残っている秒数。 資格証明書が期限が切れたなら、このパラメタはゼロに設定されるでしょう。 実装が資格証明満了をサポートしないと、値GSS_Cの_INDEFINITEを返すでしょう。 必要でないなら、NULLを指定してください。
cred_usage Integer, modify
How the credential may be used. One of the
following:
GSS_C_INITIATE
GSS_C_ACCEPT
GSS_C_BOTH
Specify NULL if not required.
信用_用法Integer、Howを変更してください。資格証明書は使用されてもよいです。 以下の1つ: _GSS_C INITIATE GSS_C_ACCEPT GSS_C_BOTH Specify NULLか必要です。
mechanisms gss_OID_set, modify
Set of mechanisms supported by the credential.
Specify NULL if not required.
メカニズムgss_OID_が用意ができていて、資格証明書によってサポートされたメカニズムのSetを変更してください。 必要でないなら、NULLを指定してください。
Function value:
機能値:
GSS status code
GSSステータスコード
GSS_S_COMPLETE Successful completion
GSS_S_COMPLETE Successful完成
GSS_S_NO_CRED The referenced credentials could not be
accessed.
__いいえ、CRED。GSS_S、参照をつけられた資格証明書にアクセスできませんでした。
GSS_S_DEFECTIVE_CREDENTIAL The referenced credentials were
invalid.
_GSS_S DEFECTIVE_CREDENTIAL、参照をつけられた資格証明書は無効でした。
GSS_S_CREDENTIALS_EXPIRED The referenced credentials have expired.
If the lifetime parameter was not passed as
NULL, it will be set to 0.
_GSS_S CREDENTIALS_EXPIRED、参照をつけられた資格証明書は期限が切れました。 生涯パラメタがNULLとして通過されなかったなら、それは0に設定されるでしょう。
#ifndef GSSAPI_H_ #define GSSAPI_H_
#ifndef GSSAPI_H_ #はGSSAPI_H_を定義します。
/* * First, define the platform-dependent types. */ typedef <platform-specific> OM_uint32; typedef <platform-specific> gss_ctx_id_t; typedef <platform-specific> gss_cred_id_t; typedef <platform-specific> gss_name_t;
/、**最初に、プラットホーム依存するタイプを定義してください。 */typedef<プラットホーム特有の>OM_uint32。 typedefの<のプラットホーム特有の>gss_ctx_イド_t。 typedef<プラットホーム特有の>gss_信用_イド_t。 typedefの<のプラットホーム特有の>gss_名前_t。
Wray [Page 40] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[40ページ]RFC1509GSSAPI--概要とC結合1993年9月
/* * Note that a platform supporting the xom.h X/Open header file * may make use of that header for the definitions of OM_uint32 * and the structure to which gss_OID_desc equates. */
xom.h X/Openがヘッダーファイル*であるとサポートするプラットホームがOM_uint32*と構造の定義にどのgss_OID_descにそのヘッダーを利用するかもしれないかという/**メモは一致しています。 */
typedef struct gss_OID_desc_struct {
OM_uint32 length;
void *elements;
} gss_OID_desc, *gss_OID;
typedef struct gss_OID_desc_struct OM_uint32の長さ; 空間*要素;のgss_OID_desc、*gss_OID。
typedef struct gss_OID_set_desc_struct {
int count;
gss_OID elements;
} gss_OID_set_desc, *gss_OID_set;
*typedef struct gss_OID_は_desc_struct intカウント; gss_OID要素;gss_OID_セット_descを設定して、gss_OID_はセットしました。
typedef struct gss_buffer_desc_struct {
size_t length;
void *value;
} gss_buffer_desc, *gss_buffer_t;
_typedef struct gss_バッファ_desc_structサイズ_tの長さ; 空間*値;のgss_バッファdesc、*gss_バッファ_t。
typedef struct gss_channel_bindings_struct {
OM_uint32 initiator_addrtype;
gss_buffer_desc initiator_address;
OM_uint32 acceptor_addrtype;
gss_buffer_desc acceptor_address;
gss_buffer_desc application_data;
} *gss_channel_bindings_t;
typedef struct gss_チャンネル_結合_struct OM_uint32創始者_addrtype; gss_バッファ_desc創始者_アドレス; OM_uint32アクセプタ_addrtype; gss_バッファ_descアクセプタ_アドレス; gss_バッファ_descアプリケーション_データ;*gss_チャンネル_結合_t。
/* * Six independent flags each of which indicates that a context * supports a specific service option. */ #define GSS_C_DELEG_FLAG 1 #define GSS_C_MUTUAL_FLAG 2 #define GSS_C_REPLAY_FLAG 4 #define GSS_C_SEQUENCE_FLAG 8 #define GSS_C_CONF_FLAG 16 #define GSS_C_INTEG_FLAG 32
6独立者がそれぞれ旗を揚げさせるそれの/**は、文脈*が、特定のサービスがオプションであるとサポートするのを示します。 */#がDELEG_旗の1#、が定義するGSS_C_を定義する、GSS_Cの_の互いの_旗の2#、が_再生_旗の4#、が定義するGSS_Cを定義する、GSS_C_系列_旗の8#、がCONF_旗の16#、が定義するGSS_C_を定義する、GSS_C_INTEG_旗32
/* * Credential usage options */ #define GSS_C_BOTH 0 #define GSS_C_INITIATE 1 #define GSS_C_ACCEPT 2
/**資格証明用法オプション*/#、がBOTH0#、が定義するGSS_C_を定義する、GSS_C_INITIATE1#、はGSS_C_ACCEPT2を定義します。
Wray [Page 41] RFC 1509 GSSAPI - Overview and C bindings September 1993
レイ[41ページ]RFC1509GSSAPI--概要とC結合1993年9月
/* * Status code types for gss_display_status */ #define GSS_C_GSS_CODE 1 #define GSS_C_MECH_CODE 2
gss_ディスプレイ_状態*/#、がGSS_C_GSS_CODE1#、を定義するので、/**ステータスコードタイプはGSS_C_MECH_CODE2を定義します。
/* * The constant definitions for channel-bindings address families */ #define GSS_C_AF_UNSPEC 0; #define GSS_C_AF_LOCAL 1; #define GSS_C_AF_INET 2; #define GSS_C_AF_IMPLINK 3; #define GSS_C_AF_PUP 4; #define GSS_C_AF_CHAOS 5; #define GSS_C_AF_NS 6; #define GSS_C_AF_NBS 7; #define GSS_C_AF_ECMA 8; #define GSS_C_AF_DATAKIT 9; #define GSS_C_AF_CCITT 10; #define GSS_C_AF_SNA 11; #define GSS_C_AF_DECnet 12; #define GSS_C_AF_DLI 13; #define GSS_C_AF_LAT 14; #define GSS_C_AF_HYLINK 15; #define GSS_C_AF_APPLETALK 16; #define GSS_C_AF_BSC 17; #define GSS_C_AF_DSS 18; #define GSS_C_AF_OSI 19; #define GSS_C_AF_X25 21;
チャンネル結合のための一定の定義がファミリー*/#、を扱う/**はGSS_C_AF_UNSPEC0を定義します。 #GSS_C_AF_LOCAL1を定義してください。 #GSS_C_AF_INET2を定義してください。 #GSS_C_AF_IMPLINK3を定義してください。 #GSS_C_AF_PUP4を定義してください。 #GSS_C_AF_CHAOS5を定義してください。 #GSS_C_AF_NS6を定義してください。 #GSS_C_AF_NBS7を定義してください。 #GSS_C_AF_ECMA8を定義してください。 #GSS_C_AF_DATAKIT9を定義してください。 #GSS_C_AF_CCITT10を定義してください。 #GSS_C_AF_SNA11を定義してください。 #GSS_C_AF_DECnet12を定義してください。 #GSS_C_AF_DLI13を定義してください。 #GSS_C_AF_LAT14を定義してください。 #GSS_C_AF_HYLINK15を定義してください。 #GSS_C_AF_APPLETALK16を定義してください。 #GSS_C_AF_BSC17を定義してください。 #GSS_C_AF_DSS18を定義してください。 #GSS_C_AF_OSI19を定義してください。 #_GSS_C AF_X25 21を定義してください。
#define GSS_C_AF_NULLADDR 255;
#GSS_C_AF_NULLADDR255を定義してください。
#define GSS_C_NO_BUFFER ((gss_buffer_t) 0)
#define GSS_C_NULL_OID ((gss_OID) 0)
#define GSS_C_NULL_OID_SET ((gss_OID_set) 0)
#define GSS_C_NO_CONTEXT ((gss_ctx_id_t) 0)
#define GSS_C_NO_CREDENTIAL ((gss_cred_id_t) 0)
#define GSS_C_NO_CHANNEL_BINDINGS ((gss_channel_bindings_t) 0)
#define GSS_C_EMPTY_BUFFER {0, NULL}
#define GSS_C_NO_BUFFER ((gss_buffer_t) 0) #define GSS_C_NULL_OID ((gss_OID) 0) #define GSS_C_NULL_OID_SET ((gss_OID_set) 0) #define GSS_C_NO_CONTEXT ((gss_ctx_id_t) 0) #define GSS_C_NO_CREDENTIAL ((gss_cred_id_t) 0) #define GSS_C_NO_CHANNEL_BINDINGS ((gss_channel_bindings_t) 0) #define GSS_C_EMPTY_BUFFER {0, NULL}
/* * Define the default Quality of Protection for per-message * services. Note that an implementation that offers multiple * levels of QOP may either reserve a value (for example zero, * as assumed here) to mean "default protection", or alternatively * may simply equate GSS_C_QOP_DEFAULT to a specific explicit QOP * value.
/* * Define the default Quality of Protection for per-message * services. Note that an implementation that offers multiple * levels of QOP may either reserve a value (for example zero, * as assumed here) to mean "default protection", or alternatively * may simply equate GSS_C_QOP_DEFAULT to a specific explicit QOP * value.
Wray [Page 42] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 42] RFC 1509 GSSAPI - Overview and C bindings September 1993
*/ #define GSS_C_QOP_DEFAULT 0
*/ #define GSS_C_QOP_DEFAULT 0
/* * Expiration time of 2^32-1 seconds means infinite lifetime for a * credential or security context */ #define GSS_C_INDEFINITE 0xfffffffful
/* * Expiration time of 2^32-1 seconds means infinite lifetime for a * credential or security context */ #define GSS_C_INDEFINITE 0xfffffffful
/* Major status codes */
/* Major status codes */
#define GSS_S_COMPLETE 0
#define GSS_S_COMPLETE 0
/* * Some "helper" definitions to make the status code macros obvious. */ #define GSS_C_CALLING_ERROR_OFFSET 24 #define GSS_C_ROUTINE_ERROR_OFFSET 16 #define GSS_C_SUPPLEMENTARY_OFFSET 0 #define GSS_C_CALLING_ERROR_MASK 0377ul #define GSS_C_ROUTINE_ERROR_MASK 0377ul #define GSS_C_SUPPLEMENTARY_MASK 0177777ul
/* * Some "helper" definitions to make the status code macros obvious. */ #define GSS_C_CALLING_ERROR_OFFSET 24 #define GSS_C_ROUTINE_ERROR_OFFSET 16 #define GSS_C_SUPPLEMENTARY_OFFSET 0 #define GSS_C_CALLING_ERROR_MASK 0377ul #define GSS_C_ROUTINE_ERROR_MASK 0377ul #define GSS_C_SUPPLEMENTARY_MASK 0177777ul
/*
* The macros that test status codes for error conditions
*/
#define GSS_CALLING_ERROR(x) \
(x & (GSS_C_CALLING_ERROR_MASK << GSS_C_CALLING_ERROR_OFFSET))
#define GSS_ROUTINE_ERROR(x) \
(x & (GSS_C_ROUTINE_ERROR_MASK << GSS_C_ROUTINE_ERROR_OFFSET))
#define GSS_SUPPLEMENTARY_INFO(x) \
(x & (GSS_C_SUPPLEMENTARY_MASK << GSS_C_SUPPLEMENTARY_OFFSET))
#define GSS_ERROR(x) \
((GSS_CALLING_ERROR(x) != 0) || (GSS_ROUTINE_ERROR(x) != 0))
/* * The macros that test status codes for error conditions */ #define GSS_CALLING_ERROR(x) \ (x & (GSS_C_CALLING_ERROR_MASK << GSS_C_CALLING_ERROR_OFFSET)) #define GSS_ROUTINE_ERROR(x) \ (x & (GSS_C_ROUTINE_ERROR_MASK << GSS_C_ROUTINE_ERROR_OFFSET)) #define GSS_SUPPLEMENTARY_INFO(x) \ (x & (GSS_C_SUPPLEMENTARY_MASK << GSS_C_SUPPLEMENTARY_OFFSET)) #define GSS_ERROR(x) \ ((GSS_CALLING_ERROR(x) != 0) || (GSS_ROUTINE_ERROR(x) != 0))
/* * Now the actual status code definitions */
/* * Now the actual status code definitions */
/*
* Calling errors:
*/
#define GSS_S_CALL_INACCESSIBLE_READ \
(1ul << GSS_C_CALLING_ERROR_OFFSET)
#define GSS_S_CALL_INACCESSIBLE_WRITE \
(2ul << GSS_C_CALLING_ERROR_OFFSET)
/* * Calling errors: */ #define GSS_S_CALL_INACCESSIBLE_READ \ (1ul << GSS_C_CALLING_ERROR_OFFSET) #define GSS_S_CALL_INACCESSIBLE_WRITE \ (2ul << GSS_C_CALLING_ERROR_OFFSET)
Wray [Page 43] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 43] RFC 1509 GSSAPI - Overview and C bindings September 1993
#define GSS_S_CALL_BAD_STRUCTURE \
(3ul << GSS_C_CALLING_ERROR_OFFSET)
#define GSS_S_CALL_BAD_STRUCTURE \ (3ul << GSS_C_CALLING_ERROR_OFFSET)
/* * Routine errors: */ #define GSS_S_BAD_MECH (1ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_NAME (2ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_NAMETYPE (3ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_BINDINGS (4ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_STATUS (5ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_SIG (6ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_NO_CRED (7ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_NO_CONTEXT (8ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_DEFECTIVE_TOKEN (9ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_DEFECTIVE_CREDENTIAL (10ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_CREDENTIALS_EXPIRED (11ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_CONTEXT_EXPIRED (12ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_FAILURE (13ul << GSS_C_ROUTINE_ERROR_OFFSET)
/* * Routine errors: */ #define GSS_S_BAD_MECH (1ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_NAME (2ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_NAMETYPE (3ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_BINDINGS (4ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_STATUS (5ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_BAD_SIG (6ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_NO_CRED (7ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_NO_CONTEXT (8ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_DEFECTIVE_TOKEN (9ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_DEFECTIVE_CREDENTIAL (10ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_CREDENTIALS_EXPIRED (11ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_CONTEXT_EXPIRED (12ul << GSS_C_ROUTINE_ERROR_OFFSET) #define GSS_S_FAILURE (13ul << GSS_C_ROUTINE_ERROR_OFFSET)
/* * Supplementary info bits: */ #define GSS_S_CONTINUE_NEEDED (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 0)) #define GSS_S_DUPLICATE_TOKEN (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 1)) #define GSS_S_OLD_TOKEN (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 2)) #define GSS_S_UNSEQ_TOKEN (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 3))
/* * Supplementary info bits: */ #define GSS_S_CONTINUE_NEEDED (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 0)) #define GSS_S_DUPLICATE_TOKEN (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 1)) #define GSS_S_OLD_TOKEN (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 2)) #define GSS_S_UNSEQ_TOKEN (1ul << (GSS_C_SUPPLEMENTARY_OFFSET + 3))
/* * Finally, function prototypes for the GSSAPI routines. */
/* * Finally, function prototypes for the GSSAPI routines. */
OM_uint32 gss_acquire_cred
(OM_uint32*, /* minor_status */
gss_name_t, /* desired_name */
OM_uint32, /* time_req */
gss_OID_set, /* desired_mechs */
int, /* cred_usage */
gss_cred_id_t*, /* output_cred_handle */
gss_OID_set*, /* actual_mechs */
OM_uint32* /* time_rec */
);
OM_uint32 gss_acquire_cred (OM_uint32*, /* minor_status */ gss_name_t, /* desired_name */ OM_uint32, /* time_req */ gss_OID_set, /* desired_mechs */ int, /* cred_usage */ gss_cred_id_t*, /* output_cred_handle */ gss_OID_set*, /* actual_mechs */ OM_uint32* /* time_rec */ );
OM_uint32 gss_release_cred,
(OM_uint32*, /* minor_status */
gss_cred_id_t* /* cred_handle */
);
OM_uint32 gss_release_cred, (OM_uint32*, /* minor_status */ gss_cred_id_t* /* cred_handle */ );
Wray [Page 44] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 44] RFC 1509 GSSAPI - Overview and C bindings September 1993
OM_uint32 gss_init_sec_context
(OM_uint32*, /* minor_status */
gss_cred_id_t, /* claimant_cred_handle */
gss_ctx_id_t*, /* context_handle */
gss_name_t, /* target_name */
gss_OID, /* mech_type */
int, /* req_flags */
OM_uint32, /* time_req */
gss_channel_bindings_t,
/* input_chan_bindings */
gss_buffer_t, /* input_token */
gss_OID*, /* actual_mech_type */
gss_buffer_t, /* output_token */
int*, /* ret_flags */
OM_uint32* /* time_rec */
);
OM_uint32 gss_init_sec_context (OM_uint32*, /* minor_status */ gss_cred_id_t, /* claimant_cred_handle */ gss_ctx_id_t*, /* context_handle */ gss_name_t, /* target_name */ gss_OID, /* mech_type */ int, /* req_flags */ OM_uint32, /* time_req */ gss_channel_bindings_t, /* input_chan_bindings */ gss_buffer_t, /* input_token */ gss_OID*, /* actual_mech_type */ gss_buffer_t, /* output_token */ int*, /* ret_flags */ OM_uint32* /* time_rec */ );
OM_uint32 gss_accept_sec_context
(OM_uint32*, /* minor_status */
gss_ctx_id_t*, /* context_handle */
gss_cred_id_t, /* verifier_cred_handle */
gss_buffer_t, /* input_token_buffer */
gss_channel_bindings_t,
/* input_chan_bindings */
gss_name_t*, /* src_name */
gss_OID*, /* mech_type */
gss_buffer_t, /* output_token */
int*, /* ret_flags */
OM_uint32*, /* time_rec */
gss_cred_id_t* /* delegated_cred_handle */
);
OM_uint32 gss_accept_sec_context (OM_uint32*, /* minor_status */ gss_ctx_id_t*, /* context_handle */ gss_cred_id_t, /* verifier_cred_handle */ gss_buffer_t, /* input_token_buffer */ gss_channel_bindings_t, /* input_chan_bindings */ gss_name_t*, /* src_name */ gss_OID*, /* mech_type */ gss_buffer_t, /* output_token */ int*, /* ret_flags */ OM_uint32*, /* time_rec */ gss_cred_id_t* /* delegated_cred_handle */ );
OM_uint32 gss_process_context_token
(OM_uint32*, /* minor_status */
gss_ctx_id_t, /* context_handle */
gss_buffer_t /* token_buffer */
);
OM_uint32 gss_process_context_token (OM_uint32*, /* minor_status */ gss_ctx_id_t, /* context_handle */ gss_buffer_t /* token_buffer */ );
OM_uint32 gss_delete_sec_context
(OM_uint32*, /* minor_status */
gss_ctx_id_t*, /* context_handle */
gss_buffer_t /* output_token */
);
OM_uint32 gss_delete_sec_context (OM_uint32*, /* minor_status */ gss_ctx_id_t*, /* context_handle */ gss_buffer_t /* output_token */ );
Wray [Page 45] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 45] RFC 1509 GSSAPI - Overview and C bindings September 1993
OM_uint32 gss_context_time
(OM_uint32*, /* minor_status */
gss_ctx_id_t, /* context_handle */
OM_uint32* /* time_rec */
);
OM_uint32 gss_context_time (OM_uint32*, /* minor_status */ gss_ctx_id_t, /* context_handle */ OM_uint32* /* time_rec */ );
OM_uint32 gss_sign
(OM_uint32*, /* minor_status */
gss_ctx_id_t, /* context_handle */
int, /* qop_req */
gss_buffer_t, /* message_buffer */
gss_buffer_t /* message_token */
);
OM_uint32 gss_sign (OM_uint32*, /* minor_status */ gss_ctx_id_t, /* context_handle */ int, /* qop_req */ gss_buffer_t, /* message_buffer */ gss_buffer_t /* message_token */ );
OM_uitn32 gss_verify
(OM_uint32*, /* minor_status */
gss_ctx_id_t, /* context_handle */
gss_buffer_t, /* message_buffer */
gss_buffer_t, /* token_buffer */
int* /* qop_state */
);
OM_uitn32 gss_verify (OM_uint32*, /* minor_status */ gss_ctx_id_t, /* context_handle */ gss_buffer_t, /* message_buffer */ gss_buffer_t, /* token_buffer */ int* /* qop_state */ );
OM_uint32 gss_seal
(OM_uint32*, /* minor_status */
gss_ctx_id_t, /* context_handle */
int, /* conf_req_flag */
int, /* qop_req */
gss_buffer_t, /* input_message_buffer */
int*, /* conf_state */
gss_buffer_t /* output_message_buffer */
);
OM_uint32 gss_seal (OM_uint32*, /* minor_status */ gss_ctx_id_t, /* context_handle */ int, /* conf_req_flag */ int, /* qop_req */ gss_buffer_t, /* input_message_buffer */ int*, /* conf_state */ gss_buffer_t /* output_message_buffer */ );
OM_uint32 gss_unseal
(OM_uint32*, /* minor_status */
gss_ctx_id_t, /* context_handle */
gss_buffer_t, /* input_message_buffer */
gss_buffer_t, /* output_message_buffer */
int*, /* conf_state */
int* /* qop_state */
);
OM_uint32 gss_unseal (OM_uint32*, /* minor_status */ gss_ctx_id_t, /* context_handle */ gss_buffer_t, /* input_message_buffer */ gss_buffer_t, /* output_message_buffer */ int*, /* conf_state */ int* /* qop_state */ );
Wray [Page 46] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 46] RFC 1509 GSSAPI - Overview and C bindings September 1993
OM_uint32 gss_display_status
(OM_uint32*, /* minor_status */
OM_uint32, /* status_value */
int, /* status_type */
gss_OID, /* mech_type */
int*, /* message_context */
gss_buffer_t /* status_string */
);
OM_uint32 gss_display_status (OM_uint32*, /* minor_status */ OM_uint32, /* status_value */ int, /* status_type */ gss_OID, /* mech_type */ int*, /* message_context */ gss_buffer_t /* status_string */ );
OM_uint32 gss_indicate_mechs
(OM_uint32*, /* minor_status */
gss_OID_set* /* mech_set */
);
OM_uint32 gss_indicate_mechs (OM_uint32*, /* minor_status */ gss_OID_set* /* mech_set */ );
OM_uint32 gss_compare_name
(OM_uint32*, /* minor_status */
gss_name_t, /* name1 */
gss_name_t, /* name2 */
int* /* name_equal */
);
OM_uint32 gss_compare_name (OM_uint32*, /* minor_status */ gss_name_t, /* name1 */ gss_name_t, /* name2 */ int* /* name_equal */ );
OM_uint32 gss_display_name,
(OM_uint32*, /* minor_status */
gss_name_t, /* input_name */
gss_buffer_t, /* output_name_buffer */
gss_OID* /* output_name_type */
);
OM_uint32 gss_display_name, (OM_uint32*, /* minor_status */ gss_name_t, /* input_name */ gss_buffer_t, /* output_name_buffer */ gss_OID* /* output_name_type */ );
OM_uint32 gss_import_name
(OM_uint32*, /* minor_status */
gss_buffer_t, /* input_name_buffer */
gss_OID, /* input_name_type */
gss_name_t* /* output_name */
);
OM_uint32 gss_import_name (OM_uint32*, /* minor_status */ gss_buffer_t, /* input_name_buffer */ gss_OID, /* input_name_type */ gss_name_t* /* output_name */ );
OM_uint32 gss_release_name
(OM_uint32*, /* minor_status */
gss_name_t* /* input_name */
);
OM_uint32 gss_release_name (OM_uint32*, /* minor_status */ gss_name_t* /* input_name */ );
OM_uint32 gss_release_buffer
(OM_uint32*, /* minor_status */
gss_buffer_t /* buffer */
);
OM_uint32 gss_release_buffer (OM_uint32*, /* minor_status */ gss_buffer_t /* buffer */ );
OM_uint32 gss_release_oid_set
(OM_uint32*, /* minor_status */
gss_OID_set* /* set */
OM_uint32 gss_release_oid_set (OM_uint32*, /* minor_status */ gss_OID_set* /* set */
Wray [Page 47] RFC 1509 GSSAPI - Overview and C bindings September 1993
Wray [Page 47] RFC 1509 GSSAPI - Overview and C bindings September 1993
);
);
OM_uint32 gss_inquire_cred
(OM_uint32 *, /* minor_status */
gss_cred_id_t, /* cred_handle */
gss_name_t *, /* name */
OM_uint32 *, /* lifetime */
int *, /* cred_usage */
gss_OID_set * /* mechanisms */
);
OM_uint32 gss_inquire_cred (OM_uint32 *, /* minor_status */ gss_cred_id_t, /* cred_handle */ gss_name_t *, /* name */ OM_uint32 *, /* lifetime */ int *, /* cred_usage */ gss_OID_set * /* mechanisms */ );
#endif /* GSSAPI_H_ */
#endif /* GSSAPI_H_ */
References
References
[1] Linn, J., "Generic Security Service Application Program
Interface", RFC 1508, Geer Zolot Associate, September 1993.
[1] Linn, J., "Generic Security Service Application Program Interface", RFC 1508, Geer Zolot Associate, September 1993.
[2] "OSI Object Management API Specification, Version 2.0 t", X.400
API Association & X/Open Company Limited, August 24, 1990.
Specification of datatypes and routines for manipulating
information objects.
[2] "OSI Object Management API Specification, Version 2.0 t", X.400 API Association & X/Open Company Limited, August 24, 1990. Specification of datatypes and routines for manipulating information objects.
Security Considerations
Security Considerations
Security issues are discussed throughout this memo.
Security issues are discussed throughout this memo.
Author's Address
Author's Address
John Wray Digital Equipment Corporation 550 King Street, LKG2-2/AA6 Littleton, MA 01460 USA
John Wray Digital Equipment Corporation 550 King Street, LKG2-2/AA6 Littleton, MA 01460 USA
Phone: +1-508-486-5210 EMail: Wray@tuxedo.enet.dec.com
Phone: +1-508-486-5210 EMail: Wray@tuxedo.enet.dec.com
Wray [Page 48]
Wray [Page 48]
一覧
スポンサーリンク
