A Sad Day for Rust

Re:A Sad Day for Rust by xscott on Friday January 17, 2020 @01:00PM (#22077274)

> if you write one, advertise one, you need to care about security

No, you don't. The author doesn't owe you a single thing unless you have a warranty saying otherwise. Most licenses explicitly say something like:

   THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
   IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
   WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

If you don't like the terms, don't accept the code. I don't see how that could be more clear.

[ Parent | on HN ]

Re:A Sad Day for Rust by temac on Friday January 17, 2020 @02:30PM (#22078249)

Half (more probably 99% actually) of our critical infrastructure software use that wording (or an equivalent one), regardless of it is free software or proprietary software.

Yet most are maintained responsibly, if they are used for serious stuff and/or advertise in a way that suggest that kind of usage can be considered.

[ Parent | on HN ]