It is unfortunate about there privacy policy, but I consider all mail unsafe, as mail passes through the net from server to server they can be intercepted, is there any guarantee your mail being sent through the net is unread/analyzed/archived before you read it? The only solution is using PGP and I see you use that which is smart. We all know the governments of this world are doing their best to intercept emails and search them for certain phrases/keywords. I consider spam detection a privacy concern as well because they analyze email for certain things. I was just running dsniff and sniffed my password from clicking igoogle from my gmail client, it sent the password in clear text unless dsniff sniffed the cookie. What is a good way to enforce a good cookie policy for firefox?<br>
Best Regards,<br>defcon<br>Yes there is allot of good information in the archives, I should have searched them, although sometimes old questions have new answers<br><div class="gmail_quote">On Sun, Mar 2, 2008 at 4:41 PM, scar <<a href="mailto:scar@drigon.com">scar@drigon.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
Chris Palmer @ 2008/03/02 14:15:<br>
<div class="Ih2E3d">| defcon writes:<br>
|<br>
|> I have been using tor for a while now, and I absolutely love it, although<br>
|> the only thing keeping me from using it, is the insecurities of the exit<br>
|> nodes. I know to truly stay anonymous you should stay away from personal<br>
|> accounts "but" how can I connect through tor to gmail or other ssl<br>
enabled<br>
|> services without risking my password being sniffed or my dns request<br>
being<br>
|> hijacked. Any advice would be greatly appreciated!<br>
|<br>
| The answer is to use SSL. I'm not sure but I think you meant to say<br>
"... or<br>
| other *non*-ssl enabled serviecs...".<br>
|<br>
| In the particular case of Gmail: Gmail normally uses HTTPS for the login<br>
| phase but not thereafter. That is of course totally silly, because<br>
while the<br>
| attacker won't see your password they will still see your Gmail session<br>
| cookies. That's all they need to hijack your Gmail session -- they don't<br>
| need your password. BUT! the good news is that if you go to Gmail via<br>
| <a href="https://mail.google.com/" target="_blank">https://mail.google.com/</a>, Gmail will use HTTPS for the entire session, not<br>
| just the login phase, and then you are as safe as anyone ever can be from<br>
| network eavesdroppers (including traffic-sniffing Tor operators).<br>
|<br>
<br>
</div>sorry, but that's not entirely true. if you watch your tor circuits,<br>
gmail will jump to one insecure connection on port 80 to do "something"<br>
during the login phase, and then go back https, even if you use<br>
<a href="https://mail.google.com/" target="_blank">https://mail.google.com/</a>. this has been discussed to death, please<br>
search the archives.<br>
<br>
the best solution is to stop using gmail, since they probably keep your<br>
email forever. next-best solution is to use a 3rd-party email program<br>
and configure it to use TLS or SSL for your <a href="http://pop.gmail.com" target="_blank">pop.gmail.com</a> and<br>
<a href="http://smtp.gmail.com" target="_blank">smtp.gmail.com</a> connections.<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iD8DBQFHyztAXhfCJNu98qARCPgTAJ9IcmnkJSyq50tH6m0YM5LnWzwmyQCfdmkd<br>
s63d6BRRavBoj9CYY5daTY8=<br>
=VKYu<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br>