rekey1
Binary key regeneration for kaya web applications
Usage
rekey FILE1
[FILE2
[]]
Overview
rekey gives all Kaya binaries specified on the command line a new application secret key
The application secret key makes webapps and webprogs secure, by encrypting the state transfers. If you receive a webapp or webprog binary from someone else, or you believe someone untrusted has had read access to your binary, you can use the rekey application to generate a new application secret key without needing a recompile.
Binary distributors of Kaya applications are strongly recommended to use 'rekey' as part of the installation process.
Obtaining
The latest release of Kaya can be obtained from <http://compsoc.dur.ac.uk/kaya/download.php>
Development versions can be obtained using darcs(1) from <http://compsoc.dur.ac.uk/kaya/darcs/>
Security
rekey will use /dev/random to generate the new key if possible. If /dev/random is unavailable (Windows without MinGW, for example), the new key will be generated pseudo-randomly. This may allow an attacker to easily guess the new key. In environments where security is a concern, therefore, we strongly recommend recompiling with kayac(1) rather than using rekey if /dev/random is unavailable.
rekey will give a warning when rekeying if /dev/random is unavailable.