Manu wrote:
> Mark,
>
> thanks a lot for your answer. Well, I don't think that the effort would
> justify the result.
>
> So maybe I will try some sort of double transparent proxy (one for port 80
> and the other for port 443) or something else.
>
FYI you can do transparent proxies for HTTP - but not HTTPS. That would
be called a "man-in-the-middle" attack, and SSL by design resists such
fiddling.
If your intent is to "know" what URLs your internal staff are
downloading from HTTPS servers, then I think you won't find an easy
answer. Only a terminating proxy will achieve what you want - and then
that's dependent on how the client is configured.
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Snort-users mailing list
Snort-users@lists.sourceforge.net
Go to this URL to change user options or unsubscribe:
https://lists.sourceforge.net/lists/listinfo/snort-users
Snort-users list archive:
http://www.geocrawler.com/redir-sf.php3?list=snort-users
|