Introduction

Mircryption now provides robust encrypted logging procedures to replace the built-in mirc logging routines.  By using these encrypted logging procedures you can be sure that no one but you will be able to read your log files.

IMPORTANT: When using the mircryption encrypted logging functions, make sure to DISABLE the built-in mirc logging from the options->logging dialog, and any other logging functions that may be present in your other scripts.

There are three steps to encrypted logging:

The first thing you need to do is set the passphrase for your log files.  This passphrase will be used to encode log files using the blowfish algorithm.  All log files will be encrypted with this passphrase, regardless of the channel, and regardless of whether you are set to encrypt on a given channel.

The phrase you set will be stored in your master (encrypted) keyfile, but you will have to type it in manually when you want to view the encrypted logs, so make it something long and difficult to guess, but also something you dont mind typing.  A good idea might be to use the same keyphrase you used to encrypt your master keyfile.

To set the logging passphrase, right click in a channel window and select Mircryption -> Encrypted Logging -> set key for encrypted logging.

If you ever forget your logging key, you can simply list all your mircryption keys and look for the value for _mcloggingkey.

You only need to set your logging key once, but you may change it whenever you want.

After you have set your encryption passphrase, you need to add some logging rules to tell mircryption what information to log.

The idea of using logging rules, and the structure of these rules was developed by the original author a script called "log.mrc", aka (advanced logging) v1.0 by ash ([email protected]).

Logging rules are very concise and very flexible, and allow you to customize exactly what information to log and the name of the file to store it in.  You can use log rules to create nice hierarchies of log files appropriately split into different files by the current date, or use a single log file for every channel.

A subsequent section will describe log rules in detail.  A sample rule:

 log all in #,? from * to file Logs/&w/&t/&dm.log

You can add, delete and list rules through the right-click menu -> Mircryption -> Encrypted Logging.

You may load encrypted log files into a text editor, but they will be unintelligable.

To decrypt your encrypted logs, you need to use the provided Mircrypted File Viewer.  Just type in your logging passphrase and drag and drop your log files onto the form to decrypt them.