> Upon launching, Google Desktop made several HTTPS connections to both > www.google.com and desktopservices.google.com. It used IE's proxy > settings - we have an ISA cache/proxy that does integrated > auth. If it handled NTLM auth, I'm sure it can do basic > proxy auth as well. > However, blocking it on the network-level doesn't do a whole > lot of good > for corporations with a large mobile population. They connect > elsewhere (home, client site, hotel, etc.), and your > proprietary data is still making it to Google.
Looks like a great target for Pharming attacks. Thanks for all your data sent to me over an SSL connection. =) -Todd _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
