|
Post by Belzecue on Jul 26, 2010 13:17:57 GMT 1
Hi. You should offer the option to NOT save the password but rather enter it one time prior to first check of session. I know you encrypt passwords in the config file, but storing password in memory only should be an option too. Thanks.
|
|
|
Post by Kevin on Jul 26, 2010 14:16:38 GMT 1
The official Google notifier works like this, maybe this is better for you? I wrote Spiffy because this was one of the things that annoyed me about other Gmail notifiers.
|
|
|
Post by Kevin on Aug 1, 2010 22:32:59 GMT 1
You can also save the cfg file in a different location, see Help for more info.
|
|
|
Post by NJ1314 on Dec 12, 2010 20:59:35 GMT 1
Hi Kevin, yes the Google notifier works like that but only checks one account and with the new account switching option, is always getting confused as to which account is being checked. Hence the need for a great program like Spiffy.
But I agree, there should be an option to prompt for passwords when logging on.
Consider the scenario where a business person is using a client computer at a client site. Say they have Spiffy configured for their personal Gmail and their business Google Apps account and are using it on the client computer. The problem is that the client administrator could at anytime change the user's password and log in as them on the client computer. And then the client would have full access to the person's personal Gmail and their business Google Apps email.
Or the even simpler scenario with a person who likes Spiffy and wants to use it on their work computer to check their personal Gmail. Again their employer could change their password, log in as them, and through the saved password in Spiffy, access that person's personal Gmail.
That's the problem I see. Spiffy may be great for use on a home computer but the reality is that we use our work computers all day long.
Do you think you could add the option to prompt for passwords upon logon (similar to the official Google notifier) and not save them in the cfg file?
Thanks!
|
|
|
Post by Kevin on Feb 27, 2011 22:08:14 GMT 1
The problem is that the client administrator could at anytime change the user's password and log in as them on the client computer. And then the client would have full access to the person's personal Gmail and their business Google Apps email. Or the even simpler scenario with a person who likes Spiffy and wants to use it on their work computer to check their personal Gmail. Again their employer could change their password, log in as them, and through the saved password in Spiffy, access that person's personal Gmail. This person can only see new mails, he cannot login to your Gmail account from Spiffy. Also your Gmail password is encrypted, only your username is visible in the Accounts window.
|
|