| "Data encryption standard," Technical Report FIPS-46, U.S. Department of Commerce, Jan. 1977. |
....to the active node. This is accomplished using the AEGIS Secure Bootstrap Architecture which is able to detect alterations in the firmware and within the operating system. See [12] 13] for further detail on AEGIS. Clients of SANE have access to several cryptographic primitives. These are DES [14] for symmetric key encryption, SHA1 [15] for keyed hashes, and DSA [16] for public key signatures. Other equivalent primitives could be provided. All the algorithms have been implemented in Caml but due to performance degradation, we use a C version of SHA 1. Access to this implementation of ....
"Data encryption standard," Technical Report FIPS-46, U.S. Department of Commerce, Jan. 1977.
....4.2 Cryptographic Primitives SANE provides access to various cryptographic primitives. These can be used by other applications as is or as building blocks for more complex protocols. The services initially provided are: ffl public key signatures (DSA [NIS94] ffl symmetric key encryption (DES [NBS77] ffl (keyed) hashes (SHA1 [NIS95] This set of primitives may be enriched in the future. All the algorithms have been implemented in Caml but due to performance degradation, we use a C version of SHA1. Access to this implementation of SHA1 occurs through a Caml interface, taking care to avoid ....
Data Encryption Standard. Technical Report FIPS-46, U.S. Department of Commerce, January 1977.
....4.2 Cryptographic Primitives SANE provides access to various cryptographic primitives. These can be used by other applications as is or as building blocks for more complex protocols. The services initially provided are: ffl public key signatures (DSA [NIS94] ffl symmetric key encryption (DES [NBS77] ffl (keyed) hashes (SHA1 [NIS95] This set of primitives may be enriched in the future. All the algorithms have been implemented in Caml but due to performance degradation, we use a C version of SHA1. Access to this implementation of SHA1 occurs through a Caml interface, taking care to avoid ....
Data Encryption Standard. Technical Report FIPS-46, U.S. Department of Commerce, January 1977.
....when using a C code implementation, we cannot catch type system errors internal to that code, nor take advantage of the garbage collection mechanism available in the runtime. For these reasons, we tried to limit the amount of non Caml code in our system. We also provide implementations of DES [NBS77] and DSA [NIS94] we retain the Caml implementation of each of these for these reasons and because they are not on the critical processing path for every active packet. In the future, we intend to investigate the feasibility of statically integrating Caml native code into the byte code ....
Data encryption standard. Technical Report FIPS-46, U.S. Department of Commerce, January 1977.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC