Abstract
The demand for security services requiring cryptography is now sufficiently widespread to make appropriate security APIs increasingly valuable tools in the design of secure systems. We will examine some of the APIs currently under development, like GSS-API, and argue that the designers of such APIs have to be explicit about the key management issues relevant to their interfaces.
This is a preview of subscription content, log in via an institution.
Preview
Unable to display preview. Download preview PDF.
References
J. Linn, Generic Security Service Application Program Interface, Version 2, Internet RFC 1508, 2 June 1995
IBM, Cryptographic Application Programming Interface, 2nd Edition, October 1990
The MOSAIC Program Office Cryptologic Interface Programmers Guide, Revision P1.2, 1 February 1994
NIST, Security Requirements for Cryptographic Modules, FIPS PUB 140-1, January 1994
NIST, Cryptographic Service Calls, Draft FIPS PUB XXX, 23 May 1994
X/Open, Distributed Security Framework, X/Open Snapshot, Draft 3, 18 August 1994
X/Open, Generic Cryptographic Service API (GCS-API), Draft, 14 February 1995
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 1996 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Gollmann, D. (1996). Cryptographic APIs. In: Dawson, E., Golić, J. (eds) Cryptography: Policy and Algorithms. CPA 1995. Lecture Notes in Computer Science, vol 1029. Springer, Berlin, Heidelberg. https://doi.org/10.1007/BFb0032367
Download citation
DOI: https://doi.org/10.1007/BFb0032367
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-60759-5
Online ISBN: 978-3-540-49363-1
eBook Packages: Springer Book Archive