[DFD] new directions for DFD

[Travis]

Hi, I'm emailing you about two new directions for DFD.

The first direction I'm exploring is having the client script set
everything up; commands, variables, and rules, and freeze this
configuration like a virtual machine.

Then, the runtime script will load and thaw these rules, freezing them
at the end of its run each time, so that every change is persistent.

Secondly, what's really going to open up DFD will be a counterpart sniffer
that looks for certain traffic - video games, bittorrent, even SPA, and
triggers rules based on that.  Rather than having a hundred sniffers doing
this, I'd like to have one unified sniffer that can have sniffing modules
loaded up to detect things, and the end user just configures what modules
to load.  You shouldn't need ten sniffers to do ten traffic-related rule
changes.  I've built a prototype sniffer for bittorrent, but it still needs
a lot of work and some of that is in the supporting library, Impacket.
-- 
Crypto ergo sum.  http://www.subspacefield.org/~travis/
Truth does not fear scrutiny or competition, only lies do.
If you are a spammer, please email john at subspacefield.org to get blacklisted.