On Wed, Jun 9, 2010 at 3:24 PM, Raja Subramanian <rajasuper...@gmail.com>wrote:
> On Wed, Jun 9, 2010 at 2:17 PM, Pothuraju, Naga Deepak > <naga-deepak.pothur...@capgemini.com> wrote: > >> Seriously, if it blocked the sys admins should have a reason to. > > It makes sense for them to block it as there are few other secure > projects running from the same location. And I guess it's the same issue > with every corporate office. Having said that, I still want to understand > the setup they have & break it for my own communication purposes. > > There's an excellent quote from the Camel Book (Perl): > > "If someone hands you a strange gadget, asks you to hold > the barrel to your head and pull the trigger, you cannot assume > it will dry your hair." > > Never mind your good intentions as to why you want to bypass > your corporate security policies. Look at what you are attempting > from the company's perspective. It's clearly 1) against corporate > policy, and 2) against the law. You may be faced with consequences > more severe than you currently imagine. > > During my time at university, out of curiosity I tired such things, > and am thankful that I got away with only a good scolding. The > corporate world is not so forgiving. > even i tried such stuff and found a way to bypass the proxy server in my univ. wifi network, so mailed this issue anonymously to my college associate director.. he never replied... :D but that was way safer option than getting deeper into the intrusion and get caught at some point. :) > > If you still want to learn such things, suggest you setup a lab > at home and practice all you want. Don't do it at office or on > someone else's infrastructure. > > - Raja > _______________________________________________ > ILUGC Mailing List: > http://www.ae.iitm.ac.in/mailman/listinfo/ilugc > -- idlecool _______________________________________________ ILUGC Mailing List: http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
