On Fri, Jan 20, 2012 at 11:28, Ben Scott <[email protected]> wrote: > On Fri, Jan 20, 2012 at 2:24 PM, Ben Scott <[email protected]> wrote: >>>> So, I'm to whitelist the site every time I visit it. How exactly >>>> does that improve my security? >>> >>> If the site has been hacked, I can see what sites they're calling, and >>> between NoScript and Rquest Policy I've found a few sites that had >>> unexpected content that didn't get executed. >> >> (I'm off to check out Request Policy now...) > > Having checked it out, it looks useful (thanks!), but as near as I > can tell, as long as one doesn't whitelist excessively permissively, I > still don't see how whitelisting manually every time I visit a site > helps. For example, if I want to say that en.wikipedia.org is allowed > to request from toolserver.org, how does doing that manually at every > visit improve things over allowing it permanently? > > Or am I misunderstanding you?
I doubt you're misunderstanding me - I'm just what others would call a paranoid freak. I only ever give temporary permissions, except to an extremely narrow set of sites. It's sometimes a bit annoying, but to me it's worth the hassle. Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
