Feature Request - Secure Password Storage about nagstamon HOT 3 CLOSED

Hi,
this sounds absolutely great. The key store has been just as is because it worked but you are totally right. Can you provide the changes you did for a first start? Might be needed to be enhanced regarding the GUI but seems not to be a huge task.
Thanks + regards

from nagstamon.

Please see above referenced pull request.

Further changes I would recommend considering:

1. Saving proxy server password (as "proxy_username@proxyserver") in secure fashion
2. Consider if autologin_key should be saved securely (wasn't sure what this was)
3. Modify GUI to warn user if keyring module is not available and save password option ticked

Not related to the secure password storage but I would also recommend removing the obfuscation of the username (normal & proxy) options. This is not really sensitive like the passwords and if you use a configuration management tool like Chef, Puppet etc then this is a real pain in the neck when generating configuration file templates.

If you'd like any further assistance with any of the above please let me know.

from nagstamon.

Considered stable with latest commit 595d414.

from nagstamon.