What's new in pyTunnel 2.4
Aug 22, 2012
- Tunnel security introduced. Each time a process requests data from a tunnel socket it goes through a verification process. If the verification fails, the communication is closed. The verification process is controlled by the TUNNEL_SECURITY_CLASS parameter in the tunnels.config file. The parameter format is TUNNEL_SECURITY_CLASS=: where filename is the name or path to a python module file, and is the name of a class within the file.
- Release 2.4 includes the verify.py module which includes the following verification classes: verify:BaseRequestVerification - all requests are validated. In other words, no tunnel data security verify:perRequestVerification - tunnel manager application will ask user to confirm access during each request verify:perProcessVerification - tunnel manager application will ask user to confirm access once per process verify:perProcessPortVerification - tunnel manger will ask user to confirm access once per process and tunnel port.
New in pyTunnel 2.3 (Feb 23, 2012)
- new keyring. new keyring will prompt for a password when accessing encrypted passwords. The prior version the keyring would use it's own magic "salt" to encrypt passwords, which changes from machine to machine and does not allow the keyring to be reused on different machines.
- removed the connection reaper, I've found that it is more trouble than its worth.
New in pyTunnel 2.2 (Feb 23, 2012)
- password encryption is now handled by the keyring module and passwords are stored in a separate file than the pytunnel config file.
- tunnels now make sure that there is not already something else listening the local port before starting.
- binary distribution is a single .exe file
New in pyTunnel 2.1 (Oct 29, 2011)
- Under certain conditions a password would get corrupt in the config file. Upon reading the config file the password would be encrypted and the config file was updated, but de-crypt fail - causing the password to get lost. An additional check was added so that in event a password can not be de-crypted it will remain in the config file as plain text.
- You can now connect using a RSA or DSA key file. Previously you could configure a key file but RSA and DSA connections failed.
- You can now set individual tunnels to be automatically started or manually started. * You can add notes to each tunnel