Full Disclosure mailing list archives
Re: blocking Google Desktop
From: Michael Holstein <michael.holstein () csuohio edu>
Date: Tue, 14 Feb 2006 13:11:29 -0500
The first rule would get flowbits:noalert; flowbits:set,google.user.agent; And the second rule would get flowbits:isset,google.user.agent;
Is that global (if #1, then always #2), or is it "per-IP" ?I verified I can block the SSL session setup using the snort sig I posted the other day .. but it kills any Google SSL (gmail, groups, etc.) .. which is fine, provided I can only block google SSL to users that are running the desktop.
~Mike. _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- RE: blocking Google Desktop, (continued)
- RE: blocking Google Desktop Randall M (Feb 11)
- Re: blocking Google Desktop mamo (Feb 13)
- Re: blocking Google Desktop J.A. Terranson (Feb 11)
- Re: blocking Google Desktop Jason Coombs (Feb 11)
- Re: blocking Google Desktop J.A. Terranson (Feb 11)
- Re: blocking Google Desktop Michael Holstein (Feb 13)
- Re: blocking Google Desktop Prabhat Sharma (Feb 13)
- Re: blocking Google Desktop Valdis . Kletnieks (Feb 13)
- Re: blocking Google Desktop Michael Holstein (Feb 13)
- Re: blocking Google Desktop sekure (Feb 14)
- Re: blocking Google Desktop Michael Holstein (Feb 14)
- Re: blocking Google Desktop sekure (Feb 14)
- RE: Some one needs their coffee. WAS: blocking Google Desktop Randall M (Feb 11)
- Re: blocking Google Desktop gboyce (Feb 11)
- Re: blocking Google Desktop Nick FitzGerald (Feb 11)
- Re: blocking Google Desktop gboyce (Feb 11)