Published: February 11, 1993
Author(s)
James Dray (NIST), David Balenson (TIS)
Conference
Name: Privacy and Security Research Group Workshop on Network and Distributed System Security
Dates: February 11-12, 1993
Location: San Diego, CA
Citation: Privacy and Security Research Group Workshop on Network and Distributed System Security: Proceedings, pp. 125-133
The Advanced Smartcard Access Control System (ASACS) was developed by the National Institute of Standards and Technology in conjunction with Datakey and Trusted Information Systems. The system includes a smartcard with public key capabilities and a portable reader/writer with computational capabilities, including a microprocessor, programmable memory, a keypad, and an LCD display. Through the use of a layered interface, ASACS was integrated into several demonstration programs and into the TIS Privacy Enhanced Mail (TIS/PEM) system. This paper provides a brief overview of the ASACS.
The Advanced Smartcard Access Control System (ASACS) was developed by the National Institute of Standards and Technology in conjunction with Datakey and Trusted Information Systems. The system includes a smartcard with public key capabilities and a portable reader/writer with computational...
See full abstract
The Advanced Smartcard Access Control System (ASACS) was developed by the National Institute of Standards and Technology in conjunction with Datakey and Trusted Information Systems. The system includes a smartcard with public key capabilities and a portable reader/writer with computational capabilities, including a microprocessor, programmable memory, a keypad, and an LCD display. Through the use of a layered interface, ASACS was integrated into several demonstration programs and into the TIS Privacy Enhanced Mail (TIS/PEM) system. This paper provides a brief overview of the ASACS.
Hide full abstract
Keywords
access control; computer security; electronic mail; smart cards
Control Families
None selected
) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)
