full-disclosure - blocking Google Desktop

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <9E97F0997FB84D42B221B9FB203EFA270224844B@dc1ms2.msad.brookshires.net>
Date: Fri Feb 10 21:11:49 2006
From: toddtowles at brookshires.com (Todd Towles)
Subject: blocking Google Desktop

 

> 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