Take the 2-minute tour ×
Web Applications Stack Exchange is a question and answer site for power users of web applications. It's 100% free, no registration required.

At work, they blocked personal email. Our IT staff couldn't find a good way to block only Gmail so they blocked ALL Google accounts. I asked my supervisor if all Google sign-ins should be blocked and he confirmed Gmail only, they just didn't do it correctly. I use Google Calendar for work and being unable to sign into it is really hurting me. I've sent a request to our IT dept but they are currently dealing with server upgrades and whatnot. Basically, I'm low on the priority list.

So my question is: Is there any way to sign into Google Chrome browser or individual Google sites without going through "accounts.google.com"? I don't care about Gmail, I'm not trying to go around what they want blocked, I just need to be able to log into Google Accounts so I can let Outlook sync with Google Calendar.

share|improve this question

migrated from superuser.com Jul 12 '13 at 8:06

This question came from our site for computer enthusiasts and power users.

    
1  
Ask them for an alternative calendar that you CAN use? –  techie007 Jul 8 '13 at 19:23
1  
set up a personal wifi hotspot on your cell phone and access google.com through there? :) –  MattDMo Jul 8 '13 at 21:38
    
They don't allow it. I'm not trying to get around security. I respect their decision to block person email. It's the other things that got blocked in that pursuit that I'm trying to get back. –  WizardKnight Jul 8 '13 at 22:20
1  
This question appears to be off-topic because it is about web applications, but is not clear enough to warrant migration to Web Applications –  Darth Android Jul 12 '13 at 1:28
show 1 more comment

1 Answer 1

HTTP request headers have a domain field that states the domain the request is for, it's mainly useful for addresses that have multiple domains/sites. It's a required field in HTTP 1.1, so they could somewhat-reliably block according to that.

However, the problem is with SSL/TLS, it would encrypt everything so that the field couldn't be accessed. That could be subverted by blocking encryption for google entirely, although that's a bit extreme. Other methods might be to have everyone use a proxy that blocks requests to gmail, but a good method would be to block DNS requests/replies for mail.google.com, which skips encryption entirely, but it still has some caveats. (e.g. people could add the IP addresses for mail.google.com to their hosts file so that their browser resolves the domain properly while still sending the domain field so they access gmail)

All in all, I'd recommend you suggest blocking DNS instead of them blocking the IP addresses themselves, they may miss one or two, but it's the majority they'll probably care about.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.