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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <43F21D51.3030307@csuohio.edu>
Date: Tue Feb 14 18:11:41 2006
From: michael.holstein at csuohio.edu (Michael Holstein)
Subject: blocking Google Desktop

> 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.