Bypassing Fortiguard is not easy. All the same, if you still want to give it a try, there is one possible method through using a free proxy list.
- Visit the forum for proxies. In order to get proxy list, you have to go to the forum SocksProxyForum. If the website already blocked, put the url in the proxy site KProxy.
- Try the https method. Fortiguard cannot block it because this method is for security purposes.( the new version can now )
- Select a name. In the forum, register your username.
- Choose which proxy you want to use, socks or http by choosing topics. Choose address with irregular ports (don't use 80, 8080, 8008, 3124, 3127, or 3128 ports).
- Read the post on how to put the proxy in your web browser.
- Since proxies get blocked often you should join a proxy mailing list like the one below to keep getting fresh proxies daily.
- Some of the proxies work, and some do not. Check that you can use Charon software (you can find the download link in the forum).
- This will not work on latest versions of Fortiguard.
Note : fortiguard clearly says that none of their filters work on HTTPS ;) so you guys need to decide if its worth the money u shell in hehe
Say you have blocked Web based email in your fortiguard policy and you check it by going to http://www.gamil.com . you see that you could have access to the login page of gamil in spite of blocking it. So you try to log in and see its it blocks and once you log in it block perfectly saying its a Webbased email site. And you url would read " Http://mail.google.com/mail/?auth=DQAAAG0AAADkxf81BT4k5Q_dw7zQsGO2RuHEQ55IOMzbimKF8Ia7WbQZHvXuVo7o5smHQGg9C_nC4SQz2ofiC3hhc8q4Ar14V-PqgtawN>>>>>>> in your browser. But if a user prefix the same url with a https instead of Http he can get into his Gmail account. The firewall is unable to even log this activity ( memory logging).
Lets take an example of Proxy avoidance ( I know its a nightmare for admins) . say a user tries to access http://www.kproxy.com . Fortiguard beautifully blocks it under the Proxy avoidance category. But if the user prefix a https then he can get into the site and from there he is virtually un stoppable form accessing any shit he wants ( no logs again).
You need to input a policy that Block all the Https protocols. Well if you do this all the ligament sites such as ( MSDN just an example ) or say your Ims would get blocked. If you want to exclude suck secure sites you need to go and find all the ips they would use ( thats not really easy) and then allow then Https access.
Find all the sites that allow Https Proxy and block them. Just a reminder that each of the would have tone of ips and most of them keep changing frequently.
Fortiguard makes the filters work with https :D
Fortinet OS 3 Mr1
Fortinet OS 3 Mr2