CONTENTS

• Access Control & OS
  1. Tutorial Overview
  2. Windows Lab Procedures
  3. Unix 's File System
  5. SOLARIS
  6. SOLARIS Lab Procedures
• Apache SSL
  1. Tutorial Overview
  2. Installing Components
  3. Creating a Certificate
  4. Configuring Apache SSL
• Authenticode
  1. Tutorial Overview
  2. Installing .NET Framework SDK
  3. Signing a File
  4. Verifying a Signature
• Common Criteria Methodology
  1. Tutorial Overview
  2. General Evaluation Guidelines
  3. Evaluation of Functional Requirements TOE
  4. Questions
  5. References
• Cryptography with C#
  1. Tutorial Overview
  2. C# .NET Framework Examples
  3. Message Authentication
  4. Digital Signatures
  5. Exercises
  6. Resources
• Cryptographic Libraries
  1. Tutorial Overview
  2. OpnelSSL's Toolkit
  3. Java Cryptography Extension
  4. Exercises
  5. Resources
• Firewall Access Control Lists
  1. Tutorial Overview
  2. Technical Details
  3. Telnet and FTP
  4. Lab Report
• Firewall Configurations & Attacks
  1. Tutorial Overview
  2. Attacking Without a Firewall
  3. Filter an IP Address
  4. Filter TCP Traffic
  5. Misconfigured Firewall Examples
  6. Exercises
• Forensics
  1. Tutorial Overview
  2. Exercises
  3. Hidden Data
  4. Steganography
  5. Viewing IE Cache
  6. Installation Instructions
• IIS & Server 2003
  1. Tutorial Overview
  2. Installing Components
  3. Create a Certificate Request
  4. Submit a Certificate Request
  5. Installing a Certificate
  6. Secure Certificate Services
  7. Secure the Server
  8. Secure IIS
• IPSec and VPN Tunnel
  1. Tutorial Overview
  2. Technical Details
  3. VPN Tunnel Parameters
  4. Lab Report
• Java Code Signing
  1. Tutorial Overview
  2. Installing Java & Signing a File
  3. Verifying a Signature
• Network Protocol Analyzers
  1. Tutorial Overview
  2. TCPDump
  3. Ethereal
  4. Sniffer Distributed System
  5. Telnet Session
• PKI
  1. Tutorial Overview
  2. Installing Thunderbird
  3. Installing GPG and Enigmail
  4. Create and Use Key Pairs
• Secure Cookies
  1. Tutorial Overview
  2. Installing Components
  3. Creating a Secure Cookie
• Three Tier

1. Verify Signature. You must have the certificate from the signer in order to verify the signature of a file. All Authenticode will do is recomputed the hash value and compare it to the hash value that is provided in the signature. If the values match then the file has not been compromised. This does not guarantee that the file is not dangerous, just that it has not changed since it was signed.

To see the importance of installing and trusting the signers certificate you can try to verify the signature without installing the certificate. To verify a file's signature use the command signtool verify –v good.dll

The command id described in some detail to provide a better understanding.

2. Install Certificate. Navigate to the public certificate, which is at the SDK's installation directory and double click it to open the certificate window. Click on Import Certificate to open the certificate import wizard. Follow the on-screen instructions to import the certificate. You can keep the default settings to import the certificate.

You will be prompted to confirm the installation of the certificate because it was not granted by a CA. This is done because once you install a certificate Windows will automatically trust any certificate issued by this CA, which can lead to dangerous situations if the certificate is not coming from a trusted party. Click Yes to install the certificate.

You can now close the certificate window and reopen it to see that the certificate is now trusted. This is indicated by the absence of the red ‘X’ over the certificate image in the upper left hand corner of the window.

3. Reverify the Signature. Now you can verify the signature by using the same command as before, which is signtool verify –v good.dll.

4. Verifying a Compromised File. To see how Authenticode acts when a compromised file’s signature is being verified download the bad.dll, which is a modified version of the original after being signed. Verify the signature on this file by using the same command: signtool verify –v bad.dll.

You should see this error message because the original signature does not match up with the signature you computed.

Browse Pages << | < | 1 2 3 4 | > | >>