Contents
1. Where & how configurations saved
2. Identifying a fraud in a group of files
3. Public Private Keys & FingerPrints
4. Example using multiple backups
1. Where & How Configurations Saved
Although not as important as 2. below, it’s good to know
what DoCrypt –or any program– does with your choices.
All of your configuration files are in folder
PROP_DIR
It's the same place as docrypt.jar
JAR_PATH
All DoCrypt saved program data is under this folder.
( click displays current configuration. )
2. Identifying a Fraud in a Group of Files
Chapter 7 Secret Key Assurances
pages 59-62: Integrity
How cryptographic fingerprints work
Hands-on cryptographic fingerprints
· Verify your copy of DoCrypt against our published fingerprint
(Click File radio button to fingerprint our program doCrypt.jar.
Matching it against our website's fingerprint verifies its integrity.)
· Using fingerprints at end of DES–AES Messages
Shows the constancy of crypto fingerprints.
· more
see Message and/or File Learn More
FingerPrint a Group-of-Files Example
Launching fingerPrinter here will do (1) and (2) below
for CURRENT_CONFIG (the current configuration)
Chapter
9 Public key pioneers
10 How 
works
12 How 
works (Digitial Signatures)
15 Comparing 
16 Distributing s with Digitial Certificates
17 Certificate Authority (x.509 centralized control)
18 Pretty Good Privacy (distributed trust)
§ some 
mechanics…
11 Making pairs
13 Using in fingerprints
14 Fingerprint (hash, digest) assurances
Hands-on demos
 |
Alice & her public–private key pair |
|
 |
Alice, Bob and their respective public–private key pairs |
|
Another Strong Argument for FingerPrints
You might, reasonably, think encrypted text can't changed
so it decrypts to meaningful text. Not so. See this
'corrupt encryption' hands-on. (also at Message Cipher Learn More)
