lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 5 Jan 2020 04:09:29 +0000
From:   Al Viro <>
To:     Evan Rudford <>
Subject: Re: Is the Linux kernel underfunded? Lack of quality and security?

On Sun, Jan 05, 2020 at 04:47:33AM +0100, Evan Rudford wrote:

> - Although the kernel will always remain in C, make serious efforts to
> introduce a safe language for kernel modules and perhaps for some
> subsystems.

Let me see if I've got it right - you suggest introducing an infrastructure
that would provide the bindings between the core kernel and those "safe
language modules" and maintaining its safety (from those languages' point
of view) through the changes of said core kernel *and* through the changes
of ABI of the languages in question?  That takes an impressive skillset
from the poor sods in question - on the level of people actively working
on the language implementation, _in_ _addition_ _to_ what's normally
required for the kernel work.  And that happy group would have to keep
track of the kernel changes.  That will certainly make everything more
secure; I just wonder where have you found the funding to cover the costs
of psychiatric care for the victims^Wproud members of that august group.
You do have that funding lined up, right?

Powered by blists - more mailing lists