├── INSTALL.sh ├── README.md ├── anonym8.desktop ├── anonym8.png ├── etc └── anonym8.sh ├── opt └── anonym8 │ ├── Anons.jpeg │ └── anonym8-gui ├── polipo └── config ├── privoxy └── config ├── tor └── torrc └── usr ├── anOFF ├── anON └── anonym8 /INSTALL.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # Install script for anonym8 3 | 4 | export BLUE='\033[1;94m' 5 | export GREEN='\033[1;92m' 6 | export RED='\033[1;91m' 7 | export RESETCOLOR='\033[1;00m' 8 | 9 | echo -e "This script will install anonym8 on your computer...\n" 10 | sleep 1 11 | cp -Rf opt/anonym8 /opt/anonym8 12 | sleep 1 13 | cp -Rf anonym8.desktop /usr/share/applications 14 | sleep 1 15 | cp -Rf etc/anonym8.sh /etc/init.d/anonym8.sh 16 | sleep 1 17 | cp -Rf usr/anonym8 /usr/bin/anonym8 18 | sleep 1 19 | cp -Rf usr/anON /usr/bin/anON 20 | sleep 1 21 | cp -Rf usr/anOFF /usr/bin/anOFF 22 | sleep 1 23 | apt-get install tor macchanger resolvconf dnsmasq polipo privoxy tor-arm libnotify-bin curl bleachbit 24 | sleep 1 25 | cp -Rf polipo/config /etc/polipo/config 26 | sleep 1 27 | cp -Rf privoxy/config /etc/privoxy/config 28 | sleep 1 29 | cp -Rf tor/torrc /etc/tor/torrc 30 | sleep 1 31 | chmod +x /etc/init.d/anonym8.sh /usr/bin/anonym8 /usr/bin/anON /usr/bin/anOFF /opt/anonym8/anonym8-gui 32 | sleep 1 33 | echo -e "\n anonym8 (v 1.0) Usage Ex:\n 34 | $RED anON$BLUE =>$GREEN automated protection [ON] 35 | $RED anOFF$BLUE =>$GREEN automated protection$RED [OFF]\n 36 | $RED ADVANCED COMMANDS LIST:\n 37 | $RED┌──[$GREEN$USER$RED@$BLUE`hostname`$RED]─[$GREEN$PWD$RED] 38 | $RED└──╼ $GREEN"anonym8" $RED{$GREEN"start"$RED|$GREEN"stop"$RED|$GREEN"change"$RED|$GREEN"status..."$RED}\n 39 | $BLUE----[ Tor Tunneling related features ]---- 40 | $RED anonym8 start$BLUE =>$GREEN Start Tor Tunneling 41 | $RED anonym8 stop$BLUE =>$GREEN Stop Tor Tunneling 42 | $RED anonym8 change$BLUE =>$GREEN Changes identity restarting TOR 43 | $RED anonym8 status$BLUE =>$GREEN Tor Tunneling Status\n 44 | $BLUE----[ IP related features ]---- 45 | $RED anonym8 status_ip$BLUE =>$GREEN IP status\n 46 | $BLUE----[ I2P related features ]---- 47 | $RED anonym8 start_i2p$BLUE =>$GREEN Start i2p services 48 | $RED anonym8 stop_i2p$BLUE =>$GREEN Stop i2p services 49 | $RED anonym8 status_i2p$BLUE =>$GREEN i2p status\n 50 | $BLUE----[ privoxy related features ]---- 51 | $RED anonym8 start_privoxy$BLUE =>$GREEN Start privoxy services 52 | $RED anonym8 stop_privoxy$BLUE =>$GREEN Stop privoxy services 53 | $RED anonym8 status_privoxy$BLUE =>$GREEN privoxy status\n 54 | $BLUE----[ polipo related features ]---- 55 | $RED anonym8 start_polipo$BLUE =>$GREEN Start polipo services 56 | $RED anonym8 stop_polipo$BLUE =>$GREEN Stop polipo services 57 | $RED anonym8 status_polipo$BLUE =>$GREEN Polipo status\n 58 | $BLUE----[ macchanger related features ]---- 59 | $RED anonym8 start_mac$BLUE =>$GREEN Start macchanger services 60 | $RED anonym8 stop_mac$BLUE =>$GREEN Stop macchanger services 61 | $RED anonym8 status_mac$BLUE =>$GREEN macchanger status\n 62 | $BLUE----[ arm related features ]---- 63 | $RED anonym8 start_arm$BLUE =>$GREEN Start Monitoring Anonymizing Relay (arm)\n 64 | $BLUE----[ wipe related features ]---- 65 | $RED anonym8 wipe$BLUE =>$GREEN cache, RAM & swap-space cleaner\n 66 | $BLUE----[ hostname related features ]---- 67 | $RED anonym8 change_hostname$BLUE =>$GREEN Randomly Spoofing Hostname 68 | $RED anonym8 restore_hostname$BLUE =>$GREEN Restore Default Hostname 69 | $RED anonym8 status_hostname$BLUE =>$GREEN Show Current Hostname\n 70 | 71 | $RESETCOLOR" 72 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2 | [EN] 3 | @HiroshimanRise 4 | #anonym8 (Privacy Friend) 5 | 6 | #Transparent Proxy through TOR, I2P, Privoxy, Polipo and modify DNS, for a simple and better privacy and security; 7 | #Include Anonymizing Relay Monitor (arm), macchanger, hostname and wipe (Cleans ram/cache & swap-space) features. 8 | #Tested on #Debian #Kali #Parrot 9 | #to use the graphical interface, you'll need to install separately GTKdialog and libvte.so.9 and i2p 10 | 11 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 12 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 13 | 14 | Script requirements are: 15 | 16 | -Tor 17 | -macchanger 18 | -resolvconf 19 | -dnsmasq 20 | -polipo 21 | -privoxy 22 | -arm 23 | -libnotify 24 | -curl 25 | -bleachbit 26 | 27 | they'll be automatically installed. 28 | 29 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 30 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 31 | 32 | Open a root terminal and type: 33 | 34 | cd anonym8_directory I.Ex: cd /home/toto/Desktop/anonym8-master 35 | 36 | then: 37 | chmod +x INSTALL.sh 38 | 39 | and: 40 | bash INSTALL.sh 41 | 42 | you're done! 43 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 44 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 45 | 46 | For more security, use Firefox! 47 | 48 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 49 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 50 | 51 | here's some useful Firefox add on: 52 | 53 | profil manager => https://ftp.mozilla.org/pub/utilities/profilemanager/1.0/ 54 | random agent spoofer => https://addons.mozilla.org/en-US/firefox/addon/random-agent-spoofer/ 55 | no script => https://addons.mozilla.org/en-US/firefox/addon/noscript/ 56 | ublock origin => https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/ 57 | HTTPS everywhere => https://addons.mozilla.org/fr/firefox/addon/https-everywhere/ 58 | 59 | Reboot your system and enjoy! 60 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 61 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 62 | 63 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 64 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 65 | [FR] 66 | @HiroshimanRise 67 | #anonym8 (Privacy Friend) 68 | 69 | Établi un tunnel proxy transparent à travers Tor, I2P, Privoxy, Polipo et modifie les DNS; 70 | Inclue la fonction Anonymizing Relay Monitor (arm), macchanger et wipe (effacement de la ram et du swap); 71 | Testé sous #Debian #Kali #Parrot; 72 | Je vous encourage à améliorer et partager ce soft pour la liberté et le respect de la vie privée. 73 | Pour profiter de l'interface graphique, il vous faudra installer séparément GTKdialog ainsi que la libvte.so.9 ainsi que le paquet i2p 74 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 75 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 76 | 77 | Pour le bon fonctionnement du script, les paquets suivants seront automatiquement installés: 78 | 79 | -Tor 80 | -macchanger 81 | -resolvconf 82 | -dnsmasq 83 | -polipo 84 | -privoxy 85 | -arm 86 | -libnotify 87 | -curl 88 | -bleachbit 89 | 90 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 91 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 92 | 93 | Pour l'installation, ouvrez un terminal root et tapez: 94 | 95 | cd chemin_du_dossier_anonym8-master ex: cd /home/toto/Desktop/anonym8-master 96 | 97 | puis: 98 | chmod +x INSTALL.sh 99 | 100 | puis: 101 | bash INSTALL.sh 102 | 103 | le script va maintenant installer les composants nécessaires, répondez juste par oui ou non aux éventuelles questions. 104 | 105 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 106 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 107 | 108 | Pour plus de sécurité et par souci d'éthique, je vous recommande d'utiliser Firefox. 109 | 110 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 111 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 112 | 113 | Voici une liste d'add on Firefox pour garantir une sécurité minimum (vous êtes libre de vos choix): 114 | 115 | -profil manager => https://ftp.mozilla.org/pub/utilities/profilemanager/1.0/ 116 | -random agent spoofer => https://addons.mozilla.org/en-US/firefox/addon/random-agent-spoofer/ 117 | -no script => https://addons.mozilla.org/en-US/firefox/addon/noscript/ 118 | -ublock origin => https://addons.mozilla.org/en-US/firefox/addon/ublock-origin/ 119 | -HTTPS everywhere => https://addons.mozilla.org/fr/firefox/addon/https-everywhere/ 120 | 121 | Rebootez votre systême, vous êtes désormais prêt(e)s ? affronter la jungle des interwebs en mode "survival_horror", enjoy! 122 | 123 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 124 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 125 | -------------------------------------------------------------------------------- /anonym8.desktop: -------------------------------------------------------------------------------- 1 | [Desktop Entry] 2 | Type=Application 3 | Version=1.0 4 | Name=anonym8-gui 5 | GenericName=anonym8-gui 6 | Comment=Advanced ID Spoofer 7 | Keywords=Spoof 8 | Icon=/opt/anonym8/Anons.jpeg 9 | TryExec=/opt/anonym8/anonym8-gui 10 | Exec=/opt/anonym8/anonym8-gui 11 | Categories=System;Monitor; 12 | X-GNOME-Autostart-Delay=30 13 | StartupNotify=true 14 | -------------------------------------------------------------------------------- /anonym8.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/HiroshiManRise/anonym8/89b0959cbfdb486735091a4a2cdfd7eb53c3ebeb/anonym8.png -------------------------------------------------------------------------------- /etc/anonym8.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # This code is based on anonsurf by #ParrotSec & AnonSecTunnel by cysec666 #AnonSec 4 | # implementing TOR, I2P, Privoxy, Polipo, arm-tor and MacChanger for a simple and better privacy and security. 5 | 6 | # Coded by Hiroshiman 7 | # Twitter: @HiroshimanRise 8 | 9 | ### BEGIN INIT INFO 10 | # Provides: Anonym8 11 | # Short-Description: Transparent Proxy through TOR, I2P, Privoxy, Polipo + arm-tor and MacChanger features 12 | ### END INIT INFO 13 | 14 | # Thanks to: 15 | # cysec666 '@cysec666' 16 | # Lorenzo 'EclipseSpark' Faletra 17 | # Lisetta 'Sheireen' Ferrero 18 | # Francesco 'mibofra'/'Eli Aran'/'SimpleSmibs' Bonanno 19 | 20 | # Feel free to edit and share this script ;) 21 | 22 | export BLUE='\033[1;94m' 23 | export GREEN='\033[1;92m' 24 | export RED='\033[1;91m' 25 | export RESETCOLOR='\033[1;00m' 26 | export notify 27 | 28 | # Destinations you don't want routed through Tor 29 | TOR_EXCLUDE="192.168.0.0/16 172.16.0.0/12 10.0.0.0/8" 30 | 31 | # The UID Tor runs as 32 | # change it if, starting tor, the command 'ps -e | grep tor' returns a different UID 33 | TOR_UID="debian-tor" 34 | 35 | # Tor's TransPort 36 | TOR_PORT="9040" 37 | 38 | ### FUNCTIONS #### 39 | 40 | ## notify #### 41 | function notify { 42 | if [ -e /usr/bin/notify-send ]; then 43 | /usr/bin/notify-send "anonym8" "$1" 44 | fi 45 | } 46 | 47 | ## hostname #### 48 | 49 | # change #### 50 | function change_hostname { 51 | cp /etc/hostname /etc/hostname.bak 52 | cp /etc/hosts /etc/hosts.bak 53 | sudo service network-manager stop 54 | CURRENT_HOSTNAME=$(hostname) 55 | dhclient -r 56 | rm -f /var/lib/dhcp/dhclient* 57 | RANDOM_HOSTNAME=$(shuf -n 1 /etc/dictionaries-common/words | sed -r 's/[^a-zA-Z]//g' | awk '{print tolower($0)}') 58 | NEW_HOSTNAME=${1:-$RANDOM_HOSTNAME} 59 | echo "$NEW_HOSTNAME" > /etc/hostname 60 | sed -i 's/127.0.1.1.*/127.0.1.1\t'"$NEW_HOSTNAME"'/g' /etc/hosts 61 | if [ -f "$HOME/.Xauthority" ] ; then 62 | su "$SUDO_USER" -c "xauth -n list | grep -v $CURRENT_HOSTNAME | cut -f1 -d\ | xargs -i xauth remove {}" 63 | su "$SUDO_USER" -c "xauth add $(xauth -n list | tail -1 | sed 's/^.*\//'$NEW_HOSTNAME'\//g')" 64 | echo " * X authority file updated" 65 | fi 66 | sudo service network-manager start 67 | sleep 5 68 | echo -e -n "\n$GREEN*$BLUE New Hostname: $GREEN" 69 | hostname 70 | notify "hostname spoofed" 71 | } 72 | 73 | # restore #### 74 | function restore_hostname { 75 | sudo service network-manager stop 76 | dhclient -r 77 | rm -f /var/lib/dhcp/dhclient* 78 | if [ -e /etc/hostname.bak ]; then 79 | rm /etc/hostname 80 | cp /etc/hostname.bak /etc/hostname 81 | fi 82 | if [ -e /etc/hosts.bak ]; then 83 | rm /etc/hosts 84 | cp /etc/hosts.bak /etc/hosts 85 | fi 86 | sudo service network-manager start 87 | sleep 5 88 | echo -e -n "\n$GREEN*$BLUE Restored Hostname: $GREEN" 89 | hostname 90 | notify "hostname restored" 91 | } 92 | 93 | # status #### 94 | function status_hostname { 95 | echo -e -n "\n$GREEN*$BLUE Current Hostname: $GREEN" 96 | hostname 97 | } 98 | 99 | ## wipe #### 100 | function wipe { 101 | echo -e "\n$GREEN*$BLUE now wiping cache, ram, & swap-space...\n" 102 | sync; echo 3 > /proc/sys/vm/drop_caches 103 | swapoff -a && swapon -a 104 | sleep 1 105 | echo -e "$GREEN*$BLUE Cache, ram & swap-space$GREEN [CLEANED]"$RESETCOLOR 106 | notify "Cache, ram & swap-space cleaned!" 107 | } 108 | 109 | ## ARM #### 110 | function start_arm { 111 | echo -e "\n$GREEN*$BLUE Starting Anonymizing Relay Monitor (arm)..."$RESETCOLOR 112 | xhost + 113 | sleep 1 114 | DISPLAY=:0.0 gnome-terminal -e "sudo arm" 115 | sleep 1 116 | } 117 | 118 | ## PRIVOXY #### 119 | 120 | # START #### 121 | function start_privoxy { 122 | echo -e "\n$GREEN*$BLUE Starting Privoxy Service...\n"$RESETCOLOR 123 | sleep 1 124 | sudo service privoxy start 125 | echo -e "$GREEN*$BLUE Privoxy Service$GREEN [ON]"$RESETCOLOR 126 | sleep 1 127 | notify "Privoxy daemon ON" 128 | } 129 | 130 | # STOP #### 131 | function stop_privoxy { 132 | echo -e "\n$GREEN*$BLUE Stopping Privoxy Service...\n"$RESETCOLOR 133 | sleep 1 134 | sudo service privoxy stop 135 | sleep 1 136 | echo -e "$GREEN*$BLUE Privoxy Service$RED [OFF]"$RESETCOLOR 137 | sleep 1 138 | notify "Privoxy daemon OFF" 139 | } 140 | 141 | # STATUS #### 142 | function status_privoxy { 143 | echo -e "\n$GREEN*$BLUE Privoxy Service Status:\n"$RESETCOLOR 144 | sleep 1 145 | sudo service privoxy status 146 | sleep 1 147 | } 148 | 149 | ## POLIPO #### 150 | 151 | # START #### 152 | function start_polipo { 153 | echo -e "\n$GREEN*$BLUE Starting Polipo Service...\n"$RESETCOLOR 154 | sleep 1 155 | sudo service polipo start 156 | echo -e "$GREEN*$BLUE Polipo Service$GREEN [ON]"$RESETCOLOR 157 | sleep 1 158 | notify "Polipo daemon ON" 159 | } 160 | 161 | # STOP #### 162 | function stop_polipo { 163 | echo -e "\n$GREEN*$BLUE Stopping Polipo Service...\n"$RESETCOLOR 164 | sleep 1 165 | sudo service polipo stop 166 | sleep 1 167 | echo -e "$GREEN*$BLUE Polipo Service$RED [OFF]"$RESETCOLOR 168 | sleep 1 169 | notify "Polipo daemon OFF" 170 | } 171 | 172 | # STATUS #### 173 | function status_polipo { 174 | echo -e "\n$GREEN*$BLUE Polipo Service Status:\n"$RESETCOLOR 175 | sleep 1 176 | sudo service polipo status 177 | sleep 1 178 | } 179 | 180 | ## MACCHANGER #### 181 | 182 | # START #### 183 | function start_mac { 184 | echo -e "\n$GREEN*$BLUE Spoofing Mac Address...\n" 185 | sudo service network-manager stop 186 | sleep 1 187 | echo -e "$GREEN*$BLUE wlan0 MAC address:\n"$GREEN 188 | sleep 1 189 | sudo ifconfig wlan0 down 190 | sleep 1 191 | sudo macchanger -a wlan0 192 | sleep 1 193 | sudo ifconfig wlan0 up 194 | sleep 1 195 | sudo service network-manager start 196 | echo -e "\n$GREEN*$BLUE Mac Address Spoofing$GREEN [ON]"$RESETCOLOR 197 | sleep 1 198 | notify "Mac Address Spoofing ON" 199 | } 200 | 201 | # STOP #### 202 | function stop_mac { 203 | echo -e "\n$GREEN*$BLUE Restoring Mac Address...\n" 204 | sudo service network-manager stop 205 | sleep 1 206 | echo -e "$GREEN*$BLUE wlan0 MAC address:\n"$GREEN 207 | sleep 1 208 | sudo ifconfig wlan0 down 209 | sleep 1 210 | sudo macchanger -p wlan0 211 | sleep 1 212 | sudo ifconfig wlan0 up 213 | sleep 1 214 | sudo service network-manager start 215 | sleep 1 216 | echo -e "\n$GREEN*$BLUE Mac Address Spoofing$RED [OFF]"$RESETCOLOR 217 | sleep 1 218 | notify "Mac Address Spoofing OFF" 219 | } 220 | 221 | # STATUS #### 222 | function status_mac { 223 | echo -e "\n$GREEN*$BLUE Mac Adress Status:\n" 224 | sleep 1 225 | echo -e "$GREEN*$BLUE wlan0 Mac Adress:\n"$GREEN 226 | sleep 1 227 | macchanger wlan0 228 | sleep 1 229 | } 230 | 231 | ## I2P #### 232 | 233 | # START #### 234 | function start_i2p { 235 | echo -e "\n$GREEN*$BLUE starting I2P service\n"$RESETCOLOR 236 | anonym8 stop 237 | sleep 4 238 | cp /etc/resolv.conf /etc/resolv.conf.bak 239 | touch /etc/resolv.conf 240 | echo -e 'nameserver 127.0.0.1\nnameserver 213.73.91.35\nnameserver 87.118.100.175' > /etc/resolv.conf 241 | echo -e "\n$GREEN*$BLUE resolv.conf: Chaos Computer Club & German Privacy Foundation$GREEN [ACTIVATED]\n"$RESETCOLOR 242 | sleep 1 243 | sudo -u i2psvc i2prouter start 244 | sleep 1 245 | echo -e "$GREEN*$BLUE I2P Service$GREEN [ON]"$RESETCOLOR 246 | sleep 1 247 | notify "I2P Daemon ON" 248 | } 249 | 250 | # STOP #### 251 | function stop_i2p { 252 | echo -e "\n$GREEN*$BLUE stop I2P service\n"$GREEN 253 | sleep 1 254 | sudo -u i2psvc i2prouter stop 255 | if [ -e /etc/resolv.conf.bak ]; then 256 | rm /etc/resolv.conf 257 | cp /etc/resolv.conf.bak /etc/resolv.conf 258 | fi 259 | sleep 1 260 | echo -e "\n$GREEN*$BLUE I2P Service$RED [OFF]"$RESETCOLOR 261 | sleep 1 262 | notify "I2P Daemon OFF" 263 | } 264 | 265 | # STATUS #### 266 | function status_i2p { 267 | echo -e "\n$GREEN*$BLUE I2P Service Status:\n"$GREEN 268 | sleep 1 269 | sudo -u i2psvc i2prouter status 270 | sleep 1 271 | } 272 | 273 | ## IP #### 274 | function status_ip { 275 | echo -e -n "\n$GREEN*$BLUE Current Proxy IP: $GREEN" 276 | curl icanhazip.com 277 | sleep 1 278 | echo -e "\n$GREEN*$BLUE Current Tor IP:\n"$GREEN 279 | sleep 1 280 | curl ipinfo.io/ 281 | sleep 1 282 | } 283 | 284 | ## START #### 285 | function start { 286 | # Make sure only root can run this script 287 | if [ $(id -u) -ne 0 ]; then 288 | echo -e "\n$GREEN[$RED!$GREEN]$RED This script must be run as root$RESETCOLOR" >&2 289 | exit 1 290 | fi 291 | 292 | echo -e "\n$GREEN*$BLUE Killing dangerous applications and cleaning some cache elements...\n"$RESETCOLOR 293 | sleep 1 294 | killall -q chrome dropbox iceweasel skype icedove thunderbird firefox-esr firefox chromium xchat transmission kvirc pidgin hexchat # feel free to add your own internet connected app 295 | sleep 1 296 | bleachbit -c adobe_reader.cache chromium.cache chromium.current_session chromium.history elinks.history emesene.cache epiphany.cache firefox.url_history flash.cache flash.cookies google_chrome.cache google_chrome.history links2.history opera.cache opera.search_history opera.url_history &> /dev/null 297 | sleep 1 298 | echo -e "$GREEN*$BLUE Dangerous applications$GREEN [KILLED]\n" 299 | sleep 1 300 | if [ ! -e /var/run/tor/tor.pid ]; then 301 | echo -e "$GREEN*$BLUE starting Tor...\n" >&2 302 | sleep 1 303 | service resolvconf stop 304 | killall dnsmasq 305 | sleep 2 306 | service tor start 307 | sleep 6 308 | fi 309 | if ! [ -f /etc/network/iptables.rules ]; then 310 | iptables-save > /etc/network/iptables.rules 311 | echo -e "$GREEN*$BLUE Saving iptables.rules...$RESETCOLOR\n" 312 | sleep 2 313 | fi 314 | iptables -F 315 | iptables -t nat -F 316 | echo -e "$GREEN*$BLUE iptables.rules$GREEN [SAVED]\n" 317 | sleep 2 318 | echo -e "$GREEN*$BLUE Saving resolv.conf...\n" 319 | cp /etc/resolv.conf /etc/resolv.conf.bak 320 | touch /etc/resolv.conf 321 | sleep 2 322 | echo -e "$GREEN*$BLUE resolv.conf$GREEN [SAVED]\n" 323 | sleep 2 324 | echo -e "$GREEN*$BLUE Modifying DNS...\n" 325 | sleep 2 326 | echo -e 'nameserver 127.0.0.1\nnameserver 213.73.91.35\nnameserver 87.118.100.175' > /etc/resolv.conf 327 | echo -e "$GREEN*$BLUE resolv.conf: Chaos Computer Club & German Privacy Foundation DNS$GREEN [ACTIVATED]\n"$RESETCOLOR 328 | sleep 2 329 | 330 | # set iptables nat 331 | iptables -t nat -A OUTPUT -m owner --uid-owner $TOR_UID -j RETURN 332 | iptables -t nat -A OUTPUT -p udp --dport 53 -j REDIRECT --to-ports 53 333 | iptables -t nat -A OUTPUT -p tcp --dport 53 -j REDIRECT --to-ports 53 334 | iptables -t nat -A OUTPUT -p udp -m owner --uid-owner $TOR_UID -m udp --dport 53 -j REDIRECT --to-ports 53 335 | 336 | # resolve .onion domains mapping 10.192.0.0/10 address space 337 | iptables -t nat -A OUTPUT -p tcp -d 10.192.0.0/10 -j REDIRECT --to-ports 9040 338 | iptables -t nat -A OUTPUT -p udp -d 10.192.0.0/10 -j REDIRECT --to-ports 9040 339 | 340 | # exclude local addresses 341 | for NET in $TOR_EXCLUDE 127.0.0.0/9 127.128.0.0/10; do 342 | iptables -t nat -A OUTPUT -d $NET -j RETURN 343 | done 344 | 345 | # redirect all other output through TOR 346 | iptables -t nat -A OUTPUT -p tcp --syn -j REDIRECT --to-ports $TOR_PORT 347 | iptables -t nat -A OUTPUT -p udp -j REDIRECT --to-ports $TOR_PORT 348 | iptables -t nat -A OUTPUT -p icmp -j REDIRECT --to-ports $TOR_PORT 349 | 350 | # accept already established connections 351 | iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT 352 | 353 | # exclude local addresses 354 | for NET in $TOR_EXCLUDE 127.0.0.0/8; do 355 | iptables -A OUTPUT -d $NET -j ACCEPT 356 | done 357 | 358 | # allow only tor output 359 | iptables -A OUTPUT -m owner --uid-owner $TOR_UID -j ACCEPT 360 | iptables -A OUTPUT -j REJECT 361 | 362 | echo -e "$GREEN*$BLUE Tor Tunneling$GREEN [ON]"$RESETCOLOR 363 | sleep 1 364 | notify "Tor Tunneling ON" 365 | } 366 | 367 | ## STOP #### 368 | function stop { 369 | # Make sure only root can run our script 370 | if [ $(id -u) -ne 0 ]; then 371 | echo -e "\n$GREEN[$RED!$GREEN]$RED This script must be run as root\n" >&2 372 | exit 1 373 | fi 374 | echo -e "\n$GREEN*$BLUE killing dangerous applications and cleaning some cache elements...\n"$RESETCOLOR 375 | killall -q chrome dropbox iceweasel skype icedove thunderbird firefox-esr firefox chromium xchat transmission kvirc pidgin hexchat # feel free to add your own internet connected app 376 | sleep 1 377 | bleachbit -c adobe_reader.cache chromium.cache chromium.current_session chromium.history elinks.history emesene.cache epiphany.cache firefox.url_history flash.cache flash.cookies google_chrome.cache google_chrome.history links2.history opera.cache opera.search_history opera.url_history &> /dev/null 378 | sleep 1 379 | echo -e "$GREEN*$BLUE Dangerous applications$GREEN [KILLED]\n" 380 | sleep 1 381 | iptables -F 382 | iptables -t nat -F 383 | sleep 2 384 | echo -e "$GREEN*$BLUE Restoring iptables.rules...$RESETCOLOR\n" 385 | sleep 2 386 | if [ -f /etc/network/iptables.rules ]; then 387 | iptables-restore < /etc/network/iptables.rules 388 | rm /etc/network/iptables.rules 389 | sleep 1 390 | echo -e "$GREEN*$BLUE iptables.rules$GREEN [RESTORED]\n" 391 | sleep 2 392 | fi 393 | echo -e "$GREEN*$BLUE Restoring resolv.conf...\n" 394 | if [ -e /etc/resolv.conf.bak ]; then 395 | rm /etc/resolv.conf 396 | cp /etc/resolv.conf.bak /etc/resolv.conf 397 | fi 398 | echo -e "$GREEN*$BLUE resolv.conf$GREEN [RESTORED]\n" 399 | sleep 2 400 | echo -e "$GREEN*$BLUE Stopping Tor...\n" 401 | service tor stop 402 | sleep 4 403 | echo -e "$GREEN*$BLUE Restarting Services...\n" 404 | service resolvconf start 405 | service dnsmasq start 406 | echo -e "$GREEN*$BLUE Services Successfully$GREEN [RELOADED]\n" 407 | sleep 3 408 | echo -e "$GREEN*$BLUE Tor Tunneling$RED [OFF]"$RESETCOLOR 409 | sleep 1 410 | notify "Tor Tunneling OFF" 411 | } 412 | 413 | ## CHANGE #### 414 | function change { 415 | echo -e "\n$GREEN*$BLUE Changing Tor Relay...\n"$RESETCOLOR 416 | service tor reload 417 | sleep 4 418 | echo -e "$GREEN*$BLUE Change Identity$GREEN [SUCCESS]\n" 419 | sleep 1 420 | echo -e -n "$GREEN*$BLUE Current Proxy IP: $GREEN" 421 | curl icanhazip.com 422 | sleep 1 423 | echo -e "\n$GREEN*$BLUE Current Tor IP:\n"$GREEN 424 | sleep 1 425 | curl ipinfo.io/ 426 | sleep 1 427 | notify "Tor Relay Changed" 428 | } 429 | 430 | ## STATUS #### 431 | function status { 432 | echo -e "\n$GREEN*$BLUE Tor Tunneling Status:\n"$RESETCOLOR 433 | service tor status 434 | } 435 | 436 | ### CASE #### 437 | 438 | case "$1" in 439 | status_hostname) 440 | status_hostname 441 | ;; 442 | change_hostname) 443 | change_hostname 444 | ;; 445 | restore_hostname) 446 | restore_hostname 447 | ;; 448 | start) 449 | start 450 | ;; 451 | stop) 452 | stop 453 | ;; 454 | change) 455 | change 456 | ;; 457 | status) 458 | status 459 | ;; 460 | status_ip) 461 | status_ip 462 | ;; 463 | start_i2p) 464 | start_i2p 465 | ;; 466 | stop_i2p) 467 | stop_i2p 468 | ;; 469 | status_i2p) 470 | status_i2p 471 | ;; 472 | start_privoxy) 473 | start_privoxy 474 | ;; 475 | stop_privoxy) 476 | stop_privoxy 477 | ;; 478 | status_privoxy) 479 | status_privoxy 480 | ;; 481 | start_polipo) 482 | start_polipo 483 | ;; 484 | stop_polipo) 485 | stop_polipo 486 | ;; 487 | status_polipo) 488 | status_polipo 489 | ;; 490 | start_mac) 491 | start_mac 492 | ;; 493 | stop_mac) 494 | stop_mac 495 | ;; 496 | status_mac) 497 | status_mac 498 | ;; 499 | start_arm) 500 | start_arm 501 | ;; 502 | wipe) 503 | wipe 504 | ;; 505 | *) 506 | # USAGE #### 507 | echo -e " anonym8 (v 1.0) Usage Ex:\n 508 | $RED anON$BLUE =>$GREEN automated protection [ON] 509 | $RED anOFF$BLUE =>$GREEN automated protection$RED [OFF]\n 510 | $RED ADVANCED COMMANDS LIST:\n 511 | $RED┌──[$GREEN$USER$RED@$BLUE`hostname`$RED]─[$GREEN$PWD$RED] 512 | $RED└──╼ $GREEN"anonym8" $RED{$GREEN"start"$RED|$GREEN"stop"$RED|$GREEN"change"$RED|$GREEN"status..."$RED}\n 513 | $BLUE----[ Tor Tunneling related features ]---- 514 | $RED anonym8 start$BLUE =>$GREEN Start Tor Tunneling 515 | $RED anonym8 stop$BLUE =>$GREEN Stop Tor Tunneling 516 | $RED anonym8 change$BLUE =>$GREEN Changes identity restarting TOR 517 | $RED anonym8 status$BLUE =>$GREEN Tor Tunneling Status\n 518 | $BLUE----[ IP related features ]---- 519 | $RED anonym8 status_ip$BLUE =>$GREEN IP status\n 520 | $BLUE----[ I2P related features ]---- 521 | $RED anonym8 start_i2p$BLUE =>$GREEN Start i2p services 522 | $RED anonym8 stop_i2p$BLUE =>$GREEN Stop i2p services 523 | $RED anonym8 status_i2p$BLUE =>$GREEN i2p status\n 524 | $BLUE----[ privoxy related features ]---- 525 | $RED anonym8 start_privoxy$BLUE =>$GREEN Start privoxy services 526 | $RED anonym8 stop_privoxy$BLUE =>$GREEN Stop privoxy services 527 | $RED anonym8 status_privoxy$BLUE =>$GREEN privoxy status\n 528 | $BLUE----[ polipo related features ]---- 529 | $RED anonym8 start_polipo$BLUE =>$GREEN Start polipo services 530 | $RED anonym8 stop_polipo$BLUE =>$GREEN Stop polipo services 531 | $RED anonym8 status_polipo$BLUE =>$GREEN Polipo status\n 532 | $BLUE----[ macchanger related features ]---- 533 | $RED anonym8 start_mac$BLUE =>$GREEN Start macchanger services 534 | $RED anonym8 stop_mac$BLUE =>$GREEN Stop macchanger services 535 | $RED anonym8 status_mac$BLUE =>$GREEN macchanger status\n 536 | $BLUE----[ arm related features ]---- 537 | $RED anonym8 start_arm$BLUE =>$GREEN Start Monitoring Anonymizing Relay (arm)\n 538 | $BLUE----[ wipe related features ]---- 539 | $RED anonym8 wipe$BLUE =>$GREEN cache, RAM & swap-space cleaner\n 540 | $BLUE----[ hostname related features ]---- 541 | $RED anonym8 change_hostname$BLUE =>$GREEN Randomly Spoofing Hostname 542 | $RED anonym8 restore_hostname$BLUE =>$GREEN Restore Default Hostname 543 | $RED anonym8 status_hostname$BLUE =>$GREEN Show Current Hostname\n 544 | 545 | $RESETCOLOR" >&2 546 | exit 1 547 | ;; 548 | esac 549 | 550 | echo -e $RESETCOLOR 551 | exit 0 552 | -------------------------------------------------------------------------------- /opt/anonym8/Anons.jpeg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/HiroshiManRise/anonym8/89b0959cbfdb486735091a4a2cdfd7eb53c3ebeb/opt/anonym8/Anons.jpeg -------------------------------------------------------------------------------- /opt/anonym8/anonym8-gui: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | # This code is based on anonsurf by #ParrotSec & AnonSecTunnel by cysec666 #AnonSec 4 | 5 | # Coded by Hiroshiman 6 | # Twitter: @HiroshimanRise 7 | 8 | ### BEGIN INIT INFO 9 | # Provides: Anonym8 10 | # Short-Description: Transparent Proxy through TOR, Privoxy, Polipo + MacChanger features, for a simple and better privacy and security. 11 | ### END INIT INFO 12 | 13 | # Thanks to: 14 | # cysec666 '@cysec666' 15 | # Lorenzo 'EclipseSpark' Faletra 16 | # Lisetta 'Sheireen' Ferrero 17 | # Francesco 'mibofra'/'Eli Aran'/'SimpleSmibs' Bonanno 18 | 19 | # Feel free to edit and share this script ;) 20 | 21 | tmp_file=/tmp/code_terminal 22 | 23 | #anonym8 24 | start='echo "anON" > /tmp/code_terminal' 25 | stop='echo "anOFF" > /tmp/code_terminal' 26 | change='echo "anonym8 change" > /tmp/code_terminal' 27 | 28 | #macchanger 29 | start_mac='echo "anonym8 start_mac" > /tmp/code_terminal' 30 | stop_mac='echo "anonym8 stop_mac" > /tmp/code_terminal' 31 | status_mac='echo "anonym8 status_mac" > /tmp/code_terminal' 32 | 33 | #ip 34 | status_ip='echo "anonym8 status_ip" > /tmp/code_terminal' 35 | 36 | #tor 37 | start_tor='echo "anonym8 start" > /tmp/code_terminal' 38 | stop_tor='echo "anonym8 stop" > /tmp/code_terminal' 39 | status_tor='echo "anonym8 status" > /tmp/code_terminal' 40 | 41 | #privoxy 42 | start_privoxy='echo "anonym8 start_privoxy" > /tmp/code_terminal' 43 | stop_privoxy='echo "anonym8 stop_privoxy" > /tmp/code_terminal' 44 | status_privoxy='echo "anonym8 status_privoxy" > /tmp/code_terminal' 45 | 46 | #polipo 47 | start_polipo='echo "anonym8 start_polipo" > /tmp/code_terminal' 48 | stop_polipo='echo "anonym8 stop_polipo" > /tmp/code_terminal' 49 | status_polipo='echo "anonym8 status_polipo" > /tmp/code_terminal' 50 | 51 | #i2p 52 | start_i2p='echo "anonym8 start_i2p" > /tmp/code_terminal' 53 | stop_i2p='echo "anonym8 stop_i2p" > /tmp/code_terminal' 54 | status_i2p='echo "anonym8 status_i2p" > /tmp/code_terminal' 55 | 56 | #arm 57 | start_arm='echo "anonym8 start_arm" > /tmp/code_terminal' 58 | 59 | #wipe 60 | wipe='echo "anonym8 wipe" > /tmp/code_terminal' 61 | 62 | #hostname 63 | change_hostname='echo "anonym8 change_hostname" > /tmp/code_terminal' 64 | restore_hostname='echo "anonym8 restore_hostname" > /tmp/code_terminal' 65 | status_hostname='echo "anonym8 status_hostname" > /tmp/code_terminal' 66 | 67 | dim='8' 68 | 69 | export MAIN_DIALOG=' 70 | 71 | 72 | 73 | 74 | 80 | 86 | 87 | 88 | 89 | 95 | 101 | 107 | 113 | 119 | 125 | 131 | 132 | 133 | 134 | 135 | 141 | 147 | 148 | 149 | 155 | 161 | 162 | 163 | 169 | 170 | 171 | 177 | 178 | 179 | 180 | 181 | 182 | 188 | 194 | 200 | 201 | 202 | 208 | 214 | 215 | 216 | 222 | 228 | 229 | 230 | 236 | 242 | 243 | 244 | 245 | 246 | terminale 247 | '$tmp_file' 248 | 249 | 250 | 251 | 252 | 253 | ' 254 | gtkdialog --program=MAIN_DIALOG 255 | 256 | sed -i 'd' > $tmp_file 257 | 258 | exit 259 | -------------------------------------------------------------------------------- /polipo/config: -------------------------------------------------------------------------------- 1 | # This file only needs to list configuration variables that deviate 2 | # from the default values. See /usr/share/doc/polipo/examples/config.sample 3 | # and "polipo -v" for variables you can tweak and further information. 4 | 5 | logSyslog = true 6 | logFile = /var/log/polipo/polipo.log 7 | dnsUseGethostbyname = yes 8 | # Envoyer moins d'informations personnelles sur le net : 9 | censoredHeaders = from, accept-language 10 | censorReferer = maybe 11 | # tor 12 | socksParentProxy = "localhost:9050" 13 | socksProxyType = socks5 14 | -------------------------------------------------------------------------------- /privoxy/config: -------------------------------------------------------------------------------- 1 | # Sample Configuration File for Privoxy 2 | # 3 | # Id: config,v 4 | # 5 | # Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/ 6 | # 7 | #################################################################### 8 | # # 9 | # Table of Contents # 10 | # # 11 | # I. INTRODUCTION # 12 | # II. FORMAT OF THE CONFIGURATION FILE # 13 | # # 14 | # 1. LOCAL SET-UP DOCUMENTATION # 15 | # 2. CONFIGURATION AND LOG FILE LOCATIONS # 16 | # 3. DEBUGGING # 17 | # 4. ACCESS CONTROL AND SECURITY # 18 | # 5. FORWARDING # 19 | # 6. MISCELLANEOUS # 20 | # 7. WINDOWS GUI OPTIONS # 21 | # # 22 | #################################################################### 23 | # 24 | # 25 | # I. INTRODUCTION 26 | # =============== 27 | # 28 | # This file holds Privoxy's main configuration. Privoxy detects 29 | # configuration changes automatically, so you don't have to restart 30 | # it unless you want to load a different configuration file. 31 | # 32 | # The configuration will be reloaded with the first request after 33 | # the change was done, this request itself will still use the old 34 | # configuration, though. In other words: it takes two requests 35 | # before you see the result of your changes. Requests that are 36 | # dropped due to ACL don't trigger reloads. 37 | # 38 | # When starting Privoxy on Unix systems, give the location of this 39 | # file as last argument. On Windows systems, Privoxy will look for 40 | # this file with the name 'config.txt' in the current working 41 | # directory of the Privoxy process. 42 | # 43 | # 44 | # II. FORMAT OF THE CONFIGURATION FILE 45 | # ==================================== 46 | # 47 | # Configuration lines consist of an initial keyword followed by a 48 | # list of values, all separated by whitespace (any number of spaces 49 | # or tabs). For example, 50 | # 51 | # actionsfile default.action 52 | # 53 | # Indicates that the actionsfile is named 'default.action'. 54 | # 55 | # The '#' indicates a comment. Any part of a line following a '#' is 56 | # ignored, except if the '#' is preceded by a '\'. 57 | # 58 | # Thus, by placing a # at the start of an existing configuration 59 | # line, you can make it a comment and it will be treated as if it 60 | # weren't there. This is called "commenting out" an option and can 61 | # be useful. Removing the # again is called "uncommenting". 62 | # 63 | # Note that commenting out an option and leaving it at its default 64 | # are two completely different things! Most options behave very 65 | # differently when unset. See the "Effect if unset" explanation in 66 | # each option's description for details. 67 | # 68 | # Long lines can be continued on the next line by using a `\' as the 69 | # last character. 70 | # 71 | # 72 | # 1. LOCAL SET-UP DOCUMENTATION 73 | # ============================== 74 | # 75 | # If you intend to operate Privoxy for more users than just 76 | # yourself, it might be a good idea to let them know how to reach 77 | # you, what you block and why you do that, your policies, etc. 78 | # 79 | # 80 | # 1.1. user-manual 81 | # ================= 82 | # 83 | # Specifies: 84 | # 85 | # Location of the Privoxy User Manual. 86 | # 87 | # Type of value: 88 | # 89 | # A fully qualified URI 90 | # 91 | # Default value: 92 | # 93 | # Unset 94 | # 95 | # Effect if unset: 96 | # 97 | # http://www.privoxy.org/version/user-manual/ will be used, 98 | # where version is the Privoxy version. 99 | # 100 | # Notes: 101 | # 102 | # The User Manual URI is the single best source of information 103 | # on Privoxy, and is used for help links from some of the 104 | # internal CGI pages. The manual itself is normally packaged 105 | # with the binary distributions, so you probably want to set 106 | # this to a locally installed copy. 107 | # 108 | # Examples: 109 | # 110 | # The best all purpose solution is simply to put the full local 111 | # PATH to where the User Manual is located: 112 | # 113 | # user-manual /usr/share/doc/privoxy/user-manual 114 | # 115 | # The User Manual is then available to anyone with access to 116 | # Privoxy, by following the built-in URL: http:// 117 | # config.privoxy.org/user-manual/ (or the shortcut: http://p.p/ 118 | # user-manual/). 119 | # 120 | # If the documentation is not on the local system, it can be 121 | # accessed from a remote server, as: 122 | # 123 | # user-manual http://example.com/privoxy/user-manual/ 124 | # 125 | # WARNING!!! 126 | # 127 | # If set, this option should be the first option in the 128 | # config file, because it is used while the config file is 129 | # being read. 130 | # 131 | user-manual /usr/share/doc/privoxy/user-manual 132 | # 133 | # 1.2. trust-info-url 134 | # ==================== 135 | # 136 | # Specifies: 137 | # 138 | # A URL to be displayed in the error page that users will see if 139 | # access to an untrusted page is denied. 140 | # 141 | # Type of value: 142 | # 143 | # URL 144 | # 145 | # Default value: 146 | # 147 | # Unset 148 | # 149 | # Effect if unset: 150 | # 151 | # No links are displayed on the "untrusted" error page. 152 | # 153 | # Notes: 154 | # 155 | # The value of this option only matters if the experimental 156 | # trust mechanism has been activated. (See trustfile below.) 157 | # 158 | # If you use the trust mechanism, it is a good idea to write up 159 | # some on-line documentation about your trust policy and to 160 | # specify the URL(s) here. Use multiple times for multiple URLs. 161 | # 162 | # The URL(s) should be added to the trustfile as well, so users 163 | # don't end up locked out from the information on why they were 164 | # locked out in the first place! 165 | # 166 | #trust-info-url http://www.example.com/why_we_block.html 167 | #trust-info-url http://www.example.com/what_we_allow.html 168 | # 169 | # 1.3. admin-address 170 | # =================== 171 | # 172 | # Specifies: 173 | # 174 | # An email address to reach the Privoxy administrator. 175 | # 176 | # Type of value: 177 | # 178 | # Email address 179 | # 180 | # Default value: 181 | # 182 | # Unset 183 | # 184 | # Effect if unset: 185 | # 186 | # No email address is displayed on error pages and the CGI user 187 | # interface. 188 | # 189 | # Notes: 190 | # 191 | # If both admin-address and proxy-info-url are unset, the whole 192 | # "Local Privoxy Support" box on all generated pages will not be 193 | # shown. 194 | # 195 | #admin-address privoxy-admin@example.com 196 | # 197 | # 1.4. proxy-info-url 198 | # ==================== 199 | # 200 | # Specifies: 201 | # 202 | # A URL to documentation about the local Privoxy setup, 203 | # configuration or policies. 204 | # 205 | # Type of value: 206 | # 207 | # URL 208 | # 209 | # Default value: 210 | # 211 | # Unset 212 | # 213 | # Effect if unset: 214 | # 215 | # No link to local documentation is displayed on error pages and 216 | # the CGI user interface. 217 | # 218 | # Notes: 219 | # 220 | # If both admin-address and proxy-info-url are unset, the whole 221 | # "Local Privoxy Support" box on all generated pages will not be 222 | # shown. 223 | # 224 | # This URL shouldn't be blocked ;-) 225 | # 226 | #proxy-info-url http://www.example.com/proxy-service.html 227 | # 228 | # 2. CONFIGURATION AND LOG FILE LOCATIONS 229 | # ======================================== 230 | # 231 | # Privoxy can (and normally does) use a number of other files for 232 | # additional configuration, help and logging. This section of the 233 | # configuration file tells Privoxy where to find those other files. 234 | # 235 | # The user running Privoxy, must have read permission for all 236 | # configuration files, and write permission to any files that would 237 | # be modified, such as log files and actions files. 238 | # 239 | # 240 | # 2.1. confdir 241 | # ============= 242 | # 243 | # Specifies: 244 | # 245 | # The directory where the other configuration files are located. 246 | # 247 | # Type of value: 248 | # 249 | # Path name 250 | # 251 | # Default value: 252 | # 253 | # /etc/privoxy (Unix) or Privoxy installation dir (Windows) 254 | # 255 | # Effect if unset: 256 | # 257 | # Mandatory 258 | # 259 | # Notes: 260 | # 261 | # No trailing "/", please. 262 | # 263 | confdir /etc/privoxy 264 | # 265 | # 2.2. templdir 266 | # ============== 267 | # 268 | # Specifies: 269 | # 270 | # An alternative directory where the templates are loaded from. 271 | # 272 | # Type of value: 273 | # 274 | # Path name 275 | # 276 | # Default value: 277 | # 278 | # unset 279 | # 280 | # Effect if unset: 281 | # 282 | # The templates are assumed to be located in confdir/template. 283 | # 284 | # Notes: 285 | # 286 | # Privoxy's original templates are usually overwritten with each 287 | # update. Use this option to relocate customized templates that 288 | # should be kept. As template variables might change between 289 | # updates, you shouldn't expect templates to work with Privoxy 290 | # releases other than the one they were part of, though. 291 | # 292 | #templdir . 293 | # 294 | # 2.3. temporary-directory 295 | # ========================= 296 | # 297 | # Specifies: 298 | # 299 | # A directory where Privoxy can create temporary files. 300 | # 301 | # Type of value: 302 | # 303 | # Path name 304 | # 305 | # Default value: 306 | # 307 | # unset 308 | # 309 | # Effect if unset: 310 | # 311 | # No temporary files are created, external filters don't work. 312 | # 313 | # Notes: 314 | # 315 | # To execute external filters, Privoxy has to create temporary 316 | # files. This directive specifies the directory the temporary 317 | # files should be written to. 318 | # 319 | # It should be a directory only Privoxy (and trusted users) can 320 | # access. 321 | # 322 | #temporary-directory . 323 | # 324 | # 2.4. logdir 325 | # ============ 326 | # 327 | # Specifies: 328 | # 329 | # The directory where all logging takes place (i.e. where the 330 | # logfile is located). 331 | # 332 | # Type of value: 333 | # 334 | # Path name 335 | # 336 | # Default value: 337 | # 338 | # /var/log/privoxy (Unix) or Privoxy installation dir (Windows) 339 | # 340 | # Effect if unset: 341 | # 342 | # Mandatory 343 | # 344 | # Notes: 345 | # 346 | # No trailing "/", please. 347 | # 348 | logdir /var/log/privoxy 349 | # 350 | # 2.5. actionsfile 351 | # ================= 352 | # 353 | # Specifies: 354 | # 355 | # The actions file(s) to use 356 | # 357 | # Type of value: 358 | # 359 | # Complete file name, relative to confdir 360 | # 361 | # Default values: 362 | # 363 | # match-all.action # Actions that are applied to all sites and maybe overruled later on. 364 | # 365 | # default.action # Main actions file 366 | # 367 | # user.action # User customizations 368 | # 369 | # Effect if unset: 370 | # 371 | # No actions are taken at all. More or less neutral proxying. 372 | # 373 | # Notes: 374 | # 375 | # Multiple actionsfile lines are permitted, and are in fact 376 | # recommended! 377 | # 378 | # The default values are default.action, which is the "main" 379 | # actions file maintained by the developers, and user.action, 380 | # where you can make your personal additions. 381 | # 382 | # Actions files contain all the per site and per URL 383 | # configuration for ad blocking, cookie management, privacy 384 | # considerations, etc. 385 | # 386 | actionsfile match-all.action # Actions that are applied to all sites and maybe overruled later on. 387 | actionsfile default.action # Main actions file 388 | actionsfile user.action # User customizations 389 | # 390 | # 2.6. filterfile 391 | # ================ 392 | # 393 | # Specifies: 394 | # 395 | # The filter file(s) to use 396 | # 397 | # Type of value: 398 | # 399 | # File name, relative to confdir 400 | # 401 | # Default value: 402 | # 403 | # default.filter (Unix) or default.filter.txt (Windows) 404 | # 405 | # Effect if unset: 406 | # 407 | # No textual content filtering takes place, i.e. all +filter{name} 408 | # actions in the actions files are turned neutral. 409 | # 410 | # Notes: 411 | # 412 | # Multiple filterfile lines are permitted. 413 | # 414 | # The filter files contain content modification rules that use 415 | # regular expressions. These rules permit powerful changes on 416 | # the content of Web pages, and optionally the headers as well, 417 | # e.g., you could try to disable your favorite JavaScript 418 | # annoyances, re-write the actual displayed text, or just have 419 | # some fun playing buzzword bingo with web pages. 420 | # 421 | # The +filter{name} actions rely on the relevant filter (name) 422 | # to be defined in a filter file! 423 | # 424 | # A pre-defined filter file called default.filter that contains 425 | # a number of useful filters for common problems is included in 426 | # the distribution. See the section on the filter action for a 427 | # list. 428 | # 429 | # It is recommended to place any locally adapted filters into a 430 | # separate file, such as user.filter. 431 | # 432 | filterfile default.filter 433 | filterfile user.filter # User customizations 434 | # 435 | # 2.7. logfile 436 | # ============= 437 | # 438 | # Specifies: 439 | # 440 | # The log file to use 441 | # 442 | # Type of value: 443 | # 444 | # File name, relative to logdir 445 | # 446 | # Default value: 447 | # 448 | # Unset (commented out). When activated: logfile (Unix) or 449 | # privoxy.log (Windows). 450 | # 451 | # Effect if unset: 452 | # 453 | # No logfile is written. 454 | # 455 | # Notes: 456 | # 457 | # The logfile is where all logging and error messages are 458 | # written. The level of detail and number of messages are set 459 | # with the debug option (see below). The logfile can be useful 460 | # for tracking down a problem with Privoxy (e.g., it's not 461 | # blocking an ad you think it should block) and it can help you 462 | # to monitor what your browser is doing. 463 | # 464 | # Depending on the debug options below, the logfile may be a 465 | # privacy risk if third parties can get access to it. As most 466 | # users will never look at it, Privoxy only logs fatal errors by 467 | # default. 468 | # 469 | # For most troubleshooting purposes, you will have to change 470 | # that, please refer to the debugging section for details. 471 | # 472 | # Any log files must be writable by whatever user Privoxy is 473 | # being run as (on Unix, default user id is "privoxy"). 474 | # 475 | # To prevent the logfile from growing indefinitely, it is 476 | # recommended to periodically rotate or shorten it. Many 477 | # operating systems support log rotation out of the box, some 478 | # require additional software to do it. For details, please 479 | # refer to the documentation for your operating system. 480 | # 481 | logfile logfile 482 | # 483 | # 2.8. trustfile 484 | # =============== 485 | # 486 | # Specifies: 487 | # 488 | # The name of the trust file to use 489 | # 490 | # Type of value: 491 | # 492 | # File name, relative to confdir 493 | # 494 | # Default value: 495 | # 496 | # Unset (commented out). When activated: trust (Unix) or 497 | # trust.txt (Windows) 498 | # 499 | # Effect if unset: 500 | # 501 | # The entire trust mechanism is disabled. 502 | # 503 | # Notes: 504 | # 505 | # The trust mechanism is an experimental feature for building 506 | # white-lists and should be used with care. It is NOT 507 | # recommended for the casual user. 508 | # 509 | # If you specify a trust file, Privoxy will only allow access to 510 | # sites that are specified in the trustfile. Sites can be listed 511 | # in one of two ways: 512 | # 513 | # Prepending a ~ character limits access to this site only (and 514 | # any sub-paths within this site), e.g. ~www.example.com allows 515 | # access to ~www.example.com/features/news.html, etc. 516 | # 517 | # Or, you can designate sites as trusted referrers, by 518 | # prepending the name with a + character. The effect is that 519 | # access to untrusted sites will be granted -- but only if a 520 | # link from this trusted referrer was used to get there. The 521 | # link target will then be added to the "trustfile" so that 522 | # future, direct accesses will be granted. Sites added via this 523 | # mechanism do not become trusted referrers themselves (i.e. 524 | # they are added with a ~ designation). There is a limit of 512 525 | # such entries, after which new entries will not be made. 526 | # 527 | # If you use the + operator in the trust file, it may grow 528 | # considerably over time. 529 | # 530 | # It is recommended that Privoxy be compiled with the 531 | # --disable-force, --disable-toggle and --disable-editor 532 | # options, if this feature is to be used. 533 | # 534 | # Possible applications include limiting Internet access for 535 | # children. 536 | # 537 | #trustfile trust 538 | # 539 | # 3. DEBUGGING 540 | # ============= 541 | # 542 | # These options are mainly useful when tracing a problem. Note that 543 | # you might also want to invoke Privoxy with the --no-daemon command 544 | # line option when debugging. 545 | # 546 | # 547 | # 3.1. debug 548 | # =========== 549 | # 550 | # Specifies: 551 | # 552 | # Key values that determine what information gets logged. 553 | # 554 | # Type of value: 555 | # 556 | # Integer values 557 | # 558 | # Default value: 559 | # 560 | # 0 (i.e.: only fatal errors (that cause Privoxy to exit) are 561 | # logged) 562 | # 563 | # Effect if unset: 564 | # 565 | # Default value is used (see above). 566 | # 567 | # Notes: 568 | # 569 | # The available debug levels are: 570 | # 571 | # debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. 572 | # debug 2 # show each connection status 573 | # debug 4 # show I/O status 574 | # debug 8 # show header parsing 575 | # debug 16 # log all data written to the network 576 | # debug 32 # debug force feature 577 | # debug 64 # debug regular expression filters 578 | # debug 128 # debug redirects 579 | # debug 256 # debug GIF de-animation 580 | # debug 512 # Common Log Format 581 | # debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why. 582 | # debug 2048 # CGI user interface 583 | # debug 4096 # Startup banner and warnings. 584 | # debug 8192 # Non-fatal errors 585 | # debug 32768 # log all data read from the network 586 | # debug 65536 # Log the applying actions 587 | # 588 | # To select multiple debug levels, you can either add them or 589 | # use multiple debug lines. 590 | # 591 | # A debug level of 1 is informative because it will show you 592 | # each request as it happens. 1, 1024, 4096 and 8192 are 593 | # recommended so that you will notice when things go wrong. The 594 | # other levels are probably only of interest if you are hunting 595 | # down a specific problem. They can produce a hell of an output 596 | # (especially 16). 597 | # 598 | # If you are used to the more verbose settings, simply enable 599 | # the debug lines below again. 600 | # 601 | # If you want to use pure CLF (Common Log Format), you should 602 | # set "debug 512" ONLY and not enable anything else. 603 | # 604 | # Privoxy has a hard-coded limit for the length of log messages. 605 | # If it's reached, messages are logged truncated and marked with 606 | # "... [too long, truncated]". 607 | # 608 | # Please don't file any support requests without trying to 609 | # reproduce the problem with increased debug level first. Once 610 | # you read the log messages, you may even be able to solve the 611 | # problem on your own. 612 | # 613 | #debug 1 # Log the destination for each request Privoxy let through. See also debug 1024. 614 | #debug 1024 # Actions that are applied to all sites and maybe overruled later on. 615 | #debug 4096 # Startup banner and warnings 616 | #debug 8192 # Non-fatal errors 617 | # 618 | # 3.2. single-threaded 619 | # ===================== 620 | # 621 | # Specifies: 622 | # 623 | # Whether to run only one server thread. 624 | # 625 | # Type of value: 626 | # 627 | # 1 or 0 628 | # 629 | # Default value: 630 | # 631 | # 0 632 | # 633 | # Effect if unset: 634 | # 635 | # Multi-threaded (or, where unavailable: forked) operation, i.e. 636 | # the ability to serve multiple requests simultaneously. 637 | # 638 | # Notes: 639 | # 640 | # This option is only there for debugging purposes. It will 641 | # drastically reduce performance. 642 | # 643 | #single-threaded 1 644 | # 645 | # 3.3. hostname 646 | # ============== 647 | # 648 | # Specifies: 649 | # 650 | # The hostname shown on the CGI pages. 651 | # 652 | # Type of value: 653 | # 654 | # Text 655 | # 656 | # Default value: 657 | # 658 | # Unset 659 | # 660 | # Effect if unset: 661 | # 662 | # The hostname provided by the operating system is used. 663 | # 664 | # Notes: 665 | # 666 | # On some misconfigured systems resolving the hostname fails or 667 | # takes too much time and slows Privoxy down. Setting a fixed 668 | # hostname works around the problem. 669 | # 670 | # In other circumstances it might be desirable to show a 671 | # hostname other than the one returned by the operating system. 672 | # For example if the system has several different hostnames and 673 | # you don't want to use the first one. 674 | # 675 | # Note that Privoxy does not validate the specified hostname 676 | # value. 677 | # 678 | #hostname hostname.example.org 679 | # 680 | # 4. ACCESS CONTROL AND SECURITY 681 | # =============================== 682 | # 683 | # This section of the config file controls the security-relevant 684 | # aspects of Privoxy's configuration. 685 | # 686 | # 687 | # 4.1. listen-address 688 | # ==================== 689 | # 690 | # Specifies: 691 | # 692 | # The address and TCP port on which Privoxy will listen for 693 | # client requests. 694 | # 695 | # Type of value: 696 | # 697 | # [IP-Address]:Port 698 | # 699 | # [Hostname]:Port 700 | # 701 | # Default value: 702 | # 703 | # 127.0.0.1:8118 704 | # 705 | # Effect if unset: 706 | # 707 | # Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is 708 | # suitable and recommended for home users who run Privoxy on the 709 | # same machine as their browser. 710 | # 711 | # Notes: 712 | # 713 | # You will need to configure your browser(s) to this proxy 714 | # address and port. 715 | # 716 | # If you already have another service running on port 8118, or 717 | # if you want to serve requests from other machines (e.g. on 718 | # your local network) as well, you will need to override the 719 | # default. 720 | # 721 | # You can use this statement multiple times to make Privoxy 722 | # listen on more ports or more IP addresses. Suitable if your 723 | # operating system does not support sharing IPv6 and IPv4 724 | # protocols on the same socket. 725 | # 726 | # If a hostname is used instead of an IP address, Privoxy will 727 | # try to resolve it to an IP address and if there are multiple, 728 | # use the first one returned. 729 | # 730 | # If the address for the hostname isn't already known on the 731 | # system (for example because it's in /etc/hostname), this may 732 | # result in DNS traffic. 733 | # 734 | # If the specified address isn't available on the system, or if 735 | # the hostname can't be resolved, Privoxy will fail to start. 736 | # 737 | # IPv6 addresses containing colons have to be quoted by 738 | # brackets. They can only be used if Privoxy has been compiled 739 | # with IPv6 support. If you aren't sure if your version supports 740 | # it, have a look at http://config.privoxy.org/show-status. 741 | # 742 | # Some operating systems will prefer IPv6 to IPv4 addresses even 743 | # if the system has no IPv6 connectivity which is usually not 744 | # expected by the user. Some even rely on DNS to resolve 745 | # localhost which mean the "localhost" address used may not 746 | # actually be local. 747 | # 748 | # It is therefore recommended to explicitly configure the 749 | # intended IP address instead of relying on the operating 750 | # system, unless there's a strong reason not to. 751 | # 752 | # If you leave out the address, Privoxy will bind to all IPv4 753 | # interfaces (addresses) on your machine and may become 754 | # reachable from the Internet and/or the local network. Be aware 755 | # that some GNU/Linux distributions modify that behaviour 756 | # without updating the documentation. Check for non-standard 757 | # patches if your Privoxy version behaves differently. 758 | # 759 | # If you configure Privoxy to be reachable from the network, 760 | # consider using access control lists (ACL's, see below), and/or 761 | # a firewall. 762 | # 763 | # If you open Privoxy to untrusted users, you will also want to 764 | # make sure that the following actions are disabled: 765 | # enable-edit-actions and enable-remote-toggle 766 | # 767 | # Example: 768 | # 769 | # Suppose you are running Privoxy on a machine which has the 770 | # address 192.168.0.1 on your local private network 771 | # (192.168.0.0) and has another outside connection with a 772 | # different address. You want it to serve requests from inside 773 | # only: 774 | # 775 | # listen-address 192.168.0.1:8118 776 | # 777 | # Suppose you are running Privoxy on an IPv6-capable machine and 778 | # you want it to listen on the IPv6 address of the loopback 779 | # device: 780 | # 781 | # listen-address [::1]:8118 782 | # 783 | listen-address 127.0.0.1:8118 784 | listen-address [::1]:8118 785 | # 786 | # 4.2. toggle 787 | # ============ 788 | # 789 | # Specifies: 790 | # 791 | # Initial state of "toggle" status 792 | # 793 | # Type of value: 794 | # 795 | # 1 or 0 796 | # 797 | # Default value: 798 | # 799 | # 1 800 | # 801 | # Effect if unset: 802 | # 803 | # Act as if toggled on 804 | # 805 | # Notes: 806 | # 807 | # If set to 0, Privoxy will start in "toggled off" mode, i.e. 808 | # mostly behave like a normal, content-neutral proxy with both 809 | # ad blocking and content filtering disabled. See 810 | # enable-remote-toggle below. 811 | # 812 | toggle 1 813 | # 814 | # 4.3. enable-remote-toggle 815 | # ========================== 816 | # 817 | # Specifies: 818 | # 819 | # Whether or not the web-based toggle feature may be used 820 | # 821 | # Type of value: 822 | # 823 | # 0 or 1 824 | # 825 | # Default value: 826 | # 827 | # 0 828 | # 829 | # Effect if unset: 830 | # 831 | # The web-based toggle feature is disabled. 832 | # 833 | # Notes: 834 | # 835 | # When toggled off, Privoxy mostly acts like a normal, 836 | # content-neutral proxy, i.e. doesn't block ads or filter 837 | # content. 838 | # 839 | # Access to the toggle feature can not be controlled separately 840 | # by "ACLs" or HTTP authentication, so that everybody who can 841 | # access Privoxy (see "ACLs" and listen-address above) can 842 | # toggle it for all users. So this option is not recommended for 843 | # multi-user environments with untrusted users. 844 | # 845 | # Note that malicious client side code (e.g Java) is also 846 | # capable of using this option. 847 | # 848 | # As a lot of Privoxy users don't read documentation, this 849 | # feature is disabled by default. 850 | # 851 | # Note that you must have compiled Privoxy with support for this 852 | # feature, otherwise this option has no effect. 853 | # 854 | enable-remote-toggle 0 855 | # 856 | # 4.4. enable-remote-http-toggle 857 | # =============================== 858 | # 859 | # Specifies: 860 | # 861 | # Whether or not Privoxy recognizes special HTTP headers to 862 | # change its behaviour. 863 | # 864 | # Type of value: 865 | # 866 | # 0 or 1 867 | # 868 | # Default value: 869 | # 870 | # 0 871 | # 872 | # Effect if unset: 873 | # 874 | # Privoxy ignores special HTTP headers. 875 | # 876 | # Notes: 877 | # 878 | # When toggled on, the client can change Privoxy's behaviour by 879 | # setting special HTTP headers. Currently the only supported 880 | # special header is "X-Filter: No", to disable filtering for the 881 | # ongoing request, even if it is enabled in one of the action 882 | # files. 883 | # 884 | # This feature is disabled by default. If you are using Privoxy 885 | # in a environment with trusted clients, you may enable this 886 | # feature at your discretion. Note that malicious client side 887 | # code (e.g Java) is also capable of using this feature. 888 | # 889 | # This option will be removed in future releases as it has been 890 | # obsoleted by the more general header taggers. 891 | # 892 | enable-remote-http-toggle 0 893 | # 894 | # 4.5. enable-edit-actions 895 | # ========================= 896 | # 897 | # Specifies: 898 | # 899 | # Whether or not the web-based actions file editor may be used 900 | # 901 | # Type of value: 902 | # 903 | # 0 or 1 904 | # 905 | # Default value: 906 | # 907 | # 0 908 | # 909 | # Effect if unset: 910 | # 911 | # The web-based actions file editor is disabled. 912 | # 913 | # Notes: 914 | # 915 | # Access to the editor can not be controlled separately by 916 | # "ACLs" or HTTP authentication, so that everybody who can 917 | # access Privoxy (see "ACLs" and listen-address above) can 918 | # modify its configuration for all users. 919 | # 920 | # This option is not recommended for environments with untrusted 921 | # users and as a lot of Privoxy users don't read documentation, 922 | # this feature is disabled by default. 923 | # 924 | # Note that malicious client side code (e.g Java) is also 925 | # capable of using the actions editor and you shouldn't enable 926 | # this options unless you understand the consequences and are 927 | # sure your browser is configured correctly. 928 | # 929 | # Note that you must have compiled Privoxy with support for this 930 | # feature, otherwise this option has no effect. 931 | # 932 | enable-edit-actions 0 933 | # 934 | # 4.6. enforce-blocks 935 | # ==================== 936 | # 937 | # Specifies: 938 | # 939 | # Whether the user is allowed to ignore blocks and can "go there 940 | # anyway". 941 | # 942 | # Type of value: 943 | # 944 | # 0 or 1 945 | # 946 | # Default value: 947 | # 948 | # 0 949 | # 950 | # Effect if unset: 951 | # 952 | # Blocks are not enforced. 953 | # 954 | # Notes: 955 | # 956 | # Privoxy is mainly used to block and filter requests as a 957 | # service to the user, for example to block ads and other junk 958 | # that clogs the pipes. Privoxy's configuration isn't perfect 959 | # and sometimes innocent pages are blocked. In this situation it 960 | # makes sense to allow the user to enforce the request and have 961 | # Privoxy ignore the block. 962 | # 963 | # In the default configuration Privoxy's "Blocked" page contains 964 | # a "go there anyway" link to adds a special string (the force 965 | # prefix) to the request URL. If that link is used, Privoxy will 966 | # detect the force prefix, remove it again and let the request 967 | # pass. 968 | # 969 | # Of course Privoxy can also be used to enforce a network 970 | # policy. In that case the user obviously should not be able to 971 | # bypass any blocks, and that's what the "enforce-blocks" option 972 | # is for. If it's enabled, Privoxy hides the "go there anyway" 973 | # link. If the user adds the force prefix by hand, it will not 974 | # be accepted and the circumvention attempt is logged. 975 | # 976 | # Examples: 977 | # 978 | # enforce-blocks 1 979 | # 980 | enforce-blocks 0 981 | # 982 | # 4.7. ACLs: permit-access and deny-access 983 | # ========================================= 984 | # 985 | # Specifies: 986 | # 987 | # Who can access what. 988 | # 989 | # Type of value: 990 | # 991 | # src_addr[:port][/src_masklen] [dst_addr[:port][/dst_masklen]] 992 | # 993 | # Where src_addr and dst_addr are IPv4 addresses in dotted 994 | # decimal notation or valid DNS names, port is a port number, 995 | # and src_masklen and dst_masklen are subnet masks in CIDR 996 | # notation, i.e. integer values from 2 to 30 representing the 997 | # length (in bits) of the network address. The masks and the 998 | # whole destination part are optional. 999 | # 1000 | # If your system implements RFC 3493, then src_addr and dst_addr 1001 | # can be IPv6 addresses delimeted by brackets, port can be a 1002 | # number or a service name, and src_masklen and dst_masklen can 1003 | # be a number from 0 to 128. 1004 | # 1005 | # Default value: 1006 | # 1007 | # Unset 1008 | # 1009 | # If no port is specified, any port will match. If no 1010 | # src_masklen or src_masklen is given, the complete IP address 1011 | # has to match (i.e. 32 bits for IPv4 and 128 bits for IPv6). 1012 | # 1013 | # Effect if unset: 1014 | # 1015 | # Don't restrict access further than implied by listen-address 1016 | # 1017 | # Notes: 1018 | # 1019 | # Access controls are included at the request of ISPs and 1020 | # systems administrators, and are not usually needed by 1021 | # individual users. For a typical home user, it will normally 1022 | # suffice to ensure that Privoxy only listens on the localhost 1023 | # (127.0.0.1) or internal (home) network address by means of the 1024 | # listen-address option. 1025 | # 1026 | # Please see the warnings in the FAQ that Privoxy is not 1027 | # intended to be a substitute for a firewall or to encourage 1028 | # anyone to defer addressing basic security weaknesses. 1029 | # 1030 | # Multiple ACL lines are OK. If any ACLs are specified, Privoxy 1031 | # only talks to IP addresses that match at least one 1032 | # permit-access line and don't match any subsequent deny-access 1033 | # line. In other words, the last match wins, with the default 1034 | # being deny-access. 1035 | # 1036 | # If Privoxy is using a forwarder (see forward below) for a 1037 | # particular destination URL, the dst_addr that is examined is 1038 | # the address of the forwarder and NOT the address of the 1039 | # ultimate target. This is necessary because it may be 1040 | # impossible for the local Privoxy to determine the IP address 1041 | # of the ultimate target (that's often what gateways are used 1042 | # for). 1043 | # 1044 | # You should prefer using IP addresses over DNS names, because 1045 | # the address lookups take time. All DNS names must resolve! You 1046 | # can not use domain patterns like "*.org" or partial domain 1047 | # names. If a DNS name resolves to multiple IP addresses, only 1048 | # the first one is used. 1049 | # 1050 | # Some systems allow IPv4 clients to connect to IPv6 server 1051 | # sockets. Then the client's IPv4 address will be translated by 1052 | # the system into IPv6 address space with special prefix 1053 | # ::ffff:0:0/96 (so called IPv4 mapped IPv6 address). Privoxy 1054 | # can handle it and maps such ACL addresses automatically. 1055 | # 1056 | # Denying access to particular sites by ACL may have undesired 1057 | # side effects if the site in question is hosted on a machine 1058 | # which also hosts other sites (most sites are). 1059 | # 1060 | # Examples: 1061 | # 1062 | # Explicitly define the default behavior if no ACL and 1063 | # listen-address are set: "localhost" is OK. The absence of a 1064 | # dst_addr implies that all destination addresses are OK: 1065 | # 1066 | # permit-access localhost 1067 | # 1068 | # Allow any host on the same class C subnet as www.privoxy.org 1069 | # access to nothing but www.example.com (or other domains hosted 1070 | # on the same system): 1071 | # 1072 | # permit-access www.privoxy.org/24 www.example.com/32 1073 | # 1074 | # Allow access from any host on the 26-bit subnet 192.168.45.64 1075 | # to anywhere, with the exception that 192.168.45.73 may not 1076 | # access the IP address behind www.dirty-stuff.example.com: 1077 | # 1078 | # permit-access 192.168.45.64/26 1079 | # deny-access 192.168.45.73 www.dirty-stuff.example.com 1080 | # 1081 | # Allow access from the IPv4 network 192.0.2.0/24 even if 1082 | # listening on an IPv6 wild card address (not supported on all 1083 | # platforms): 1084 | # 1085 | # permit-access 192.0.2.0/24 1086 | # 1087 | # This is equivalent to the following line even if listening on 1088 | # an IPv4 address (not supported on all platforms): 1089 | # 1090 | # permit-access [::ffff:192.0.2.0]/120 1091 | # 1092 | # 1093 | # 4.8. buffer-limit 1094 | # ================== 1095 | # 1096 | # Specifies: 1097 | # 1098 | # Maximum size of the buffer for content filtering. 1099 | # 1100 | # Type of value: 1101 | # 1102 | # Size in Kbytes 1103 | # 1104 | # Default value: 1105 | # 1106 | # 4096 1107 | # 1108 | # Effect if unset: 1109 | # 1110 | # Use a 4MB (4096 KB) limit. 1111 | # 1112 | # Notes: 1113 | # 1114 | # For content filtering, i.e. the +filter and +deanimate-gif 1115 | # actions, it is necessary that Privoxy buffers the entire 1116 | # document body. This can be potentially dangerous, since a 1117 | # server could just keep sending data indefinitely and wait for 1118 | # your RAM to exhaust -- with nasty consequences. Hence this 1119 | # option. 1120 | # 1121 | # When a document buffer size reaches the buffer-limit, it is 1122 | # flushed to the client unfiltered and no further attempt to 1123 | # filter the rest of the document is made. Remember that there 1124 | # may be multiple threads running, which might require up to 1125 | # buffer-limit Kbytes each, unless you have enabled 1126 | # "single-threaded" above. 1127 | # 1128 | buffer-limit 4096 1129 | # 1130 | # 4.9. enable-proxy-authentication-forwarding 1131 | # ============================================ 1132 | # 1133 | # Specifies: 1134 | # 1135 | # Whether or not proxy authentication through Privoxy should 1136 | # work. 1137 | # 1138 | # Type of value: 1139 | # 1140 | # 0 or 1 1141 | # 1142 | # Default value: 1143 | # 1144 | # 0 1145 | # 1146 | # Effect if unset: 1147 | # 1148 | # Proxy authentication headers are removed. 1149 | # 1150 | # Notes: 1151 | # 1152 | # Privoxy itself does not support proxy authentication, but can 1153 | # allow clients to authenticate against Privoxy's parent proxy. 1154 | # 1155 | # By default Privoxy (3.0.21 and later) don't do that and remove 1156 | # Proxy-Authorization headers in requests and Proxy-Authenticate 1157 | # headers in responses to make it harder for malicious sites to 1158 | # trick inexperienced users into providing login information. 1159 | # 1160 | # If this option is enabled the headers are forwarded. 1161 | # 1162 | # Enabling this option is not recommended if there is no parent 1163 | # proxy that requires authentication or if the local network 1164 | # between Privoxy and the parent proxy isn't trustworthy. If 1165 | # proxy authentication is only required for some requests, it is 1166 | # recommended to use a client header filter to remove the 1167 | # authentication headers for requests where they aren't needed. 1168 | # 1169 | enable-proxy-authentication-forwarding 0 1170 | # 1171 | # 5. FORWARDING 1172 | # ============== 1173 | # 1174 | # This feature allows routing of HTTP requests through a chain of 1175 | # multiple proxies. 1176 | # 1177 | # Forwarding can be used to chain Privoxy with a caching proxy to 1178 | # speed up browsing. Using a parent proxy may also be necessary if 1179 | # the machine that Privoxy runs on has no direct Internet access. 1180 | # 1181 | # Note that parent proxies can severely decrease your privacy level. 1182 | # For example a parent proxy could add your IP address to the 1183 | # request headers and if it's a caching proxy it may add the "Etag" 1184 | # header to revalidation requests again, even though you configured 1185 | # Privoxy to remove it. It may also ignore Privoxy's header time 1186 | # randomization and use the original values which could be used by 1187 | # the server as cookie replacement to track your steps between 1188 | # visits. 1189 | # 1190 | # Also specified here are SOCKS proxies. Privoxy supports the SOCKS 1191 | # 4 and SOCKS 4A protocols. 1192 | # 1193 | # 1194 | # 5.1. forward 1195 | # ============= 1196 | # 1197 | # Specifies: 1198 | # 1199 | # To which parent HTTP proxy specific requests should be routed. 1200 | # 1201 | # Type of value: 1202 | # 1203 | # target_pattern http_parent[:port] 1204 | # 1205 | # where target_pattern is a URL pattern that specifies to which 1206 | # requests (i.e. URLs) this forward rule shall apply. Use / to 1207 | # denote "all URLs". http_parent[:port] is the DNS name or IP 1208 | # address of the parent HTTP proxy through which the requests 1209 | # should be forwarded, optionally followed by its listening port 1210 | # (default: 8000). Use a single dot (.) to denote "no 1211 | # forwarding". 1212 | # 1213 | # Default value: 1214 | # 1215 | # Unset 1216 | # 1217 | # Effect if unset: 1218 | # 1219 | # Don't use parent HTTP proxies. 1220 | # 1221 | # Notes: 1222 | # 1223 | # If http_parent is ".", then requests are not forwarded to 1224 | # another HTTP proxy but are made directly to the web servers. 1225 | # 1226 | # http_parent can be a numerical IPv6 address (if RFC 3493 is 1227 | # implemented). To prevent clashes with the port delimiter, the 1228 | # whole IP address has to be put into brackets. On the other 1229 | # hand a target_pattern containing an IPv6 address has to be put 1230 | # into angle brackets (normal brackets are reserved for regular 1231 | # expressions already). 1232 | # 1233 | # Multiple lines are OK, they are checked in sequence, and the 1234 | # last match wins. 1235 | # 1236 | # Examples: 1237 | # 1238 | # Everything goes to an example parent proxy, except SSL on port 1239 | # 443 (which it doesn't handle): 1240 | # 1241 | # forward / parent-proxy.example.org:8080 1242 | # forward :443 . 1243 | # 1244 | # Everything goes to our example ISP's caching proxy, except for 1245 | # requests to that ISP's sites: 1246 | # 1247 | # forward / caching-proxy.isp.example.net:8000 1248 | # forward .isp.example.net . 1249 | # 1250 | # Parent proxy specified by an IPv6 address: 1251 | # 1252 | # forward / [2001:DB8::1]:8000 1253 | # 1254 | # Suppose your parent proxy doesn't support IPv6: 1255 | # 1256 | # forward / parent-proxy.example.org:8000 1257 | # forward ipv6-server.example.org . 1258 | # forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> . 1259 | # 1260 | # 1261 | # 5.2. forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t 1262 | # ========================================================================= 1263 | # 1264 | # Specifies: 1265 | # 1266 | # Through which SOCKS proxy (and optionally to which parent HTTP 1267 | # proxy) specific requests should be routed. 1268 | # 1269 | # Type of value: 1270 | # 1271 | # target_pattern socks_proxy[:port] http_parent[:port] 1272 | # 1273 | # where target_pattern is a URL pattern that specifies to which 1274 | # requests (i.e. URLs) this forward rule shall apply. Use / to 1275 | # denote "all URLs". http_parent and socks_proxy are IP 1276 | # addresses in dotted decimal notation or valid DNS names ( 1277 | # http_parent may be "." to denote "no HTTP forwarding"), and 1278 | # the optional port parameters are TCP ports, i.e. integer 1279 | # values from 1 to 65535 1280 | # 1281 | # Default value: 1282 | # 1283 | # Unset 1284 | # 1285 | # Effect if unset: 1286 | # 1287 | # Don't use SOCKS proxies. 1288 | # 1289 | # Notes: 1290 | # 1291 | # Multiple lines are OK, they are checked in sequence, and the 1292 | # last match wins. 1293 | # 1294 | # The difference between forward-socks4 and forward-socks4a is 1295 | # that in the SOCKS 4A protocol, the DNS resolution of the 1296 | # target hostname happens on the SOCKS server, while in SOCKS 4 1297 | # it happens locally. 1298 | # 1299 | # With forward-socks5 the DNS resolution will happen on the 1300 | # remote server as well. 1301 | # 1302 | # forward-socks5t works like vanilla forward-socks5 but lets 1303 | # Privoxy additionally use Tor-specific SOCKS extensions. 1304 | # Currently the only supported SOCKS extension is optimistic 1305 | # data which can reduce the latency for the first request made 1306 | # on a newly created connection. 1307 | # 1308 | # socks_proxy and http_parent can be a numerical IPv6 address 1309 | # (if RFC 3493 is implemented). To prevent clashes with the port 1310 | # delimiter, the whole IP address has to be put into brackets. 1311 | # On the other hand a target_pattern containing an IPv6 address 1312 | # has to be put into angle brackets (normal brackets are 1313 | # reserved for regular expressions already). 1314 | # 1315 | # If http_parent is ".", then requests are not forwarded to 1316 | # another HTTP proxy but are made (HTTP-wise) directly to the 1317 | # web servers, albeit through a SOCKS proxy. 1318 | # 1319 | # Examples: 1320 | # 1321 | # From the company example.com, direct connections are made to 1322 | # all "internal" domains, but everything outbound goes through 1323 | # their ISP's proxy by way of example.com's corporate SOCKS 4A 1324 | # gateway to the Internet. 1325 | # 1326 | # forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080 1327 | # forward .example.com . 1328 | # 1329 | # A rule that uses a SOCKS 4 gateway for all destinations but no 1330 | # HTTP parent looks like this: 1331 | # 1332 | # forward-socks4 / socks-gw.example.com:1080 . 1333 | # 1334 | # To chain Privoxy and Tor, both running on the same system, you 1335 | # would use something like: 1336 | # 1337 | # forward-socks5t / 127.0.0.1:9050 . 1338 | # 1339 | # Note that if you got Tor through one of the bundles, you may 1340 | # have to change the port from 9050 to 9150 (or even another 1341 | # one). For details, please check the documentation on the Tor 1342 | # website. 1343 | # 1344 | # The public Tor network can't be used to reach your local 1345 | # network, if you need to access local servers you therefore 1346 | # might want to make some exceptions: 1347 | # 1348 | # forward 192.168.*.*/ . 1349 | # forward 10.*.*.*/ . 1350 | # forward 127.*.*.*/ . 1351 | # 1352 | # Unencrypted connections to systems in these address ranges 1353 | # will be as (un)secure as the local network is, but the 1354 | # alternative is that you can't reach the local network through 1355 | # Privoxy at all. Of course this may actually be desired and 1356 | # there is no reason to make these exceptions if you aren't sure 1357 | # you need them. 1358 | # 1359 | # If you also want to be able to reach servers in your local 1360 | # network by using their names, you will need additional 1361 | # exceptions that look like this: 1362 | # 1363 | # forward localhost/ . 1364 | # 1365 | # 1366 | # 5.3. forwarded-connect-retries 1367 | # =============================== 1368 | # 1369 | # Specifies: 1370 | # 1371 | # How often Privoxy retries if a forwarded connection request 1372 | # fails. 1373 | # 1374 | # Type of value: 1375 | # 1376 | # Number of retries. 1377 | # 1378 | # Default value: 1379 | # 1380 | # 0 1381 | # 1382 | # Effect if unset: 1383 | # 1384 | # Connections forwarded through other proxies are treated like 1385 | # direct connections and no retry attempts are made. 1386 | # 1387 | # Notes: 1388 | # 1389 | # forwarded-connect-retries is mainly interesting for socks4a 1390 | # connections, where Privoxy can't detect why the connections 1391 | # failed. The connection might have failed because of a DNS 1392 | # timeout in which case a retry makes sense, but it might also 1393 | # have failed because the server doesn't exist or isn't 1394 | # reachable. In this case the retry will just delay the 1395 | # appearance of Privoxy's error message. 1396 | # 1397 | # Note that in the context of this option, "forwarded 1398 | # connections" includes all connections that Privoxy forwards 1399 | # through other proxies. This option is not limited to the HTTP 1400 | # CONNECT method. 1401 | # 1402 | # Only use this option, if you are getting lots of 1403 | # forwarding-related error messages that go away when you try 1404 | # again manually. Start with a small value and check Privoxy's 1405 | # logfile from time to time, to see how many retries are usually 1406 | # needed. 1407 | # 1408 | # Examples: 1409 | # 1410 | # forwarded-connect-retries 1 1411 | # 1412 | forwarded-connect-retries 0 1413 | # 1414 | # 6. MISCELLANEOUS 1415 | # ================= 1416 | # 1417 | # 6.1. accept-intercepted-requests 1418 | # ================================= 1419 | # 1420 | # Specifies: 1421 | # 1422 | # Whether intercepted requests should be treated as valid. 1423 | # 1424 | # Type of value: 1425 | # 1426 | # 0 or 1 1427 | # 1428 | # Default value: 1429 | # 1430 | # 0 1431 | # 1432 | # Effect if unset: 1433 | # 1434 | # Only proxy requests are accepted, intercepted requests are 1435 | # treated as invalid. 1436 | # 1437 | # Notes: 1438 | # 1439 | # If you don't trust your clients and want to force them to use 1440 | # Privoxy, enable this option and configure your packet filter 1441 | # to redirect outgoing HTTP connections into Privoxy. 1442 | # 1443 | # Note that intercepting encrypted connections (HTTPS) isn't 1444 | # supported. 1445 | # 1446 | # Make sure that Privoxy's own requests aren't redirected as 1447 | # well. Additionally take care that Privoxy can't intentionally 1448 | # connect to itself, otherwise you could run into redirection 1449 | # loops if Privoxy's listening port is reachable by the outside 1450 | # or an attacker has access to the pages you visit. 1451 | # 1452 | # Examples: 1453 | # 1454 | # accept-intercepted-requests 1 1455 | # 1456 | accept-intercepted-requests 0 1457 | # 1458 | # 6.2. allow-cgi-request-crunching 1459 | # ================================= 1460 | # 1461 | # Specifies: 1462 | # 1463 | # Whether requests to Privoxy's CGI pages can be blocked or 1464 | # redirected. 1465 | # 1466 | # Type of value: 1467 | # 1468 | # 0 or 1 1469 | # 1470 | # Default value: 1471 | # 1472 | # 0 1473 | # 1474 | # Effect if unset: 1475 | # 1476 | # Privoxy ignores block and redirect actions for its CGI pages. 1477 | # 1478 | # Notes: 1479 | # 1480 | # By default Privoxy ignores block or redirect actions for its 1481 | # CGI pages. Intercepting these requests can be useful in 1482 | # multi-user setups to implement fine-grained access control, 1483 | # but it can also render the complete web interface useless and 1484 | # make debugging problems painful if done without care. 1485 | # 1486 | # Don't enable this option unless you're sure that you really 1487 | # need it. 1488 | # 1489 | # Examples: 1490 | # 1491 | # allow-cgi-request-crunching 1 1492 | # 1493 | allow-cgi-request-crunching 0 1494 | # 1495 | # 6.3. split-large-forms 1496 | # ======================= 1497 | # 1498 | # Specifies: 1499 | # 1500 | # Whether the CGI interface should stay compatible with broken 1501 | # HTTP clients. 1502 | # 1503 | # Type of value: 1504 | # 1505 | # 0 or 1 1506 | # 1507 | # Default value: 1508 | # 1509 | # 0 1510 | # 1511 | # Effect if unset: 1512 | # 1513 | # The CGI form generate long GET URLs. 1514 | # 1515 | # Notes: 1516 | # 1517 | # Privoxy's CGI forms can lead to rather long URLs. This isn't a 1518 | # problem as far as the HTTP standard is concerned, but it can 1519 | # confuse clients with arbitrary URL length limitations. 1520 | # 1521 | # Enabling split-large-forms causes Privoxy to divide big forms 1522 | # into smaller ones to keep the URL length down. It makes 1523 | # editing a lot less convenient and you can no longer submit all 1524 | # changes at once, but at least it works around this browser 1525 | # bug. 1526 | # 1527 | # If you don't notice any editing problems, there is no reason 1528 | # to enable this option, but if one of the submit buttons 1529 | # appears to be broken, you should give it a try. 1530 | # 1531 | # Examples: 1532 | # 1533 | # split-large-forms 1 1534 | # 1535 | split-large-forms 0 1536 | # 1537 | # 6.4. keep-alive-timeout 1538 | # ======================== 1539 | # 1540 | # Specifies: 1541 | # 1542 | # Number of seconds after which an open connection will no 1543 | # longer be reused. 1544 | # 1545 | # Type of value: 1546 | # 1547 | # Time in seconds. 1548 | # 1549 | # Default value: 1550 | # 1551 | # None 1552 | # 1553 | # Effect if unset: 1554 | # 1555 | # Connections are not kept alive. 1556 | # 1557 | # Notes: 1558 | # 1559 | # This option allows clients to keep the connection to Privoxy 1560 | # alive. If the server supports it, Privoxy will keep the 1561 | # connection to the server alive as well. Under certain 1562 | # circumstances this may result in speed-ups. 1563 | # 1564 | # By default, Privoxy will close the connection to the server if 1565 | # the client connection gets closed, or if the specified timeout 1566 | # has been reached without a new request coming in. This 1567 | # behaviour can be changed with the connection-sharing option. 1568 | # 1569 | # This option has no effect if Privoxy has been compiled without 1570 | # keep-alive support. 1571 | # 1572 | # Note that a timeout of five seconds as used in the default 1573 | # configuration file significantly decreases the number of 1574 | # connections that will be reused. The value is used because 1575 | # some browsers limit the number of connections they open to a 1576 | # single host and apply the same limit to proxies. This can 1577 | # result in a single website "grabbing" all the connections the 1578 | # browser allows, which means connections to other websites 1579 | # can't be opened until the connections currently in use time 1580 | # out. 1581 | # 1582 | # Several users have reported this as a Privoxy bug, so the 1583 | # default value has been reduced. Consider increasing it to 300 1584 | # seconds or even more if you think your browser can handle it. 1585 | # If your browser appears to be hanging, it probably can't. 1586 | # 1587 | # Examples: 1588 | # 1589 | # keep-alive-timeout 300 1590 | # 1591 | keep-alive-timeout 5 1592 | # 1593 | # 6.5. tolerate-pipelining 1594 | # ========================= 1595 | # 1596 | # Specifies: 1597 | # 1598 | # Whether or not pipelined requests should be served. 1599 | # 1600 | # Type of value: 1601 | # 1602 | # 0 or 1. 1603 | # 1604 | # Default value: 1605 | # 1606 | # None 1607 | # 1608 | # Effect if unset: 1609 | # 1610 | # If Privoxy receives more than one request at once, it 1611 | # terminates the client connection after serving the first one. 1612 | # 1613 | # Notes: 1614 | # 1615 | # Privoxy currently doesn't pipeline outgoing requests, thus 1616 | # allowing pipelining on the client connection is not guaranteed 1617 | # to improve the performance. 1618 | # 1619 | # By default Privoxy tries to discourage clients from pipelining 1620 | # by discarding aggressively pipelined requests, which forces 1621 | # the client to resend them through a new connection. 1622 | # 1623 | # This option lets Privoxy tolerate pipelining. Whether or not 1624 | # that improves performance mainly depends on the client 1625 | # configuration. 1626 | # 1627 | # If you are seeing problems with pages not properly loading, 1628 | # disabling this option could work around the problem. 1629 | # 1630 | # Examples: 1631 | # 1632 | # tolerate-pipelining 1 1633 | # 1634 | tolerate-pipelining 1 1635 | # 1636 | # 6.6. default-server-timeout 1637 | # ============================ 1638 | # 1639 | # Specifies: 1640 | # 1641 | # Assumed server-side keep-alive timeout if not specified by the 1642 | # server. 1643 | # 1644 | # Type of value: 1645 | # 1646 | # Time in seconds. 1647 | # 1648 | # Default value: 1649 | # 1650 | # None 1651 | # 1652 | # Effect if unset: 1653 | # 1654 | # Connections for which the server didn't specify the keep-alive 1655 | # timeout are not reused. 1656 | # 1657 | # Notes: 1658 | # 1659 | # Enabling this option significantly increases the number of 1660 | # connections that are reused, provided the keep-alive-timeout 1661 | # option is also enabled. 1662 | # 1663 | # While it also increases the number of connections problems 1664 | # when Privoxy tries to reuse a connection that already has been 1665 | # closed on the server side, or is closed while Privoxy is 1666 | # trying to reuse it, this should only be a problem if it 1667 | # happens for the first request sent by the client. If it 1668 | # happens for requests on reused client connections, Privoxy 1669 | # will simply close the connection and the client is supposed to 1670 | # retry the request without bothering the user. 1671 | # 1672 | # Enabling this option is therefore only recommended if the 1673 | # connection-sharing option is disabled. 1674 | # 1675 | # It is an error to specify a value larger than the 1676 | # keep-alive-timeout value. 1677 | # 1678 | # This option has no effect if Privoxy has been compiled without 1679 | # keep-alive support. 1680 | # 1681 | # Examples: 1682 | # 1683 | # default-server-timeout 60 1684 | # 1685 | #default-server-timeout 60 1686 | # 1687 | # 6.7. connection-sharing 1688 | # ======================== 1689 | # 1690 | # Specifies: 1691 | # 1692 | # Whether or not outgoing connections that have been kept alive 1693 | # should be shared between different incoming connections. 1694 | # 1695 | # Type of value: 1696 | # 1697 | # 0 or 1 1698 | # 1699 | # Default value: 1700 | # 1701 | # None 1702 | # 1703 | # Effect if unset: 1704 | # 1705 | # Connections are not shared. 1706 | # 1707 | # Notes: 1708 | # 1709 | # This option has no effect if Privoxy has been compiled without 1710 | # keep-alive support, or if it's disabled. 1711 | # 1712 | # Notes: 1713 | # 1714 | # Note that reusing connections doesn't necessary cause 1715 | # speedups. There are also a few privacy implications you should 1716 | # be aware of. 1717 | # 1718 | # If this option is effective, outgoing connections are shared 1719 | # between clients (if there are more than one) and closing the 1720 | # browser that initiated the outgoing connection does no longer 1721 | # affect the connection between Privoxy and the server unless 1722 | # the client's request hasn't been completed yet. 1723 | # 1724 | # If the outgoing connection is idle, it will not be closed 1725 | # until either Privoxy's or the server's timeout is reached. 1726 | # While it's open, the server knows that the system running 1727 | # Privoxy is still there. 1728 | # 1729 | # If there are more than one client (maybe even belonging to 1730 | # multiple users), they will be able to reuse each others 1731 | # connections. This is potentially dangerous in case of 1732 | # authentication schemes like NTLM where only the connection is 1733 | # authenticated, instead of requiring authentication for each 1734 | # request. 1735 | # 1736 | # If there is only a single client, and if said client can keep 1737 | # connections alive on its own, enabling this option has next to 1738 | # no effect. If the client doesn't support connection 1739 | # keep-alive, enabling this option may make sense as it allows 1740 | # Privoxy to keep outgoing connections alive even if the client 1741 | # itself doesn't support it. 1742 | # 1743 | # You should also be aware that enabling this option increases 1744 | # the likelihood of getting the "No server or forwarder data" 1745 | # error message, especially if you are using a slow connection 1746 | # to the Internet. 1747 | # 1748 | # This option should only be used by experienced users who 1749 | # understand the risks and can weight them against the benefits. 1750 | # 1751 | # Examples: 1752 | # 1753 | # connection-sharing 1 1754 | # 1755 | #connection-sharing 1 1756 | # 1757 | # 6.8. socket-timeout 1758 | # ==================== 1759 | # 1760 | # Specifies: 1761 | # 1762 | # Number of seconds after which a socket times out if no data is 1763 | # received. 1764 | # 1765 | # Type of value: 1766 | # 1767 | # Time in seconds. 1768 | # 1769 | # Default value: 1770 | # 1771 | # None 1772 | # 1773 | # Effect if unset: 1774 | # 1775 | # A default value of 300 seconds is used. 1776 | # 1777 | # Notes: 1778 | # 1779 | # The default is quite high and you probably want to reduce it. 1780 | # If you aren't using an occasionally slow proxy like Tor, 1781 | # reducing it to a few seconds should be fine. 1782 | # 1783 | # Examples: 1784 | # 1785 | # socket-timeout 300 1786 | # 1787 | socket-timeout 300 1788 | # 1789 | # 6.9. max-client-connections 1790 | # ============================ 1791 | # 1792 | # Specifies: 1793 | # 1794 | # Maximum number of client connections that will be served. 1795 | # 1796 | # Type of value: 1797 | # 1798 | # Positive number. 1799 | # 1800 | # Default value: 1801 | # 1802 | # 128 1803 | # 1804 | # Effect if unset: 1805 | # 1806 | # Connections are served until a resource limit is reached. 1807 | # 1808 | # Notes: 1809 | # 1810 | # Privoxy creates one thread (or process) for every incoming 1811 | # client connection that isn't rejected based on the access 1812 | # control settings. 1813 | # 1814 | # If the system is powerful enough, Privoxy can theoretically 1815 | # deal with several hundred (or thousand) connections at the 1816 | # same time, but some operating systems enforce resource limits 1817 | # by shutting down offending processes and their default limits 1818 | # may be below the ones Privoxy would require under heavy load. 1819 | # 1820 | # Configuring Privoxy to enforce a connection limit below the 1821 | # thread or process limit used by the operating system makes 1822 | # sure this doesn't happen. Simply increasing the operating 1823 | # system's limit would work too, but if Privoxy isn't the only 1824 | # application running on the system, you may actually want to 1825 | # limit the resources used by Privoxy. 1826 | # 1827 | # If Privoxy is only used by a single trusted user, limiting the 1828 | # number of client connections is probably unnecessary. If there 1829 | # are multiple possibly untrusted users you probably still want 1830 | # to additionally use a packet filter to limit the maximal 1831 | # number of incoming connections per client. Otherwise a 1832 | # malicious user could intentionally create a high number of 1833 | # connections to prevent other users from using Privoxy. 1834 | # 1835 | # Obviously using this option only makes sense if you choose a 1836 | # limit below the one enforced by the operating system. 1837 | # 1838 | # One most POSIX-compliant systems Privoxy can't properly deal 1839 | # with more than FD_SETSIZE file descriptors at the same time 1840 | # and has to reject connections if the limit is reached. This 1841 | # will likely change in a future version, but currently this 1842 | # limit can't be increased without recompiling Privoxy with a 1843 | # different FD_SETSIZE limit. 1844 | # 1845 | # Examples: 1846 | # 1847 | # max-client-connections 256 1848 | # 1849 | #max-client-connections 256 1850 | # 1851 | # 6.10. handle-as-empty-doc-returns-ok 1852 | # ===================================== 1853 | # 1854 | # Specifies: 1855 | # 1856 | # The status code Privoxy returns for pages blocked with 1857 | # +handle-as-empty-document. 1858 | # 1859 | # Type of value: 1860 | # 1861 | # 0 or 1 1862 | # 1863 | # Default value: 1864 | # 1865 | # 0 1866 | # 1867 | # Effect if unset: 1868 | # 1869 | # Privoxy returns a status 403(forbidden) for all blocked pages. 1870 | # 1871 | # Effect if set: 1872 | # 1873 | # Privoxy returns a status 200(OK) for pages blocked with 1874 | # +handle-as-empty-document and a status 403(Forbidden) for all 1875 | # other blocked pages. 1876 | # 1877 | # Notes: 1878 | # 1879 | # This directive was added as a work-around for Firefox bug 1880 | # 492459: "Websites are no longer rendered if SSL requests for 1881 | # JavaScripts are blocked by a proxy." 1882 | # (https://bugzilla.mozilla.org/show_bug.cgi?id=492459), the bug 1883 | # has been fixed for quite some time, but this directive is also 1884 | # useful to make it harder for websites to detect whether or not 1885 | # resources are being blocked. 1886 | # 1887 | #handle-as-empty-doc-returns-ok 1 1888 | # 1889 | # 6.11. enable-compression 1890 | # ========================= 1891 | # 1892 | # Specifies: 1893 | # 1894 | # Whether or not buffered content is compressed before delivery. 1895 | # 1896 | # Type of value: 1897 | # 1898 | # 0 or 1 1899 | # 1900 | # Default value: 1901 | # 1902 | # 0 1903 | # 1904 | # Effect if unset: 1905 | # 1906 | # Privoxy does not compress buffered content. 1907 | # 1908 | # Effect if set: 1909 | # 1910 | # Privoxy compresses buffered content before delivering it to 1911 | # the client, provided the client supports it. 1912 | # 1913 | # Notes: 1914 | # 1915 | # This directive is only supported if Privoxy has been compiled 1916 | # with FEATURE_COMPRESSION, which should not to be confused with 1917 | # FEATURE_ZLIB. 1918 | # 1919 | # Compressing buffered content is mainly useful if Privoxy and 1920 | # the client are running on different systems. If they are 1921 | # running on the same system, enabling compression is likely to 1922 | # slow things down. If you didn't measure otherwise, you should 1923 | # assume that it does and keep this option disabled. 1924 | # 1925 | # Privoxy will not compress buffered content below a certain 1926 | # length. 1927 | # 1928 | #enable-compression 1 1929 | # 1930 | # 6.12. compression-level 1931 | # ======================== 1932 | # 1933 | # Specifies: 1934 | # 1935 | # The compression level that is passed to the zlib library when 1936 | # compressing buffered content. 1937 | # 1938 | # Type of value: 1939 | # 1940 | # Positive number ranging from 0 to 9. 1941 | # 1942 | # Default value: 1943 | # 1944 | # 1 1945 | # 1946 | # Notes: 1947 | # 1948 | # Compressing the data more takes usually longer than 1949 | # compressing it less or not compressing it at all. Which level 1950 | # is best depends on the connection between Privoxy and the 1951 | # client. If you can't be bothered to benchmark it for yourself, 1952 | # you should stick with the default and keep compression 1953 | # disabled. 1954 | # 1955 | # If compression is disabled, the compression level is 1956 | # irrelevant. 1957 | # 1958 | # Examples: 1959 | # 1960 | # # Best speed (compared to the other levels) 1961 | # compression-level 1 1962 | # 1963 | # # Best compression 1964 | # compression-level 9 1965 | # 1966 | # # No compression. Only useful for testing as the added header 1967 | # # slightly increases the amount of data that has to be sent. 1968 | # # If your benchmark shows that using this compression level 1969 | # # is superior to using no compression at all, the benchmark 1970 | # # is likely to be flawed. 1971 | # compression-level 0 1972 | # 1973 | # 1974 | #compression-level 1 1975 | # 1976 | # 6.13. client-header-order 1977 | # ========================== 1978 | # 1979 | # Specifies: 1980 | # 1981 | # The order in which client headers are sorted before forwarding 1982 | # them. 1983 | # 1984 | # Type of value: 1985 | # 1986 | # Client header names delimited by spaces or tabs 1987 | # 1988 | # Default value: 1989 | # 1990 | # None 1991 | # 1992 | # Notes: 1993 | # 1994 | # By default Privoxy leaves the client headers in the order they 1995 | # were sent by the client. Headers are modified in-place, new 1996 | # headers are added at the end of the already existing headers. 1997 | # 1998 | # The header order can be used to fingerprint client requests 1999 | # independently of other headers like the User-Agent. 2000 | # 2001 | # This directive allows to sort the headers differently to 2002 | # better mimic a different User-Agent. Client headers will be 2003 | # emitted in the order given, headers whose name isn't 2004 | # explicitly specified are added at the end. 2005 | # 2006 | # Note that sorting headers in an uncommon way will make 2007 | # fingerprinting actually easier. Encrypted headers are not 2008 | # affected by this directive. 2009 | # 2010 | #client-header-order Host \ 2011 | # Accept \ 2012 | # Accept-Language \ 2013 | # Accept-Encoding \ 2014 | # Proxy-Connection \ 2015 | # Referer \ 2016 | # Cookie \ 2017 | # DNT \ 2018 | # If-Modified-Since \ 2019 | # Cache-Control \ 2020 | # Content-Length \ 2021 | # Content-Type 2022 | # 2023 | # 2024 | # 7. WINDOWS GUI OPTIONS 2025 | # ======================= 2026 | # 2027 | # Privoxy has a number of options specific to the Windows GUI 2028 | # interface: 2029 | # 2030 | # 2031 | # 2032 | # If "activity-animation" is set to 1, the Privoxy icon will animate 2033 | # when "Privoxy" is active. To turn off, set to 0. 2034 | # 2035 | activity-animation 1 2036 | # 2037 | # 2038 | # 2039 | # If "log-messages" is set to 1, Privoxy copies log messages to the 2040 | # console window. The log detail depends on the debug directive. 2041 | # 2042 | #log-messages 1 2043 | # 2044 | # 2045 | # 2046 | # If "log-buffer-size" is set to 1, the size of the log buffer, i.e. 2047 | # the amount of memory used for the log messages displayed in the 2048 | # console window, will be limited to "log-max-lines" (see below). 2049 | # 2050 | # Warning: Setting this to 0 will result in the buffer to grow 2051 | # infinitely and eat up all your memory! 2052 | # 2053 | #log-buffer-size 1 2054 | # 2055 | # 2056 | # 2057 | # log-max-lines is the maximum number of lines held in the log 2058 | # buffer. See above. 2059 | # 2060 | #log-max-lines 200 2061 | # 2062 | # 2063 | # 2064 | # If "log-highlight-messages" is set to 1, Privoxy will highlight 2065 | # portions of the log messages with a bold-faced font: 2066 | # 2067 | #log-highlight-messages 1 2068 | # 2069 | # 2070 | # 2071 | # The font used in the console window: 2072 | # 2073 | #log-font-name Comic Sans MS 2074 | # 2075 | # 2076 | # 2077 | # Font size used in the console window: 2078 | # 2079 | #log-font-size 8 2080 | # 2081 | # 2082 | # 2083 | # "show-on-task-bar" controls whether or not Privoxy will appear as 2084 | # a button on the Task bar when minimized: 2085 | # 2086 | show-on-task-bar 1 2087 | # 2088 | # 2089 | # 2090 | # If "close-button-minimizes" is set to 1, the Windows close button 2091 | # will minimize Privoxy instead of closing the program (close with 2092 | # the exit option on the File menu). 2093 | # 2094 | #close-button-minimizes 1 2095 | # 2096 | # 2097 | # 2098 | # The "hide-console" option is specific to the MS-Win console 2099 | # version of Privoxy. If this option is used, Privoxy will 2100 | # disconnect from and hide the command console. 2101 | # 2102 | #hide-console 2103 | # 2104 | # 2105 | forward / localhost:8123 2106 | -------------------------------------------------------------------------------- /tor/torrc: -------------------------------------------------------------------------------- 1 | VirtualAddrNetwork 10.192.0.0/10 2 | #define a non-standard ports to not conflicts with other tor instances 3 | TransPort 127.0.0.1:9040 IsolateClientAddr IsolateSOCKSAuth IsolateClientProtocol IsolateDestPort IsolateDestAddr 4 | SocksPort 127.0.0.1:9050 IsolateClientAddr IsolateSOCKSAuth IsolateClientProtocol IsolateDestPort IsolateDestAddr 5 | DNSPort 127.0.0.1:53 6 | AutomapHostsOnResolve 1 7 | AutomapHostsSuffixes .exit,.onion 8 | #daemonize 9 | RunAsDaemon 1 10 | #sandbox 11 | Sandbox 1 12 | #use hardware accaleration when possible for crypto 13 | HardwareAccel 1 14 | #socket safety hacks 15 | TestSocks 1 16 | WarnUnsafeSocks 1 17 | AllowNonRFC953Hostnames 0 18 | AllowDotExit 0 19 | WarnPlaintextPorts 23,109,110,143,80 20 | #dns safety hacks 21 | ClientRejectInternalAddresses 1 22 | #circuit hacks 23 | NewCircuitPeriod 40 24 | MaxCircuitDirtiness 600 25 | MaxClientCircuitsPending 48 26 | UseEntryGuards 1 27 | UseEntryGuardsAsDirGuards 1 28 | EnforceDistinctSubnets 1 29 | #ok, it is a bit complex, so i will spend more words here: 30 | #this option means that tor will try to use the previously used 31 | #exit node for these domains, this is helpful in case of 32 | #websites with sessions related to your IP that may change 33 | #their behavior if your ip changes, but this option may help 34 | #websites to associate all your actions to a single 35 | #navigation session, by watching your IP. 36 | # 37 | #We decided to use it for the following addresses 38 | #because they track you anyway by using cookies 39 | #(so they will know who you are wven if you 40 | #change IP), so we decided to use the IP of the 41 | #same exit node in order to not let these services 42 | #map your exit nodes pool, so they will know 43 | #only one of the exit nodes in your pool. 44 | TrackHostExits .facebook.com,.facebook.net,.twitter.com,.fbcdn.com,.fbcdn.net,.akamaihd.com,.google.com,.google.it,.google.fr,.google.de,.google.br,.yandex.ru,.yandex.com,.gmail.com,.googleapis.com,.gstatic.com,.adform.net,.google-analitics.com,.googletagservices.com 45 | ExcludeNodes {US},{FR},{UK},{GB} 46 | ExitNodes 217.115.10.132,217.115.10.131,{kp},{af},{dz},{cu},{gm},{ht},{is},{mr},{ng},{ru},{vn},{so} 47 | StrictNodes 1 48 | -------------------------------------------------------------------------------- /usr/anOFF: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | export BLUE='\033[1;94m' 4 | export GREEN='\033[1;92m' 5 | export RED='\033[1;91m' 6 | export RESETCOLOR='\033[1;00m' 7 | 8 | anonym8 stop 9 | sleep 25 10 | anonym8 stop_privoxy 11 | sleep 2 12 | anonym8 stop_polipo 13 | sleep 2 14 | anonym8 stop_mac 15 | sleep 3 16 | anonym8 wipe 17 | sleep 3 18 | anonym8 status_ip 19 | sleep 3 20 | 21 | echo " _ _ ___ ____" 22 | echo " _| || |_ / _ \ / __ \ " 23 | echo "|_ __ _/ /_\ \_ __ ___ _ ____ __ _ __ __ | | | | " 24 | echo " | || |_| _ | '_ \ / _ \| '_ \ \/ /| '_ ' _ \ |__| / " 25 | echo "|_ __ _| | | | | | | (_) | | | \ / | | | | |/ ____ \ " 26 | echo " |_||_| \_| |_|_| |_|\___/|_| |_|__| |_| |_| | | | | " 27 | echo " | |____| | " 28 | echo " \______/ " 29 | echo " ...Privacy Friend..." 30 | sleep 03 31 | echo -e '\E[31m'" _____________________________________________ "; tput sgr0 32 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 33 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 34 | echo -e '\E[31m'" ||\E[37m ███████▓█████▓▓╬╬╬╬╬╬╬╬▓███▓╬╬╬╬╬╬╬▓╬╬▓█ \E[31m|| "; tput sgr0 35 | echo -e '\E[31m'" ||\E[37m ████▓▓▓▓╬╬▓█████╬╬╬╬╬╬███▓╬╬╬╬╬╬╬╬╬╬╬╬╬█ \E[31m|| "; tput sgr0 36 | echo -e '\E[31m'" ||\E[37m ███▓▓▓▓╬╬╬╬╬╬▓██╬╬╬╬╬╬▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 37 | echo -e '\E[31m'" ||\E[37m ████▓▓▓╬╬╬╬╬╬╬▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 38 | echo -e '\E[31m'" ||\E[37m ███▓█▓███████▓▓███▓╬╬╬╬╬╬▓███████▓╬╬╬╬▓█ \E[31m|| "; tput sgr0 39 | echo -e '\E[31m'" ||\E[37m ████████████████▓█▓╬╬╬╬╬▓▓▓▓▓▓▓▓╬╬╬╬╬╬╬█ \E[31m|| "; tput sgr0 40 | echo -e '\E[31m'" ||\E[37m ███▓▓▓▓▓▓▓╬╬▓▓▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 41 | sleep 1 42 | echo -e '\E[31m'" ||\E[37m ████▓▓▓╬╬╬╬▓▓▓▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 43 | echo -e '\E[31m'" ||\E[37m ███▓█▓▓▓▓▓▓▓▓▓▓▓▓▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 44 | echo -e '\E[31m'" ||\E[37m █████▓▓▓▓▓▓▓▓█▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 45 | echo -e '\E[31m'" ||\E[37m █████▓▓▓▓▓▓▓██▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬██ \E[31m|| "; tput sgr0 46 | echo -e '\E[31m'" ||\E[37m █████▓▓▓▓▓████▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬██ \E[31m|| "; tput sgr0 47 | echo -e '\E[31m'" ||\E[37m ████▓█▓▓▓▓██▓▓▓▓██╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬██ \E[31m|| "; tput sgr0 48 | echo -e '\E[31m'" ||\E[37m ████▓▓███▓▓▓▓▓▓▓██▓╬╬╬╬╬╬╬╬╬╬╬╬█▓╬▓╬╬▓██ \E[31m|| "; tput sgr0 49 | sleep 1 50 | echo -e '\E[31m'" ||\E[37m █████▓███▓▓▓▓▓▓▓▓████▓▓╬╬╬╬╬╬╬█▓╬╬╬╬╬▓██ \E[31m|| "; tput sgr0 51 | echo -e '\E[31m'" ||\E[37m █████▓▓█▓███▓▓▓████╬▓█▓▓╬╬╬▓▓█▓╬╬╬╬╬╬███ \E[31m|| "; tput sgr0 52 | echo -e '\E[31m'" ||\E[37m ██████▓██▓███████▓╬╬╬▓▓╬▓▓██▓╬╬╬╬╬╬╬▓███ \E[31m|| "; tput sgr0 53 | echo -e '\E[31m'" ||\E[37m ███████▓██▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓╬╬╬╬╬╬╬╬╬╬╬████ \E[31m|| "; tput sgr0 54 | echo -e '\E[31m'" ||\E[37m ███████▓▓██▓▓▓▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓████ \E[31m|| "; tput sgr0 55 | echo -e '\E[31m'" ||\E[37m ████████▓▓▓█████▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█████ \E[31m|| "; tput sgr0 56 | echo -e '\E[31m'" ||\E[37m █████████▓▓▓█▓▓▓▓▓███▓╬╬╬╬╬╬╬╬╬╬╬▓██████ \E[31m|| "; tput sgr0 57 | sleep 1 58 | echo -e '\E[31m'" ||\E[37m ██████████▓▓▓█▓▓▓╬▓██╬╬╬╬╬╬╬╬╬╬╬▓███████ \E[31m|| "; tput sgr0 59 | echo -e '\E[31m'" ||\E[37m ███████████▓▓█▓▓▓▓███▓╬╬╬╬╬╬╬╬╬▓████████ \E[31m|| "; tput sgr0 60 | echo -e '\E[31m'" ||\E[37m ██████████████▓▓▓███▓▓╬╬╬╬╬╬╬╬██████████ \E[31m|| "; tput sgr0 61 | echo -e '\E[31m'" ||\E[37m ███████████████▓▓▓██▓▓╬╬╬╬╬╬▓███████████ \E[31m|| "; tput sgr0 62 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 63 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 64 | echo -e '\E[31m'" ||__________________________________________|| "; tput sgr0 65 | sleep 3 66 | echo -e " anonym8 (v 1.0) Usage Ex:\n 67 | $RED anON$BLUE =>$GREEN automated protection [ON] 68 | $RED anOFF$BLUE =>$GREEN automated protection$RED [OFF]\n 69 | $RED ADVANCED COMMANDS LIST:\n 70 | $RED┌──[$GREEN$USER$RED@$BLUE`hostname`$RED]─[$GREEN$PWD$RED] 71 | $RED└──╼ $GREEN"anonym8" $RED{$GREEN"start"$RED|$GREEN"stop"$RED|$GREEN"change"$RED|$GREEN"status..."$RED}\n 72 | $BLUE----[ Tor Tunneling related features ]---- 73 | $RED anonym8 start$BLUE =>$GREEN Start Tor Tunneling 74 | $RED anonym8 stop$BLUE =>$GREEN Stop Tor Tunneling 75 | $RED anonym8 change$BLUE =>$GREEN Changes identity restarting TOR 76 | $RED anonym8 status$BLUE =>$GREEN Tor Tunneling Status\n 77 | $BLUE----[ IP related features ]---- 78 | $RED anonym8 status_ip$BLUE =>$GREEN IP status\n 79 | $BLUE----[ I2P related features ]---- 80 | $RED anonym8 start_i2p$BLUE =>$GREEN Start i2p services 81 | $RED anonym8 stop_i2p$BLUE =>$GREEN Stop i2p services 82 | $RED anonym8 status_i2p$BLUE =>$GREEN i2p status\n 83 | $BLUE----[ privoxy related features ]---- 84 | $RED anonym8 start_privoxy$BLUE =>$GREEN Start privoxy services 85 | $RED anonym8 stop_privoxy$BLUE =>$GREEN Stop privoxy services 86 | $RED anonym8 status_privoxy$BLUE =>$GREEN privoxy status\n 87 | $BLUE----[ polipo related features ]---- 88 | $RED anonym8 start_polipo$BLUE =>$GREEN Start polipo services 89 | $RED anonym8 stop_polipo$BLUE =>$GREEN Stop polipo services 90 | $RED anonym8 status_polipo$BLUE =>$GREEN Polipo status\n 91 | $BLUE----[ macchanger related features ]---- 92 | $RED anonym8 start_mac$BLUE =>$GREEN Start macchanger services 93 | $RED anonym8 stop_mac$BLUE =>$GREEN Stop macchanger services 94 | $RED anonym8 status_mac$BLUE =>$GREEN macchanger status\n 95 | $BLUE----[ arm related features ]---- 96 | $RED anonym8 start_arm$BLUE =>$GREEN Start Monitoring Anonymizing Relay (arm)\n 97 | $BLUE----[ wipe related features ]---- 98 | $RED anonym8 wipe$BLUE =>$GREEN cache, RAM & swap-space cleaner\n 99 | $BLUE----[ hostname related features ]---- 100 | $RED anonym8 change_hostname$BLUE =>$GREEN Randomly Spoofing Hostname 101 | $RED anonym8 restore_hostname$BLUE =>$GREEN Restore Default Hostname 102 | $RED anonym8 status_hostname$BLUE =>$GREEN Show Current Hostname\n 103 | 104 | $RESETCOLOR" 105 | -------------------------------------------------------------------------------- /usr/anON: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | export BLUE='\033[1;94m' 4 | export GREEN='\033[1;92m' 5 | export RED='\033[1;91m' 6 | export RESETCOLOR='\033[1;00m' 7 | 8 | anonym8 wipe 9 | sleep 3 10 | anonym8 start_mac 11 | sleep 3 12 | anonym8 start_polipo 13 | sleep 2 14 | anonym8 start_privoxy 15 | sleep 2 16 | anonym8 start 17 | sleep 25 18 | anonym8 status_ip 19 | sleep 3 20 | 21 | echo " _ _ ___ ____" 22 | echo " _| || |_ / _ \ / __ \ " 23 | echo "|_ __ _/ /_\ \_ __ ___ _ ____ __ _ __ __ | | | | " 24 | echo " | || |_| _ | '_ \ / _ \| '_ \ \/ /| '_ ' _ \ |__| / " 25 | echo "|_ __ _| | | | | | | (_) | | | \ / | | | | |/ ____ \ " 26 | echo " |_||_| \_| |_|_| |_|\___/|_| |_|__| |_| |_| | | | | " 27 | echo " | |____| | " 28 | echo " \______/ " 29 | echo " ...Privacy Friend..." 30 | sleep 03 31 | echo -e '\E[31m'" _____________________________________________ "; tput sgr0 32 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 33 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 34 | echo -e '\E[31m'" ||\E[37m ███████▓█████▓▓╬╬╬╬╬╬╬╬▓███▓╬╬╬╬╬╬╬▓╬╬▓█ \E[31m|| "; tput sgr0 35 | echo -e '\E[31m'" ||\E[37m ████▓▓▓▓╬╬▓█████╬╬╬╬╬╬███▓╬╬╬╬╬╬╬╬╬╬╬╬╬█ \E[31m|| "; tput sgr0 36 | echo -e '\E[31m'" ||\E[37m ███▓▓▓▓╬╬╬╬╬╬▓██╬╬╬╬╬╬▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 37 | echo -e '\E[31m'" ||\E[37m ████▓▓▓╬╬╬╬╬╬╬▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 38 | echo -e '\E[31m'" ||\E[37m ███▓█▓███████▓▓███▓╬╬╬╬╬╬▓███████▓╬╬╬╬▓█ \E[31m|| "; tput sgr0 39 | echo -e '\E[31m'" ||\E[37m ████████████████▓█▓╬╬╬╬╬▓▓▓▓▓▓▓▓╬╬╬╬╬╬╬█ \E[31m|| "; tput sgr0 40 | echo -e '\E[31m'" ||\E[37m ███▓▓▓▓▓▓▓╬╬▓▓▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 41 | sleep 1 42 | echo -e '\E[31m'" ||\E[37m ████▓▓▓╬╬╬╬▓▓▓▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 43 | echo -e '\E[31m'" ||\E[37m ███▓█▓▓▓▓▓▓▓▓▓▓▓▓▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 44 | echo -e '\E[31m'" ||\E[37m █████▓▓▓▓▓▓▓▓█▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█ \E[31m|| "; tput sgr0 45 | echo -e '\E[31m'" ||\E[37m █████▓▓▓▓▓▓▓██▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬██ \E[31m|| "; tput sgr0 46 | echo -e '\E[31m'" ||\E[37m █████▓▓▓▓▓████▓▓▓█▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬██ \E[31m|| "; tput sgr0 47 | echo -e '\E[31m'" ||\E[37m ████▓█▓▓▓▓██▓▓▓▓██╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬██ \E[31m|| "; tput sgr0 48 | echo -e '\E[31m'" ||\E[37m ████▓▓███▓▓▓▓▓▓▓██▓╬╬╬╬╬╬╬╬╬╬╬╬█▓╬▓╬╬▓██ \E[31m|| "; tput sgr0 49 | sleep 1 50 | echo -e '\E[31m'" ||\E[37m █████▓███▓▓▓▓▓▓▓▓████▓▓╬╬╬╬╬╬╬█▓╬╬╬╬╬▓██ \E[31m|| "; tput sgr0 51 | echo -e '\E[31m'" ||\E[37m █████▓▓█▓███▓▓▓████╬▓█▓▓╬╬╬▓▓█▓╬╬╬╬╬╬███ \E[31m|| "; tput sgr0 52 | echo -e '\E[31m'" ||\E[37m ██████▓██▓███████▓╬╬╬▓▓╬▓▓██▓╬╬╬╬╬╬╬▓███ \E[31m|| "; tput sgr0 53 | echo -e '\E[31m'" ||\E[37m ███████▓██▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓╬╬╬╬╬╬╬╬╬╬╬████ \E[31m|| "; tput sgr0 54 | echo -e '\E[31m'" ||\E[37m ███████▓▓██▓▓▓▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓████ \E[31m|| "; tput sgr0 55 | echo -e '\E[31m'" ||\E[37m ████████▓▓▓█████▓▓╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬╬▓█████ \E[31m|| "; tput sgr0 56 | echo -e '\E[31m'" ||\E[37m █████████▓▓▓█▓▓▓▓▓███▓╬╬╬╬╬╬╬╬╬╬╬▓██████ \E[31m|| "; tput sgr0 57 | sleep 1 58 | echo -e '\E[31m'" ||\E[37m ██████████▓▓▓█▓▓▓╬▓██╬╬╬╬╬╬╬╬╬╬╬▓███████ \E[31m|| "; tput sgr0 59 | echo -e '\E[31m'" ||\E[37m ███████████▓▓█▓▓▓▓███▓╬╬╬╬╬╬╬╬╬▓████████ \E[31m|| "; tput sgr0 60 | echo -e '\E[31m'" ||\E[37m ██████████████▓▓▓███▓▓╬╬╬╬╬╬╬╬██████████ \E[31m|| "; tput sgr0 61 | echo -e '\E[31m'" ||\E[37m ███████████████▓▓▓██▓▓╬╬╬╬╬╬▓███████████ \E[31m|| "; tput sgr0 62 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 63 | echo -e '\E[31m'" ||------------------------------------------|| "; tput sgr0 64 | echo -e '\E[31m'" ||__________________________________________|| "; tput sgr0 65 | sleep 3 66 | echo -e " anonym8 (v 1.0) Usage Ex:\n 67 | $RED anON$BLUE =>$GREEN automated protection [ON] 68 | $RED anOFF$BLUE =>$GREEN automated protection$RED [OFF]\n 69 | $RED ADVANCED COMMANDS LIST:\n 70 | $RED┌──[$GREEN$USER$RED@$BLUE`hostname`$RED]─[$GREEN$PWD$RED] 71 | $RED└──╼ $GREEN"anonym8" $RED{$GREEN"start"$RED|$GREEN"stop"$RED|$GREEN"change"$RED|$GREEN"status..."$RED}\n 72 | $BLUE----[ Tor Tunneling related features ]---- 73 | $RED anonym8 start$BLUE =>$GREEN Start Tor Tunneling 74 | $RED anonym8 stop$BLUE =>$GREEN Stop Tor Tunneling 75 | $RED anonym8 change$BLUE =>$GREEN Changes identity restarting TOR 76 | $RED anonym8 status$BLUE =>$GREEN Tor Tunneling Status\n 77 | $BLUE----[ IP related features ]---- 78 | $RED anonym8 status_ip$BLUE =>$GREEN IP status\n 79 | $BLUE----[ I2P related features ]---- 80 | $RED anonym8 start_i2p$BLUE =>$GREEN Start i2p services 81 | $RED anonym8 stop_i2p$BLUE =>$GREEN Stop i2p services 82 | $RED anonym8 status_i2p$BLUE =>$GREEN i2p status\n 83 | $BLUE----[ privoxy related features ]---- 84 | $RED anonym8 start_privoxy$BLUE =>$GREEN Start privoxy services 85 | $RED anonym8 stop_privoxy$BLUE =>$GREEN Stop privoxy services 86 | $RED anonym8 status_privoxy$BLUE =>$GREEN privoxy status\n 87 | $BLUE----[ polipo related features ]---- 88 | $RED anonym8 start_polipo$BLUE =>$GREEN Start polipo services 89 | $RED anonym8 stop_polipo$BLUE =>$GREEN Stop polipo services 90 | $RED anonym8 status_polipo$BLUE =>$GREEN Polipo status\n 91 | $BLUE----[ macchanger related features ]---- 92 | $RED anonym8 start_mac$BLUE =>$GREEN Start macchanger services 93 | $RED anonym8 stop_mac$BLUE =>$GREEN Stop macchanger services 94 | $RED anonym8 status_mac$BLUE =>$GREEN macchanger status\n 95 | $BLUE----[ arm related features ]---- 96 | $RED anonym8 start_arm$BLUE =>$GREEN Start Monitoring Anonymizing Relay (arm)\n 97 | $BLUE----[ wipe related features ]---- 98 | $RED anonym8 wipe$BLUE =>$GREEN cache, RAM & swap-space cleaner\n 99 | $BLUE----[ hostname related features ]---- 100 | $RED anonym8 change_hostname$BLUE =>$GREEN Randomly Spoofing Hostname 101 | $RED anonym8 restore_hostname$BLUE =>$GREEN Restore Default Hostname 102 | $RED anonym8 status_hostname$BLUE =>$GREEN Show Current Hostname\n 103 | 104 | $RESETCOLOR" 105 | -------------------------------------------------------------------------------- /usr/anonym8: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | 3 | /etc/init.d/anonym8.sh "$@" 4 | --------------------------------------------------------------------------------