LWN.net's Journal
[Most Recent Entries]
[Calendar View]
Thursday, February 18th, 2021
| Time |
Event |
| 1:11a |
[$] LWN.net Weekly Edition for February 18, 2021
The LWN.net Weekly Edition for February 18, 2021 is available. | | 2:19p |
Google's effort to mitigate memory-safety issues The Google Security Blog carries an
announcement of a heightened effort to reimplement security-critical software in memory-safe languages. " The new Rust-based HTTP and TLS
backends for curl and now this new TLS library for Apache httpd are an
important starting point in this overall effort. These codebases sit at the
gateway to the internet and their security is critical in the protection of
data for millions of users worldwide." | | 2:46p |
Security updates for Thursday
Security updates have been issued by Debian (mumble, openssl, php7.3, and webkit2gtk), openSUSE (jasper, php7, and screen), SUSE (bind, php7, and php72), and Ubuntu (bind9, openssl, openssl1.0, and webkit2gtk). | | 3:20p |
[$] How useful should copy_file_range() be? The copy_file_range()
system call looks like a relatively straightforward feature; it allows user space to ask the kernel to copy a range of data from one file to another, hopefully applying some optimizations along the way. In truth, this call has never been as generic as it seems, though some changes made during 5.3 helped in that regard. When the developers of the Go language ran into problems with copy_file_range(), there ensued a lengthy discussion on how this system call should work and whether the kernel needs to do more to make it useful. |
|