Me: OpenSSH is one of the most secure apps ever written, even in C C Haters: no it’s not! Several RCE bugs! Me: prove it. Show me a working exploit. *crickets* FUD and Security pedanticism is unbecoming of our insustry, Pals.
-
-
That’s a good one and valid, but not one of the bugs anyone else has brought up
. Besides, having bugs isn’t the issue. Resolving, reducing, and remaining well architected is the point. -
Yep. And choosing a language that eliminates whole classes of exploitable vulnerabilities is part of good architecture in my book. I won't deny that OpenSSH is comparatively well written. But writing C is much harder than most people realize. Undefined behaviour everywhere.
-
Yeah no one is disagreeing. Ignoring better options isn’t the point. Acknowledging that good architecture is a choice is. It isn’t really “harder” now, either. In fact it’s easier today to write safe C than ever before. We know more & have better tools/OS guards. It’s easy now :)
-
Easy really is the wrong word here. And there's still stuff sanitizers and static analyzers don't see. There's still exploits despite mitigations. In most cases, there's just no need to waste cognitive load on low level details. Higher level languages are more economical.
-
I’m one of the best when it comes to finding 0day in C. :) but I know it’s easy now, to write safe C. You can disagree all you want, but the tools and mitigation’s are available. Our industry failure is not making access simple and straight forward.
-
#define SIZE 8192 char buf[SIZE]; void cpy(struct foo* p, int count) { int n = count * sizeof(struct foo); if ((n < SIZE) && (n > 0)) memcpy(buf, p, n); } Safe or not? Why? How many people can spot this? Which tools? Far from easy. -
Creating situations that are easily avoidable doesn’t prove your point, it proves mine. :)
-
What about the situation in the above code is easy to avoid? I've shown the snippet to rooms full of people who do code audits for a living. Maybe 1 in 30 even gets what the problem is. Regular engineers? Zero out of 30.
- 6 more replies
New conversation -
-
-
oh, and it's also an exploit against a dead system... who is stupid enough to still run a FreeBSD version that's not been updated for over 7 years ?
-
Sadly? Lots of people... also embedded boards based on F7
-
those people deserve to get hacked...
-
I’m of the opinion that no one deserves to be hacked :) but I grok your feels
-
the main problem with wide-open embedded shitz is generally that it's used as a puppet in DDoS later on...
End of conversation
New conversation -
-
-
that's actually an exploit against PAM... not openssh proper.
-
I was waiting for someone to point it out, but...

End of conversation
New conversation -
-
-
It seems to lack any searchable identifier (e.g. CVE) and it's not even clear if it was an OpenSSH bug of a pam bug.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.