|
|
still insecure without SSL
When working at public hotspots, I always check whether my system is sending out cleartext username password combos using DsnifFE. .Mac through port 25 does, and the POP does as well. I therefore disable .Mac when on a public wireless network. I'll have to try this alternate port trick to see if it makes a difference. However, I don't discount the fact that real hackers might also be scanning for alternate ports used by major ISPs.
still insecure without SSL
I use ssl on dot mac. Port 587 supports this and i use imap secure on port 993
still insecure without SSL
awesome, that did not used to be the case. Does .Mac mail still require you to send "from" your @mac.com e-mail address? I guess I could try it... I have about 20 different "from" addresses with the various jobs and organizations I am involved in. They all filter into 2 Gmail accounts for the excellent spam filtering. Between them, there are over 103,000 junk mails in the Spam folders from the past 30 days.
still insecure without SSL
Uhhh...instead of disabling your .Mac accounts you could just use SSL. After all, you did mention SSL at the bottom of your post. ;)
still insecure without SSL
uhh (whatever language that is...)
still insecure without SSL
I was under the impression that .Mac uses SSL for login/password even at a hotspot ... now I'm concerned ...
still insecure without SSL
This is very unsettling. Everything is sent clear text when accessing .Mac on a public wireless network?!?!?! |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.07 seconds |
|