3 citations found. Retrieving documents...
J. Daemen and V. Rijmen. AES proposal: Rijndael. Advanced Encryption Standard Submission, 2nd version, March 1999.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Zero-Interaction Authentication - Corner, Noble (2002)   (19 citations)  (Correct)

....page data and file names; this makes it ideal for constructing cryptographic file services. The FiST distribution also includes a proof of concept cryptographic file system, Cryptfs. 3.1. 1 File and Name Encryption The kernel module encrypts both file pages and file names with the Rijndael cipher [8]. We selected Rijndael for two reasons. First, it has been chosen as NIST s Advanced Encryption Standard, AES. Second, it has excellent perfor mance, particularly for key setup a serious concern in the face of per directory keys. ZIA preserves file sizes under encryption. File pages are ....

....of CFS. A user supplies his keys only once; thereafter, the file system is empowered to decrypt files on the user s behalf. Cryptfs significantly outperforms CFS, and our benchmarks show Cryptfs in an even better light. This is primarily due to the replacement of Blowfish [29] with Rijndael [8]. Microsoft Windows 2000 provides the Encrypting File System (EFS) 19] While EFS solves many administrative issues, it is essentially no di#erent from CFS or Cryptfs. A single password serves as the key encrypting key for on disk, per file keys. EFS still depends on screen saver or suspension ....

J. Daemen and V. Rijmen. AES proposal: Rijndael. Advanced Encryption Standard Submission, 2nd version, March 1999.


Protecting Applications with Transient Authentication - Corner, Noble (2003)   (2 citations)  (Correct)

....pick the more convenient option. 5.2 Application Programming Interface Before a user starts an application that employs the Transient Authentication API, that user must have one or more master keys for that application installed on their token. In our implementation, master keys are 128 bit AES [8] keys. These keys must be installed by an administrative authority, and can never be exposed beyond the token. As we will see, the master key is typically used as a key encrypting key, but can sometimes protect small data items directly. Once a key is installed, the API is available. It is ....

....client machine was an IBM ThinkPad X24, with 256 MB of physical memory and a 1.1 GHz Pentium III CPU. The token was a Compaq iPAQ 3870 with 64MB of RAM. They were connected by a Bluetooth [16] wireless network running in PAN mode. All encryption, except the authentication phase, is done using AES [8] with 128 bit keys. The token is somewhat more powerful and larger than current wearable devices. However, the rapid advancements in embedded, low power devices makes this a realistic token in the near future. 6.1 Transparent Protection Transparent protection has no effect on system performance ....

J. Daemen and V. Rijmen. AES proposal: Rijndael. Advanced Encryption Standard Submission, 2nd version, March 1999.


USENIX Association - The First International   (Correct)

No context found.

J. Daemen and V. Rijmen. AES proposal: Rijndael. Advanced Encryption Standard Submission, 2nd version, March 1999.

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