There may be situations where it's impossible to rule out that the online computer system is compromized, and where it may even bear
unacceptable risks to move the portable OmniMix system with all its executables back and forth between that online computer and the
hardened offline device where your secret messages reside.
In such cases it would be favourable to install a second OmniMix instance on that insular device in order to create all encryption
protected remailer packets there without having to fear being bugged. The resulting text files are then safely transferred to the
online computer on a removable device and from there forwarded to the remailer network.
To get that working you first you have to ensure that at the offline computer all relevant remailer statistics text files are
up-to-date. So copy at least the Mixmaster and Yamn statistics files mlist.txt.raw_mix and pubring.mix.raw_mix resp. mlist2.txt.raw_yam
and pubring.mix.raw_yam from your online system's 'mix' folder to the offline installation. Then, as the remailer pool directory of the
OmniMix system ('mix\pool'), in which Mixmaster and Yamn store newly created packets, is routinely cleared before and after processing
to avoid unauthorized access, further adjustments have to be made to get hold of these files. Go to the StateInt tab and change Del(ete)
to 'Never' to keep newly created remailer packets after processing. Now switch to Simulation Mode to avoid unsuccessful mailing attempts
and send your messages to OmniMix to convert them into remailer packets.
Finally relocate all the resulting files to the online system's remailer pool folder, where you have to select Del(ete) 'After' instead
of 'Always' to preserve the injected files for delivery e.g. with the next processed (dummy) message.
Be aware that with Del(ete) set to 'Before' or 'Never' your remailer chunks remain undeleted even after closing OmniMix! So take care.
