3 ms·
Most of the restrictions you might want to circumvent are put in place for legal reasons, not technical. Some data is not allowed to leave the state, some the b
by noonespecial 17y ago
Most of the restrictions you might want to circumvent are put in place for legal reasons, not technical. Some data is not allowed to leave the state, some the building. Amazon servers are not on the list!
One tiny slip, one mishap, and all of the "being freakin' awesome at your job" in the world won't stop you from being a great big minus sign on your company's balance sheet with regards to hiring you.
If you happen to be an employee considering these methods in order to improve your own awesomeness by breaking the rules, consider why those restrictions where put there in the first place: "jackass,you are the problem"
Sorry for the rant, just an old IT guy here who's had one too many dealings with over-clever users who broke stuff big time by "knowing better" without knowing enough...
- varaon 17y agoNot to mention that they may not look kindly upon you exporting data without their knowledge (they might suspect or consider it to be data theft). My last employer had a good IT department, but also a strict security policy. USB keys were a no-no, so uploading company data to a third party wouldn't be favourably looked upon either.
- bockris 17y agoI had a manager in 2001 that broke internal IT policy by buying a wireless router to use in his office and he didn't secure it. Why did he need it you ask. Because sometimes he didn't want to sit at his desk but at his conference table 10 feet away. We almost failed a PCI audit because of his stunt. Also we bought a software application that the vendor insisted needed unrestricted access to the internet. We tried it from behind our firewall and whatever they were doing couldn't get past our proxy. We actually had to deploy this internal application in a DMZ and waste a public IP to run it. We had a tech from that company doing some upgrades and later we found that we were running an FTP warez site. The tech had started up the default IIS FTP server so he could leave some files to retrieve later and didn't bother to tell us.
- jmount 17y agoI never did it, but my frustration with one IT department was so great that I planned to: buy a wireless router, turn it on, name it "ITDeptPrivate", give it a random password, NOT hook it up to anything and lock it in closet or drawer somewhere. Let them wasted their time hunting down something that in some sense does not exist.
- bockris 17y agoIf you valued your job that little, you might as well have quit, IMO. You aren't going to change policy with nose thumbing pranks. I have a decent win/lose record by engaging the decision makers over policy issues like this. When you don't win, you can't cry about it. You find a new job or live with it and wait for an opportunity to bring it up again. Playing tricks or willfully circumventing restrictions just makes it worse for everyone when you are caught.
- itgoon 17y agoYeah, this is bad. It isn't like standing up a Linux box, or OSS CMS, or something like that, internally. Now, if Amazon or someone were to offer a variation of EC2 that did satisfy all the various privacy/data retention laws and regs... /me scurries off to do some idle research