B. Kaliski, \PKCS #7: Cryptographic Message Syntax, Version 1.5," RFC 2315, Mar 1998. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Signed Executables for Linux - van Doorn, Ballintijn, Arbaugh (2001) (Correct)
....with a single container, and the implementation requires only a small number of kernel modi cations. To permit exibility, we added attributes to the signature, and rather than inventing our own formats used standards as much possible. Hence we use ELF [9] for our executable binaries, the PKCS#7 [10] format for storing our signatures, and the X.509 [21] format for storing public key certi cates. Our system ensures its integrity guarantees for executables at load time. It does not provide protection against run time attacks such as code injection attacks (e.g. bu er over ows) These should ....
....are used during execution. More speci cally, the signature covers the ELF parts listed below: ELF header. All program headers. All loadable segments, and The interpreter segment. The rationale behind signing these ELF portions is described in the sections below. We use the PKCS#7 [10] format for our digital signatures implementation. A human readable example of such a signature is shown in Figure 2 which is taken from the bin ls program. We chose the PKCS#7 format since it is extensible, allowing us to store extra information in the future. It is also useful that it is a ....
B. Kaliski. PKCS #7: Cryptographic Message Syntax (Version 1.5). In Internet Request for Comments (RFC) 2315. March 1998.
A Chosen Ciphertext Attack against Several E-Mail Encryption.. - Katz, Schneier (2000) (2 citations) (Correct)
No context found.
B. Kaliski, \PKCS #7: Cryptographic Message Syntax, Version 1.5," RFC 2315, Mar 1998.
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