Introduction
============
DIL stands for "Device Intervention Layer". As the name says, it's used to intervene into a data-stream. It acts like a layer between the source application and the target device.
Plugins are used to manipulate, encrypt or monitor the data.
Features
========
Device
------
+ Plugin based
- Plugins can act in two modes:
+ Intervene
- Ciphers, others that manipulate the data
+ Non-intervene
- Monitors, analytical plugins
- Plugin can request a seed
+ Two seed input modes:
- Keyborad (a MUI passphrase-request will open, all builtin)
- File
+ Supported command-sets
- EXEC, TD, ETD, TD64, SCSI, DIL
+ API for shell-commands
Shell-commands
--------------
Some shell-commands helps to make things easy:
+ dilCheckCfg Check a configuration
+ dilPlugInfo Show informations about a plugin
+ dilGenDosDriver Generate a DosDriver
+ dilMount Mount a unit
+ dilUnMount Unmount a unit
+ dilRevoke Revoke a unit
Plugins
-------
+ Easy to design
+ 3 plugins so far:
- default.dilp Used as default, it does nothing, just forwards the data.
- blockmon.dilp Used to monitor the disk-access of the loaded filesystem.
- poly.dilp En/decrypt the data using a polymorphic function. The strength depends on the used blocksize and can be from 4096 to 262144 bits.
Grab the user and developer archive
here or get it via MorphUp...
