Also, XSPLIT will produce N files of the same size as the original file you feed it.
I just glanced at the .doc and ran it once last night on my PC -- haven't looked at the source -- but a possible application of this occurred to me this morning. The N files are binary, but it should be easy to restrict them to ASCII using a command-line switch or a file for PRNG input, right? Then they would be suitable for Internet (re)mailing. (Concerns about cryptographic integrity are irrelevant for my purposes.) A remailer could receive, say, a 5k message, which might be ~4.5k after peeling off that remailer's layer of encryption. XSPLIT could then be invoked to produce several ASCII files of identical size. These bogus files could be mailed to various remailers at the same time as the "real" file, with a prepended instruction to send 'em to the bit bucket. Of course, latency would then have to be added before processing the "real" file to defeat traffic analyis. I'm probably missing something, but it's a thought anyway... Alan Westrope <awestrop@nyx.cs.du.edu> __________/|-, <adwestro@ouray.denver.colorado.edu> (_) \|-' finger for pgp 2.6 public key "Silent, We the Empire Await, Trystero!" -- Pynchon (sorta...)