Re:I found a security issue on a competitor, got fired and s...
by jahewson on Wednesday March 16, 2022 @10:37PM
(#30707001)
Agreed that anyone who knew about the flaw should be as suspect as the employee in question. But what was this guy doing pentesting a competitor instead of performing his job duties - that’s grounds for being fired right there. Even with an “ok” outcome he’d have arguably caused harm to his employer.
[ Parent
| on HN ]
Re:I found a security issue on a competitor, got fired and s...
by SamBam on Wednesday March 16, 2022 @11:22PM
(#30707304)
Even ignoring that most software jobs understand that a small amount of time just noodling away on tech stuff is to be expected as part of the job, exploring a competitor's public APIs seems very closely aligned with many programmer's priorities.
Re:I found a security issue on a competitor, got fired and s...
by paxys on Wednesday March 16, 2022 @10:53PM
(#30707113)
Maybe, but if his company really had a problem with it he would have been fired or at least repremanded when he initially brought up the problem, not months later.
Re:I found a security issue on a competitor, got fired and s...
by Brian_K_White on Wednesday March 16, 2022 @10:56PM
(#30707125)
I know right? I bet he even went to the bathroom and even slept at night. Imagine!
Re:I found a security issue on a competitor, got fired and s...
by MathCodeLove on Wednesday March 16, 2022 @11:09PM
(#30707231)
Because that's definitely the same thing.
[dead]