Re:What developers should know about TCP
by irrational on Friday May 15, 2020 @01:36PM
(#23194907)
Why don't you tell us the vendor's name? It seems like the responsible thing to do.
Even after the bug gets fixed, it'll probably take years for all the embedded devices in the public internet to get patched, so no.
Re:What developers should know about TCP
by laughinghan on Friday May 15, 2020 @06:58PM
(#23198501)
But in the meantime, won't the vendor keep adding more broken devices to the public internet, making the problem worse?
The longer it takes for this problem to become public, won't the more harm be caused when it does become public?
We're just waiting for the free market to kick in.
Re:What developers should know about TCP
by outworlder on Friday May 15, 2020 @02:02PM
(#23195259)
> This time they don't understand why client-side authentication means no authentication at all
I've seen this... with an intern! I can't imagine dealing with a whole team like that.
Re:What developers should know about TCP
by throwaway_pdp09 on Friday May 15, 2020 @01:06PM
(#23194548)
How do you not kill these people? How do you put up with it? How do vendors like this survive?
Just like in nature, they survive because they are good enough, and don't experience enough competition to be eliminated by selection.
Depending on what kind of vendor we're talking about, it might be that such aspects aren't even part of what makes them competitive. The average user is not going to know about these types of issues, and so they're not even going to consider such issues when evaluating the vendor.
full disclosure could put some selective pressure on them.
Re:What developers should know about TCP
by heavenlyblue on Friday May 15, 2020 @07:40PM
(#23198829)
I would assume the “free market” here is that these companies will over-extend themselves so much that they will no longer be able to hide the bugs from the malicious parties and their devices will start getting hacked en masse.
I would assume, however, that there is no law forcing minimal security so you can class A them, can you?
Just about every industrial automation vendor is like this in my experience. They never upgrade because they don't want to break anything.
In between the emails I googled a bit and found the changelogs for the RTOS they were using. Turned out that it was a bug in the upstream HTTP server. This also meant that the platform they were using had all the security holes from those five-plus years. The bug was later silently fixed when they acquired a newer release from upstream.
Currently I'm having a similar issue with the very same vendor. This time they don't understand why client-side authentication means no authentication at all and why passwords must not be stored in plain text in the database that can be remotely backed up from the device.