![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to rdemo.txt CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [PGP] / pgp / rsaref / doc|
Return to rdemo.txt CVS log | Up to [PGP] / pgp / rsaref / doc |
1.1 root 1: RDEMO:
2: Demonstation Program for RSAREF(TM)
3: User's Manual
4:
5: RSA Laboratories
6: March 21, 1994
7:
8: Version 2.0
9:
10: Copyright (C) 1991-4 RSA Laboratories, a division of RSA Data
11: Security, Inc.
12:
13:
14: This note describes RDEMO, a program that demonstrates features
15: of the RSAREF cryptographic toolkit.
16:
17: RDEMO is a simple program that exercises RSAREF's cryptographic
18: operations. With RDEMO, you can perform the cryptographic operations
19: of signing, sealing, verifying, and opening files, as well as
20: generating key pairs. There can be up to three different key pairs,
21: so you can simulate a multi-user environment.
22:
23: RDEMO has a main menu with six commands. The main menu is displayed
24: when you start up RDEMO, and is displayed again after RDEMO performs
25: a command. After you select a command RDEMO prompts for parameters
26: such as file names.
27:
28: RDEMO's commands and their parameters are summarized in the following
29: table.
30:
31: Note that these commands have the same names, but different
32: parameters and functions than those in version 1.0. There is no
33: maximum file size in the new program. The old program has been
34: renamed to OLDRDEMO.
35:
36:
37: RDEMO COMMAND PARAMETERS
38:
39: S - Sign a file name of file
40: digest content which private key to sign with
41: encrypt digest with message-digest algorithm
42: private key name of file in which to save
43: signature
44:
45: V - Verify a signed file name of file
46: digest content which public key to verify with
47: decrypt signature with message-digest algorithm
48: public key name of file in which signature is
49: compare result to digest saved
50:
51: E - sEal a file name of file
52: generate random data name of file in which to save
53: encryption key, IV(*) encrypted content
54: encrypt key with public which public key to seal with
55: key data encryption algorithm
56: encrypt content with key names of files in which to save
57: encrypted key and IV
58:
59: O - Open a sealed file name of file in which encrypted
60: decrypt encrypted key content is saved
61: with private key name of file in which to save
62: decrypt encrypted content recovered content
63: with key which private key to open with
64: data encryption algorithm
65: names of files in which encrypted key
66: and IV are saved
67:
68: G - Generate a keypair length of key in bits (508-1024)
69: generate RSA public/ name of file in which to save key pair
70: private key pair
71:
72: Q - Quit
73:
74:
75: (*) Initialization vector for cipher-block chaining mode.
76:
77:
78: NOTES
79:
80: 1. You select keys by number: '1', '2', or '3'. The first two key
81: pairs are built in. The third is generated by RDEMO's 'Generate a
82: key pair' command.
83:
84: 2. How you specify file names to RDEMO depends on your operating
85: system. RDEMO recognizes the special file name '-' as the
86: standard output stream (typically the screen display). You can
87: usually cancel an RDEMO command by giving a blank line in
88: response to a prompt for a parameter.
89:
90: 3. RDEMO reads and writes all files except the key pair file (which
91: it only writes) in binary mode.
92:
93: 4. Message-digest algorithm choices are MD2 and MD5.
94:
95: 5. For data encryption, the choices are DES, DESX, two-key
96: triple-DES (DES-EDE2), and three-key triple-DES (DES-EDE3).
97:
98: 6. If you want RDEMO not to display the main menu or any prompts,
99: put the string '-s' on the command line when you start RDEMO.
100: This is useful when RDEMO's input stream comes from a script
101: file.
102:
103: 7. RDEMO seeds RSAREF's random number generator with a fixed value.
104: As a result, RDEMO sessions with the same commands and
105: parameters produce the same results. The use of a fixed seed
106: value is not recommended for non-demonstration applications.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.