>> developers should be liable for the damage caused by their negligent code

To be fair, at this point I would rather see developers not writing code; rather than writing buggy one.

I had a friend on FB who's just completed a security course and wrote a password generator in Go. The random was seeded from a current date in nanoseconds. The issue is that while no one will probably ever reverse his passwords, but the guy open-sourced his script. How many people will be influenced by that piece of code?

Lawyers have that: if you can't be liable - you're not a lawyer. GTFO.

I found that same exact issue in Terraform Go code where it generates passwords for AWS IAM users: https://www.cvedetails.com/cve/CVE-2018-9057/

We need to find out who is teaching this stupidity and make them stop.

libssh is pretty niche. This isn't openssh.

libssh is used because openssh isn't suited to be used as a library. So it's one of the most popular ways to automate the most popular remote shell protocol.

It's not really niche - I'd say it's an average popularity library and likely used by a bunch of internal projects.

The libssh client code is used pretty commonly for that sort of thing.

The libssh server code, on the other hand, is pretty niche.

So "niche" it was used by github, albeit in a configuration that protected them from this

Except for github, its unlikely you use any software that uses libssh.

Just because it has that name dosen't make it some kind of official SSH library that tons of software uses.

What does git use?

OpenSSH.

Actually, just whatever 'ssh' binary is installed. That is not necessarily OpenSSH, but it is the most common choice.