Fixing issue #258, bad keyfile permissions.

This spits out a warning to the console, but ideally it would also
issue a warning to the GUI for those who didn't start it from the
console. N.B. the warning is a one shot thing, since it fixes the
problem in a way essentially undetectable in the future, so it
should be done right if it is to be done at all.
Maybe we should even disable all keys automatically if the keyfile
is found in an insecure state.
Fix #263 & #262: insecure keyfile permissions.

* Added conditional to keyfile fix code that excludes windows.
* Cleaned up old keyfile permissions fix.
* Added umask (not conditional against Windows, because I don't think that is necessary).
Make warning message more specific.
Merge branch 'master' of https://github.com/Bitmessage/PyBitmessage into keyfile_perm_fix
Merge branch 'master' of https://github.com/Bitmessage/PyBitmessage into keyfile_perm_fix
No paranoid key disable for bad keyfile perms.
Spelling.
Logging fixes.
Merge branch 'master' of https://github.com/Bitmessage/PyBitmessage into keyfile_perm_fix
Merge branch 'no_propagate_loggers' into keyfile_perm_fix

Conflicts:
	src/shared.py
Switch an stderr message to logger.
Clarify IOError handling with comment.
added translations
Packaging for multiple distros
Refactor type 2 message decoding, drop any extra lines from subject.
This allows other clients to insert headers in extra lines of text between
the Subject and Body fields of the message, as discussed on the 24x7 mailing
list. The PyBitmessage client was never able to meaningfully display
multi-line subjects, so this does not break anything. The extra lines are
thrown away and never stored anywhere, so this also protects against
watermarking attacks.
Fixing the puppy script
Some Arch dependencies
Duplocated command in Makefile
python2-gevent is optional
Adding configuration option to listen for connections when operating with a SOCKS proxy.