Hot answers tagged

11

You're looking at it the wrong way. The no_proxy environment variable lists the domain suffixes, not the prefixes. From the documentation: no_proxy: This variable should contain a comma-separated list of domain extensions proxy should not be used for. So for IPs, you have two options: 1) Add each IP in full: printf -v no_proxy '%s,' ...


11

ssh -D 8080 name@myserver.com export http_proxy=socks5://127.0.0.1:8080 https_proxy=socks5://127.0.0.1:8080 youtube-dl youtube.com/watch?V=3XjwiV-6_CA


8

Most browsers enable you to get a warning if you have HTTP content on an HTTPS page. This can be very annoying if you visit sites that mix HTTP content on their HTTPS pages. From your question it appears Wikipedia is one of those. When properly set, Firefox warns me visiting this page. A web server is not required to offer HTTPS. Many sites do not ...


7

I think pretty much all linux/unix software that uses networking will honor the http_proxy and ftp_proxy environment variables. Depending on how your distribution is set up, /etc/environment will exist and be read by default by login shells. You can add a line saying http_proxy=123.45.67.89:1011 in /etc/environment easily enough, but changes in that file ...


7

1) Squid is a special proxy for http and https traffic. As it knows this protocol it can offer some advanced features like caching, filtering, rewrite rules, dns resolving. All web browsers know how to handle http proxies as it's part of that protocol spec. Additionally Squid can act as a transparent proxy where you don't configure your web browser to use ...


6

Youtube-dl doesn't support a SOCKS proxy. There's a feature request for it, with links to a couple of working proposals. Youtube-dl supports HTTP proxies out of the box. To benefit from this support, you'll need to run a proxy on myserver.com. Pretty much any lightweight proxy will do, for example tinyproxy. The proxy only needs to listen to local ...


6

Here are a couple: WebScarab: http://www.owasp.org/index.php/OWASP_WebScarab_Project Burp http://portswigger.net/proxy/


6

info wget says: `no_proxy' This variable should contain a comma-separated list of domain extensions proxy should _not_ be used for. For instance, if the value of `no_proxy' is `.mit.edu', proxy will not be used to retrieve documents from MIT. So the variable should contain a list of domains, not IP ranges. You'll need to set up ...


6

cntlm provides a solution, along with some configuration. The basic steps to follow are: Install cntlm. Edit its configuration file at /etc/cntlm.conf, the comments included makes it easy enough. Add a proxy server (or two). Specify your user name and NT domain name in the appropriate places, and remove the password entry. Start the cntlm service, eg ...


5

I agree that the best way to use the proxy server is with the environment variable http_proxy, as other answers have pointed out. Unfortunately, not all applications honour the http_proxy environment variable, which is why I still use tsocks for some programs to use LD_PRELOAD to force network connections to go through a SOCKS proxy.


4

Edit "/etc/apt/apt.conf" and add below entry: Acquire::http::Proxy "http://username:password@proxyhost:port/"; Reference Link


4

What is possible depends on what the firewall allows. If the firewall allows arbitrary traffic on port 443 Some firewalls take the simple way out and allow anything on port 443. If that's the case, the easiest way to reach your home server is to make it listen to SSH connections on port 443. If your machine is directly connected to the Internet, simply add ...


3

As mentioned previously this is not really load balancing, but it's possible. Try something like: frontend http-in bind *:80 # urls acl host_foo hdr(host) -i www.foo.com acl host_bar hdr(host) -i www.bar.com acl host_zoo hdr(host) -i www.zoo.com # clusters use_backend foo_cluster if host_foo use_backend bar_cluster if ...


3

With ssh -D 8080 yourserver you can start a SOCKS proxy to your home server. Configure your client to use localhost:8080 as SOCKS proxy. This method requires that port forwarding is enabled, see the AllowTcpForwarding directive in /etc/ssh/sshd_config. If you can not enable the TCP forwarding you might have a look at sshuttle. See ...


3

There is no central authority who assigns an official meaning to environment variables before applications can use them. POSIX defines the meaning of some variables (PATH, TERM, …) and lists several more in a non-normative way as being in common use, all of them in uppercase. http_proxy and friends isn't one of them. Unlike basically all conventional ...


3

Using base64 is useless, it's just a simple transformation. Using encryption with a key that's stored alongside the encrypted data is also useless because it's still just a simple transformation. If you're worried about someone getting access to your configuration files, then you need to encrypt with a key that isn't in your configuration files, and that ...


3

The reason why you need to redirect that URL rather than rewrite is because you are visiting an unencrypted web page with the http:// (plaintext) URL, and the proxy needs to tell the browser to talk to the https:// URL. If the connection was simply redirected at the SSL port, your browser wouldn't know what to do with an SSL response if it were somehow ...


3

You might be interested in HTTP Strict Transport Security sometimes called STS or HSTS. This is a voluntary header a web server can send out to instruct the web browser that the site must always be secure. Chrome is one of the browsers that implement it. http://www.imperialviolet.org/2011/02/17/hstsui.html I think you can add Wikipedia to the default ...


3

Did you try the following syntax ? http_proxy=http://address:port/ wget --proxy-user=USERNAME --proxy-password=PASSWORD http://url


3

Here's a slightly simpler (one-line) approach based on janmoesen's solution. export no_proxy=`echo 10.1.1.{1..255} | sed 's/ /,/g'` Unfortunately, sed chokes on all the arguments passed from the expansion of 10.1.{1..255}.{1..255}, either in his code or mine. So if you really need to expand to 256 * 256 IP addresses, you'll need a different approach, ...


3

Not having root privileges prevents you from listening on ports below 1024 on typical Linux systems. Thus, Squid should work OK as non-root listening on 8080 as long as the system you are on hasn't blocked incoming traffic on that port via a firewall or iptables. Not sure how many file descriptors Squid uses typically but if your admin has set a limit for ...


3

It seems to be related with environment variables. If you set the proxy in your profile (as environment variables), then probably when issuing sudo, these variables don't get loaded. If you succeed doing so with su, then probably you're using su - (that's the way to load the environment variables of root). To get loaded these variables (for a normal user) ...


2

You can't do this in a sane way for Google search queries. Why? Google is using HTTPS (SSL) everywhere now. All traffic between the endpoints (browser & Google server) is encrypted and checked for integrity. The only way to read (let alone modify) encrypted traffic is changing it at or beyond on one of the endpoints. Suggestions in the direction of ...


2

Caching https is hard to set up, sorry. You need to create a local CA certficate, and configure the client programs to accept it. I don't know what proxy software you'd have to use for it. Squid isn't great for caching large downloads. It doesn't support partial instances, i.e. resuming interrupted downloads. Polipo supports partial instances, and I ...


2

Get a 10/100 ethernet hub, a real hub, like a Netgear DS104. Put it between the wifi and the router. Hubs replicate traffic on all ports, so you can connect a separate machine to another port on the hub and sniff everything.


2

Your failing to reach XChat through the proxy because your proxy is specifically set to deny you this privilege. Talk to whoever configures or maintains the proxy and see if they'll allow this.


2

Unless your brand of router specifically allows for that kind of interception (most don't unless you're talking about industrial grade stuff with triple digit costs and usage licenses) I'm afraid you're sunk; a better bet might be to install a wifi card in your computer and try to sniff the wireless traffic directly using something like wireshark or Kismet. ...


2

Ports 80 and 443 are the standard ports for http and https, respectively. If you use these ports for your application (instead of port 5678) then you won't need to specify the port number in your URLs.


2

You don't need --uid-owner in PREROUTING, you need it in OUTPUT (like in your example).


2

If firefox uses the desired proxy, then you can get the Proxy's IP and port. As root: netstat -t -n -p | grep firefox



Only top voted, non community-wiki answers of a minimum length are eligible