Re:How to unc0ver a 0-day in 4 hours or less
by ehsankia on Thursday July 09, 2020 @04:43PM
(#23784948)
Reguardless of how bad the original fix was, this is why testing is important. The original person should've added tests to make sure that specific issue doesn't come up again, and it would've caught the regression.
> Thus, this is another case of a reintroduced bug that could have been identified by simple regression tests.
Re:How to unc0ver a 0-day in 4 hours or less
by thomaslkjeldsen on Thursday July 09, 2020 @05:31PM
(#23785456)
> Talk about running in circles.
So maybe writing and reading useful commit logs is not such a bad idea after all :)
Reminds me of this quote: "Those who don't know their history are doomed to repeat it."
Re:How to unc0ver a 0-day in 4 hours or less
by hnick on Thursday July 09, 2020 @09:23PM
(#23787191)
Or comments in code. They are very useful when pointing out gotchas.
Re:How to unc0ver a 0-day in 4 hours or less
by userbinator on Thursday July 09, 2020 @03:56PM
(#23784381)
...or the more interesting and perhaps less plausible explanation: someone who doesn't toe the line, someone who was trying to "take down the system from within"...
I often wonder what goes through the minds of those whose work helps companies exert more control over their customers. Maybe some of them are not so "obedient" after all...
Ooof. Talk about running in circles. Either this was someone who is swamped with work and spaced out, or a new programmer who wasn't familiar with the original. Oddly, I feel bad for both of them!