| Product Standard |
|---|
| Security: Secure Communication Services |
| Document Number: X98SS |
©January 1998, The Open Group All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of the copyright owners.
Motif,® OSF/1,® UNIX,® and the "X Device"® are registered trademarks and IT DialToneTM; and The Open GroupTM; are trademarks of The Open Group in the U.S. and other countries.
Secure Communication Services
No label.
A product registered as conformant to this Product Standard provides a secure communication context when interoperating with similar systems as part of a distributed system. Within this secure context it must support the authentication and integrity feature sets defined in the X/Open GSS-API Specification.1 It may also optionally support the confidentiality and delegation feature sets.
These services are accessible via a programming interface, the Generic Security Service API (GSS-API). The security services are independent of particular communications services and protocols, but can be used in conjunction with various communications services and protocols to provide secure communication. Details of the particular authentication technology employed (for example, Kerberos, KryptoKnight), must be stated in the Conformance Statement associated with any conformant system.
To conform to this Product Standard a system must support all mandatory functionality defined in the referenced specification, and make appropriate declarations concerning the security mechanism technology as defined below.
Not applicable.
X/Open GSS-API Specification, Part 1: GSS-API, Part 2: C-language Bindings.
ISO C Language.2 ISO C language source programs invoking the services of this Product Standard must be supported by the registered product.
X/Open GSS-API Specification, Section 5.2, Mechanism-independent Token Format.
No specific security mechanism technologies are mandated, but full details of the actual authentication technology (for example, Kerberos, KryptoKnight), together with any associated implementation options where compatibility is required to ensure interoperability, must be recorded in the Conformance Statement. These details indicate with which other systems the product is likely to interoperate.
Not applicable.
Not applicable.
None.
None.
Not applicable.
Any comments relating to the material contained in this document may be submitted to The Open Group at:
The Open Groupor by electronic mail to:
Apex Plaza
Forbury Road
Reading
Berkshire, RG1 1AX
United Kingdom
OGSpecs@opengroup.org