-
• #2
For #3 would I just copy and paste "67.207.134.180 http://www.londonfgss.com css.londonfgss.com static.londonfgss.com js.londonfgss.com londonfgss.com" into the host file and hit save?
Is there anything else I'd need to do?
-
• #3
I work by myself from home so that makes life very much easier.
But occasionally if I think my girlfriend might come home and catch me looking at bike websites I always have a full screen browser page with hardcore porn ready to bring to the front to hide 'londonfgss'.
-
• #4
Object For #3 would I just copy and paste "67.207.134.180 http://www.londonfgss.com css.londonfgss.com static.londonfgss.com js.londonfgss.com londonfgss.com" into the host file and hit save?
Is there anything else I'd need to do?
Nope, that's it.
Once copied it, give it 10 minutes, and when you run your browser it will be looking at the changes in your hosts file and will send the IP address over the wire and not the domain name... so in the logs you'll be fine.
I personally think the very best tactic is #2, the https route. The only downside is that as nothing (not even your browser) will log or cache that access, the site will be fractionally slower as it has to fetch everything for every page, including that header logo and all of the javascript and css.
-
• #5
I've already added three to my host file but on your recommendation I'll use the https method ;]
Thanks for the sneaky tips
-
• #6
this is great advise. thanks vb.
about 2yrs ago, my old company's HR did a random check on staff. i came up on top (out of about 300?) for the two days they did the check...and that was before lfgss.com! anyway, got a slap on the wrist...didnt give a sht anyway as i was couple of mths away from leavin the company at that point. but it was very very embarassing.
-
• #7
iPhone over Edge™ people !
-
• #9
hael or if you dont have to worry bout the proxy and just how it looks use this wee gem :D
That's genius ! :)
-
• #10
Unfortunately for me, the only option that works here is #1.
Even the PC's are protected, meaning you need to be an administrator to change anything, which includes changing the bloody date or time!
As for the above site, I even get this friendly warning:
[cite]Blue Coat Web Filter[/cite]Your request was categorized by Blue Coat Web Filter as 'Proxy Avoidance'.
If you wish to question or dispute this result, please click here. -
• #11
Sam Unfortunately for me, the only option that works here is #1.
Even the PC's are protected, meaning you need to be an administrator to change anything, which includes changing the bloody date or time!
As for the above site, I even get this friendly warning:
[quote][cite]Blue Coat Web Filter[/cite]Your request was categorized by Blue Coat Web Filter as 'Proxy Avoidance'.
If you wish to question or dispute this result, please click here.
[/quote]Ha! we have a blue coat here at work ...suppose I should get round to installing it.. but I dont care what people look at tbh, a company I used to work for if you typed in any job sites it referred you to a page saying "We dont want to lose you please come and have a chat with HR" -
• #12
Sam
Dose n.o 2 not work?
You could always try and get yourself a free shell acount and then use this method
if you have firefox you can use preferences to alter the proxy info.
http://anonymouse.org/ Is another thing like hael's link. Depends if the nanny software knows about it.
-
• #13
Hi Tommy
That doesn't work either, as we cannot access our Internet options!! It's fucking shit here! For now I'll just keep using one of the other website addresses until that's blocked, then move onto the next one. Since the original .com address was blocked it has been fine using the .co.uk one to be honest.
The anonymouse site is also blocked BTW. Gah!
-
• #14
http://www.proxy.org - it's a list of thousands of proxy sites. One of them will work ;]
-
• #15
yes, but proxy.org is blocked...
-
• #16
sigh... you just need to be nice to your IT ppl... we all like briberies, particularly the ones containing chocolate ;)
-
• #17
tynan I work by myself from home so that makes life very much easier.
But occasionally if I think my girlfriend might come home and catch me looking at bike websites I always have a full screen browser page with hardcore porn ready to bring to the front to hide 'londonfgss'.
hahah thats what i do also
-
• #18
Well, for the people working at home, I've split the traffic over two different sub-domains so that more http connections to the server above the maximium of 4 can be in use and the pages go faster. You guys needn't do anything, it should just work faster by default.
-
• #19
why thank you kindly :)
can you make my sewing machine faster as well? -
• #20
Might have to start using some of these for when i'm browsing at work :)
general computer question for you vb... I'm connected to my uni's network through my halls, so when I access a site through a secure connection is the data encrypted from my computer to the server of the web site, or only between my network's server and then the web site's server?
Not for lfgss - nothing is blocked on our network at all, we allegedly only get monitored if we download >5gb a day (it is verrrry fast) - something else.
-
• #21
If you are connected to any SSL/https/SSH service, then your data is encrypted between your application (the browser/SSH terminal or whatever) and the end server that you are talking to.
No-one is able to read the contents of the communication.
However, it is possible that they can read the URL and headers of the original request for the communication. For this reason most services will set up the secure connection prior to asking for a password or giving out any private data.
Because of the probability that a secure communication will contain private data, even though your browser could cache the unencrypted version it displays to you... the default is that browsers will never cache or store any copy of anything sent over SSL.
Following on from that, if you've ordered gig tickets online and been told to print and page and didn't, and then clicked back in your browser... this is why the page no longer exists. Secure pages aren't stored and your browser has nothing to go back to.
-
• #22
velocity boy If you are connected to any SSL/https/SSH service, then your data is encrypted between your application (the browser/SSH terminal or whatever) and the end server that you are talking to.
No-one is able to read the contents of the communication.
However, it is possible that they can read the URL and headers of the original request for the communication. For this reason most services will set up the secure connection prior to asking for a password or giving out any private data.
Because of the probability that a secure communication will contain private data, even though your browser could cache the unencrypted version it displays to you... the default is that browsers will never cache or store any copy of anything sent over SSL.
Following on from that, if you've ordered gig tickets online and been told to print and page and didn't, and then clicked back in your browser... this is why the page no longer exists. Secure pages aren't stored and your browser has nothing to go back to.
Burn him! Hes a Witch with his interwebs voodoo! ;) -
• #23
ok, cool. cheers vb
-
• #24
I am in charge of the IT at our work and my boss came in to do a random check on ebay, facebook etc. and he apologised to me if it became embarassing for me as I may be in the report.
Well lets just say none of the reports had anything bad to say about me!!
I completely bypass the filtering / logging system and have totally unfiltered internet access at work, it's good to know more than your boss sometimes.
In a previous job, I had to check the filters in a small company. One day they were filled with loads of adult sites, I took a copy of the logs and reported it to my boss without actually working out who it was. We then sat at his computer and looked into who had done it and it turned out to be him, lets just say I got promoted and a pay rise quickly after that ;-)
-
• #25
heh... isn't it good to work in IT!
we don't bother with logs much either unless we suspect someone is up to no good. it would be a massive waste of our gaming time if we were to check what everyone does all the time.
Most work places have a proxy through which all computers in your workplace connect to get to the internet.
It is trivial for them to log the traffic through that proxy and to see which computers and logins in the workplace generate which traffic. This means that you should always assume that your workplace knows where you surf unless you truly know they are not doing this (i.e. you're self-employed and have set up no such thing).
The key to not being caught surfing at work is to keep your usage down or stick to browsing at lunchtime when you could reasonably argue that you were doing so in your time.
Of course, failing that the key is not to show up in their computer generated reports.
How not to show up in reports that are compiled against traffic usage:
1) Use a secure connection, as these are never cached or logged.
2) Use an IP address and HOSTS entry so that the site isn't identifiable from the log files.
#1, you can use this secure URL to access the one URL. Note that the certificate is self-signed, which means I made it up... it's still secure but because I didn't pay Verisign it may give you warnings... just click OK or Accept or whatever and it's all cool... your connection will be encrypted and no access will be logged by your workplace.
https: //www.londonfgss.com/
#2 Put the following in your hosts file:
209.20.64.92 www.londonfgss.com css.londonfgss.com static.londonfgss.com js.londonfgss.com londonfgss.com
Now when you enter www.londonfgss.com your local computer resolves the DNS using your hosts file and only the IP address gets logged by your firewall. And if someone visited the IP address they wouldn't get this site (try it, your browser has to know about the domain name as well as the IP address).
So those are the two methods I've provided to make sure you lot don't get caught being productive on here, unproductive at work. If you get caught and sacked or whatever... it's firmly your own fault ;)