I am trying to access a website which is blocked by ISP. When using tor browser integrated with tor browser bundle, I am able to access the website. But when I am using 127.0.0.1:9150 socks proxy setting in firefox, the ISP is able to detect the URL and blocking it. How to access the website from browser other than tor browser.
I solved the problem. Actually I was using ISP's DNS server. Tor browser has remote_dns property as true so it uses some other dns server while this property was false in Firefox. Hence the request from firefox to resolve hostname to ISP's dns server was blocked. When I set this property true in firefox, it was not blocking the site then.
Go to about:config in firefox
Search for network.proxy.socks_remote_dns and set it true
Related
I have a VPN that only connect through HTTPS on my browser with its extension. I'm using Windows 10 and I'm looking for a solution like Tor Browser that have a SOCKS5 proxy (127.0.0.1:9150) and other apps can use it to bypass censorship.
Is there any solution for Firefox, Chrome or any other browser that after connecting to VPN extension, other apps can use a SOCKS5 or HTTP proxy to connect through it?
I tried Proxifier and similar apps on Windows 10 and no luck. But official VPN browser extension and FoxyProxy work.
I tried different ISPs and I know my firewall is not the problem and VPN is connected on other ISPs.
VPN name: TorGuard
The best solution I found so far is to use v2rayA (https://v2raya.org/en/).
First you connect to your HTTPS proxy through this app and then you can use HTTP or SOCKS5 proxy that it gives you to connect other apps or use Proxifier (https://www.proxifier.com/download/) to tunnel all traffic.
P.S. The default address and port of v2rayA are:
HTTP 127.0.0.1:20171
SOCKS5 127.0.0.1:20170
I purchased a VPS server, installed IIS, setup domain and published static index.html page. It worked if I go to mydomain.com but 1 or 1.5 hours later it stopped working and I can only see the message The site can't be reached.
The VPS is accessible via Remote desktop and if I locally run the IE I can access mydomain.com but It does not work from outside of the VPS.
If I reboot the VPS server then after a while the page can be accessed again but again it lasts for around 1-1.5hours.
What could be the reason of this?
If it is caused by idle timeout, then your index.html page will not be displayed, this error means that your browser cannot establish a connection with the website you try to reach, because your Internet connection has been interrupted or because your internet service provider has blocked the access to the website.
You can try the following methods to solve this error:
Restart your Internet Router.
Try to visit other websites, to make sure that your Internet connection is working.
If you own another computer/device in your place, then try to visit the website where your receive the "ERR_CONNECTION_CLOSED" error, in order to make sure that the site you 're trying to visit is not blocked from your ISP.
If you have setup a VPN connection, then disconnect from it.
Temporarily disable the Firewall application.
Im running kali Linux 2.0 and am doing DNS spoofing via an evil twin AP.
I have started a dhcp client and configured the hosts file to redirect google.com to my apache2 web server running a very simple webpage that simply displays "hello world"
The problem comes when I try to resolve the address via chrome or firefox. I am able to redirect and display my custom webpage when running on IE, but nothing works on chrome or firefox and I get the message : page not found. It seems that chrome likes to force me to use https://
I'm wondering if anyone knows the security features that come with chrome or firefox that would prevent this sort of attack
thanks!! let me know if I need to provide any info
HSTS might have this effect.
See https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
"HTTP Strict Transport Security (HSTS) is a web security policy mechanism which helps to protect websites against protocol downgrade attacks and cookie hijacking. It allows web servers to declare that web browsers (or other complying user agents) should only interact with it using secure HTTPS connections,[1] and never via the insecure HTTP protocol. HSTS is an IETF standards track protocol and is specified in RFC 6797.
The HSTS Policy[2] is communicated by the server to the user agent via an HTTP response header field named "Strict-Transport-Security". HSTS Policy specifies a period of time during which the user agent should only access the server in a secure fashion."
This is due to HSTS requirements of, in your case "google.com".
You can easily "solve" that problem and get proper spoofed DNS redirection setting server to which you are spoofing to SSL Enabled mode.
Then after entering "google.com" in your "attacked" machine instead of seeing not loaded page (as previously nothing responded on 443 port of your server) you will most likely see a failed SSL handshake (unless you'll manage to provide valid certificate for google.com for your server ;-) ).
If you're using standard Ettercap and Apache2 on Kali setting you may find that usefull:
https://hallard.me/enable-ssl-for-apache-server-in-5-minutes/
Unsure if this is Selenium, chromedriver, Docker or IIS-specific. I am using Docker for Windows (beta, with Hyper-V) on my PC. On the same PC, I am using IIS to serve a website.
When using the selenium/standalone-chrome-debug:2.53.0 image to run a test on that website, the Chrome instance in the container does not receive any HttpOnly-cookies (I have used VNC to check). It does get normal cookies though. This means the CSRF token is gone, and trying to POST a form fails.
Works fine if I visit the website on my PC. Both my PC and the container has the domain for the website in their HOSTS-file.
Normal traffic (HTTP GET) works fine from the container, the only difference (thus far) is that it does not get HttpOnly-cookies.
Edit: When I opened up for navigating to external sites I do receive HttpOnly-cookies. So this is probably not related to Selenium or the chromedriver.
It might be related to use of VPN on my host PC, which I need for the local IIS website.
This turned out not to be a problem with Docker/Selenium/chromedriver/VPN.
We had a request filter that added the Secure-flag to cookies that are sent with the response, but only to requests that comes from remote machines. The Docker container is in this case seen as a remote machine.
When testing on my local IIS I am doing this over HTTP, which means that secure (HTTPS) cookies are not sent.
I have a website behind cloudflare. I need to enable websockets over SSL without turning off cloudflare support. I have a PRO plan and hence won't get the new websocket support. I am using Nginx to proxy a SSL connection to a web socket running on a node server. Now, I read somewhere that cloudflare could work with approved ports would support websockets. Hence, I'm using 8443 for the Nginx port and another port for the node server. Using wscat it returns a 200 error.
$ wscat -c wss://xyz.com:8443
error: Error: unexpected server response (200)
I know that the websocket is expecting a 101 code. However, if I visit https://xyz.com:8443, I can see the page displayed by the node server telling me proxy is working. Also, once I turn off cloudflare support, the websocket starts working. Any clues to get this working. I know I can create a subdomain but I'd prefer running the websocket behind cloudflare.
If you're trying to access this through CloudFlare's network you'd need to explicitly have web sockets enabled on your domain before they will work -- regardless of the port. As in, even if the port can pass through our network, that won't automatically mean that web sockets will be enabled or accessible on your domain.
You can try contacting our support team to request an exception to see if they can enable it for your domain, but typically this is still only available at the business and enterprise levels.
Disclaimer: I work at CloudFlare.