Date: Fri, 6 Sep 2024 08:05:07 +0100 From: David Chisnall <theraven@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: Alan Somers <asomers@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: The Case for Rust (in any system) Message-ID: <EA471699-809C-44A0-B1E2-20B76CB04284@freebsd.org> In-Reply-To: <CANCZdfoHP3G3YMvpqVwpQZSRQ64pnYhBJD60Dcar%2BBCUaJNL-w@mail.gmail.com> References: <CANCZdfoHP3G3YMvpqVwpQZSRQ64pnYhBJD60Dcar%2BBCUaJNL-w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 Sep 2024, at 21:17, Warner Losh <imp@bsdimp.com> wrote: >=20 > Without enough resources, > the rewrites will be crap and nobody will want to use them (or maybe even > FreeBSD). The rewrites to date have lost functionality (though maybe not > functionality that's important) relative to what they replace. The new Windows sudo tool is a good example of this. It was written in Rust a= nd, as far as I know, no one has found any memory safety errors. Some large c= ategories of potential vulnerabilities were eliminated by construction, whic= h is great. Unfortunately, that didn=E2=80=99t stop it having a terrible sec= urity architecture that allowed remote privilege elevation. You don=E2=80=99= t just need competent Rust programmers, you need competent Rust programmers w= ho are domain experts. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EA471699-809C-44A0-B1E2-20B76CB04284>