Updated OP: I just lost my job for going above and beyond. - Page 7

WhoBeDaPlaya · 11-07-2012, 05:38 PM

Quote:

Originally Posted by jagec

That's not hacking, hacking looks like this:

He was hacking surveillance equipment, not the damn Gibson!

Red Squirrel · 11-07-2012, 06:07 PM

Quote:

Originally Posted by Jodell88

Well shit, the OP got fired for doing something I had to do for my data communications class for my degree. I guess I 'hacked' 25 universities from all over the world by their logic.

I better go hide from the feds. I'm an international criminal.

I'm pretty much a hardcore phreaker by their definition. I login to the console for the DMS (regional phone switch) and MTX (switch for CDMA cellular). I can hack into everybody's phones. I should be in federal prison!

Actually there is a feature that's pretty cool, I can hookup to any phone I want and make a phone call as if it came from them. It's a good way to test stuff like line noise or long distance related troubles.

ketchup79 · 11-07-2012, 06:14 PM

Quote:

Originally Posted by Red Squirrel

I'm pretty much a hardcore phreaker by their definition. I login to the console for the DMS (regional phone switch) and MTX (switch for CDMA cellular). I can hack into everybody's phones. I should be in federal prison!

Actually there is a feature that's pretty cool, I can hookup to any phone I want and make a phone call as if it came from them. It's a good way to test stuff like line noise or long distance related troubles.

We can do the same. What kind of phones do you guys use?

Red Storm · 11-07-2012, 06:14 PM

ITT: People who are as clueless as the OP's former employers. As well as some who know what they are talking about.

Good luck to you OP, I would do what you can to make sure that company doesn't affect your future employment, but I think you can find much better places to work.

ketchup79 · 11-07-2012, 06:19 PM

If you haven't done so already, get a set of good references from that company. From the way you explained things, there should be plenty of people there who still know what a good employee you were. Get them on LinkedIn if they are not already.

marmasatt · 11-07-2012, 06:27 PM

Quote:

Originally Posted by Arkitech

How was he being an idiot? Those are very basic commands, they don't weaken or compromise the security of the network in anyway.

Not too mention, way to pour salt in the guy's wounds.

HeXen · 11-07-2012, 06:33 PM

Quote:

Originally Posted by waggy

UNLESS you are IT you never mess with the command propt. there is no reason to do it.

HR and such are idiots and have no clue that /ipconfig is. all they see is a lot of numbers scroll by.

they take this as you are either installing software, hacking, or worse.

never a good idea.

also as six mentioned this was not "above and beyond" for his job and in no way would have helped him in a interview

agree...he went above and beyond the scope of his employment. Just do your job to the best that can be done and end it there.

Jeff7 · 11-07-2012, 06:34 PM

Either he wanted the position, as Red Storm suggested, or else he'd only ever seen command prompts on CSI-type TV shows, where the only ones using a command prompt are either people breaking into a system illegally, or the police/FBI/whatever who are trying to catch them.

---

In high school, I decided to run a defrag program on one of the super-awesome Pentium I PCs in one of the computer labs. (This was right around the same year that the Pentium III was released. High-end stuff there.

)
The programming teacher saw the defragmentation map, and thought I was running something that was going to damage the computer. She was unfamiliar with this "defragmenting" process. Luckily, I didn't get in trouble, though I did have to close the program.

PenguinPower · 11-07-2012, 06:38 PM

Quote:

Originally Posted by Corporate Thug

Unless he can show that the termination was pretextual...in other words, show a pattern that people from other races were disciplined less severely for more severe violations...it's a stretch though to be honest.

Yep. Already said that.

HeXen · 11-07-2012, 06:38 PM

For whatever reason, this thread reminds me of the kid who brought a Linux CD to class at school, passed copies around and got expelled for pirating?
...it made funny

Jeff7 · 11-07-2012, 06:47 PM

Quote:

Originally Posted by HeXen

For whatever reason, this thread reminds me of the kid who brought a Linux CD to class at school, passed copies around and got expelled for pirating?
...it made funny

Seriously? Link?

Let me guess...the school had a zero-tolerance policy about this sort of thing?

"But the license says that the software may be freely distributed!"
"LALALALA EXPELLED GO AWAY I CAN'T HEAR YOU!!!"

HeXen · 11-07-2012, 06:51 PM

Quote:

Originally Posted by Jeff7

Seriously? Link?

Let me guess...the school had a zero-tolerance policy about this sort of thing?

"But the license says that the software may be freely distributed!"
"LALALALA EXPELLED GO AWAY I CAN'T HEAR YOU!!!"

It's been a couple years back. Had the Linux community in quite the uproar over it. I'm sure someone here remembers more about it, I think it was even discussed here. What I recall is the teacher didn't know what Linux was and took it to the principal who thought he was pirating software cause they knew nothing of open source. I think they let him back in with an apology.

yllus · 11-07-2012, 06:52 PM

I came in expecting that you ran netcat or nmap, which are borderline activities (they shouldn't be, but alarm bells would ring for most competently managed networks). But what you ran is totally innocuous, especially if the commands were in fact accessible.

Sorry to hear about this. You were clearly fired because your supervisor wanted you out of the way.

Eli · 11-07-2012, 06:59 PM

Ask someone in IT for permission to run a command prompt and some network commands, lol.. some of you folks are insane.

I wouldn't think twice about opening a command prompt and checking some things out just for the hell of it, let alone any legitimate reason like preparing for an internal job interview.

GoodRevrnd · 11-07-2012, 07:17 PM

Quote:

Originally Posted by Acanthus

The best i've got is inconsistency.

As i've said earlier, someone installed a wireless router on the surveillance network with the intention of breaking the internet block (he failed lol) and was caught by IT in the process.

He was promoted.

Good lord. Earlier in the thread it just sounded like some guy set up a wireless router as a necessary job function in a secure environment and left it open out of incompetence. I would expect someone to be written up over that, and possibly terminated depending on how sensitive the environment it. The fact that he did this with the sole intent of bypassing a web block and still has a job is mind boggling.

You got fired because someone wanted you out o the way. Sorry man.

Pheran · 11-07-2012, 07:59 PM

Quote:

Originally Posted by Acanthus

I'm very close to my CCENT.

The problem is all jobs available in networking want a 4 year degree.

Pay no attention to this requirement when applying for jobs. Sure, you'll sometimes get filtered out by mindless HR departments, but some of us really don't care and will evaluate your skillset in an interview regardless of what pieces of paper you hold.

Cattlegod · 11-07-2012, 08:42 PM

Here is a different way to look at it. Say there is a room at the company. It says restricted access on the door. Inside the room is a high voltage panel without any safety guards and all of the wires are exposed. You are interviewing for a job to work on high voltage panels.

You sneak into the room to look at the panel to learn about it and the security guard sees you walk in. The security guard turns you in and you get fired under the condition that it doesn't matter if you we're just looking around even though you didn't touch anything.

Do any of you view this situation differently?

Ns1 · 11-07-2012, 08:44 PM

Quote:

Originally Posted by Cattlegod

Here is a different way to look at it. Say there is a room that is locked at the company. It says restricted access on the door. Inside the room is a high voltage panel without any safety guards and all of the wires are exposed. You are interviewing for a job to work on high voltage panels.

You sneak into the room to look at the panel to learn about it and the security guard sees you walk in. The security guard turns you in and you get fired under the condition that it doesn't matter if you we're just looking around.

Do any of you view this situation differently?

Yes because CMD isn't locked nor does it say restricted access. OP didn't have to "sneak", all he had to do was hit start -> run -> cmd

Turin39789 · 11-07-2012, 08:49 PM

Quote:

Originally Posted by Cattlegod

Here is a different way to look at it. Say there is a room that is locked at the company. It says restricted access on the door. Inside the room is a high voltage panel without any safety guards and all of the wires are exposed. You are interviewing for a job to work on high voltage panels.

You sneak into the room to look at the panel to learn about it and the security guard sees you walk in. The security guard turns you in and you get fired under the condition that it doesn't matter if you we're just looking around even though you didn't touch anything.

Do any of you view this situation differently?

It wasn't like this at all.

You work at a security company that installs security alarms. You are interviewing for a security installation job. You walk around the building and count the doors, so during your interview you can discuss how you would setup a security system for the building.

You are fired for counting doors.

You didn't sneak into anything, you didn't open a single door. You walked down a hallway.

Cattlegod · 11-07-2012, 08:50 PM

Quote:

Originally Posted by Ns1

Yes because CMD isn't locked nor does it say restricted access. OP didn't have to "sneak", all he had to do was hit start -> run -> cmd

Updated to remove the word locked.

If it is restricted where he went, ignorance isn't an excuse.

tranceport · 11-07-2012, 08:51 PM

Quote:

Originally Posted by jagec

That's not hacking, hacking looks like this:

That looks like a gibson.

Ns1 · 11-07-2012, 08:51 PM

Quote:

Originally Posted by Cattlegod

Updated to remove the word locked.

If it is restricted where he went, ignorance isn't an excuse.

And nowhere does CMD get labeled as "restricted".

her209 · 11-07-2012, 08:52 PM

Good thing the OP didn't issue a ping command or he would have been considered to be DoS'ing a system.

Cattlegod · 11-07-2012, 08:56 PM

Quote:

Originally Posted by Ns1

And nowhere does CMD get labeled as "restricted".

I'm not saying what the OP did was wrong. The company he works at may be full of idiots and jerkoffs.

What I am saying is that if he wasn't told upfront that it was restricted, he should have picked it up based on company culture and the conversations he has had with people prior.

Ns1 · 11-07-2012, 08:58 PM

Quote:

Originally Posted by Cattlegod

I'm not saying what the OP did was wrong. The company he works at may be full of idiots and jerkoffs.

What I am saying is that if he wasn't told upfront that it was restricted, he should have picked it up based on company culture and the conversations he has had with people prior.

If it wasn't labeled as restricted, "picking it up based on company culture and conversations" is a pretty shitty threshold.

//edit

wait a second, he DID pick that up based on company culture and conversations!

Quote:

As i've said earlier, someone installed a wireless router on the surveillance network with the intention of breaking the internet block (he failed lol) and was caught by IT in the process.

He was promoted.