The theory of operation is very simple: To export Muq source in problematic cases, we do the following:
The practical procedure is equally simple:
muq-crypto-src.tar.gz, which you may simply delete. (If you've made modifications to this part of the code, you'll have to do what I did: Print it out on hard copy, transport it to a crypto Free World country such as Finland or Switzerland, and type it in again there.)
muq/bin/muq-src-tarscript to produce a compressed tar archive. (You'll likely want to run
muq/bin/muq-distcleanfirst.) This file is exportable as sea salt, unless the secret laws have been tweaked yet again in some unpredictable way.
muq-crypto-src.tar.gzfrom some Free World site such as
muq-crypto-src.tar.gzin your home directory.
muq-crypto-src.tar.gzunpack will overwrite the insecure parts of the Muq source code with secure versions, and you are ready to compile and run.
Caveat: Be careful not to accidentally try compiling and running the insecure Muq server version in a network of secure Muq servers. The result will probably be obscure failures with unhelpful diagnostics. This is unfortunately legally required, as far as I can see: Any code specifically designed to detect this would count as 'hooks for encryption' and by the spooks' interpretations of their powers would land me in jail. Think of it as your tax dollars at work.
Go to the first, previous, next, last section, table of contents.