DansGuardian Documentation Wiki

You are here: Main Index » bypass_hash_usage


|

Wiki Information

Differences

This shows you the differences between the selected revision and the current version of the page.

bypass_hash_usage 2009/04/29 14:30 bypass_hash_usage 2009/04/29 21:02 current
Line 19: Line 19:
  * a complete transaction (login, buy, etc.)   * a complete transaction (login, buy, etc.)
A couple of years ago only the topmost URL was likely to be denied, so unlocking only one particular URL like this used to work pretty well. But typical web usage has evolved so that now one click can result in tens of URL accesses, several of which may be denied even though they're deep inside a chain of requests. So in some environments the DansGuardian "bypass" feature as originally implemented is no longer viewed as all that useful. A couple of years ago only the topmost URL was likely to be denied, so unlocking only one particular URL like this used to work pretty well. But typical web usage has evolved so that now one click can result in tens of URL accesses, several of which may be denied even though they're deep inside a chain of requests. So in some environments the DansGuardian "bypass" feature as originally implemented is no longer viewed as all that useful.
-==== A Simpler Way ====+==== A Newer/Simpler Way ====
Rather than bypassing DansGuardian by using some variant on the "hash" method as discussed below, it may be simplest to just [[Bypassing DansGuardian#Requiring Password For Bypass - Details|use "multiple filter groups" to provide password-protected bypass functionality.]] This simpler way is especially relevant if you want either detailed logging or a different password for each user, as those additional requirements complicate use of the old bypass hash method. Once you get 'multiple filter groups' set up, likely you will find them very useful for many other purposes too. In other words you can think of being able to spread the initial setup cost of 'multiple filter groups' over several features besides just bypassing DansGuardian. Rather than bypassing DansGuardian by using some variant on the "hash" method as discussed below, it may be simplest to just [[Bypassing DansGuardian#Requiring Password For Bypass - Details|use "multiple filter groups" to provide password-protected bypass functionality.]] This simpler way is especially relevant if you want either detailed logging or a different password for each user, as those additional requirements complicate use of the old bypass hash method. Once you get 'multiple filter groups' set up, likely you will find them very useful for many other purposes too. In other words you can think of being able to spread the initial setup cost of 'multiple filter groups' over several features besides just bypassing DansGuardian.