Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

> Memcached, Redis, and Postgres are all dangerous to use because they are written in C?

Yes, actually. And in fact, both Redis and Memcached have been implicated in both security issues and their policy misconfigurarions have lead to widespread DDoS attacks.

As for Postgres, I think most of the industry has finally stopped directly connecting postgres to the public internet. It took many years to get any of these projects as stable as they are, and all have had major security issues in that path.

You should expect those problems if you start a new project in C, with roughly the same lifecycle. Even if you play it in fast forward (say, 25% faster) you're still in for years of major security and stability issues.

This seems ill considered in 2019.

> Does your blanket statement apply to C++ and other C derivatives as well? If so, we lose MySQL, Oracle SQL, MS SQL. Basically every database written more than a decade ago.

No, although you really need to stick to the libraries to make C++ safe. Bare pointer handling and falling back on C-like semantics is dangerous.

> From what I can tell general consensus seems to be that all of those systems are pretty stable and not dangerous because of their language choice.

I'm not sure how we'd directly measure it. Most folks I know trust Memcached slightly more than Redis because its smaller, but consider both to be risky and best when not directly connected to the public internet, as is common with MySQL and Postgres.



Is this fair?

Pretty much _all_ backend software is 'dangerous' when connected to the public internet.

It's fairly rare for anything other than say HTTP(S) and SSH to be exposed unless absolutely necessary.

It's not like it's difficult to cock up authentication in Rust, for example.


> Pretty much _all_ backend software is 'dangerous' when connected to the public internet.

Yes, software security is hard. That's why you shouldn't make it harder by using a language that has tons of undefined behavior unless you have to.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: