[Patrickmi]

Am new to these kernel space but isn’t writes operation more security at risk than Reads if it is why not break gofer into 2 categories one writes, one reads embed the one with reads with sentry user space, this may not show any significant performance in real world use but it gets both benefits

[nomel]

> writes operation more security at risk than reads

I think, in the context of security, this is like asking if it's worse to die by a car or die by a bus.

[Patrickmi]

Lol at least one is recoverable

[nomel]

Security exists because of the meaning of the bits. If those bits represent credentials to your bank account, then "recoverable" hits different.

[Bilal_io]

When you think of security you gotta think of Confidentiality, Integrity and Availability.

If you make reads less secure writes, then you'd be weakening the Confidentiality aspect.

[nine_k]

One would only need to read your password via some unsecured hole, once.

The rest of the identity theft and pillaging your accounts would require no security weaknesses, just things working correctly in presence of legitimate credentials.

[dilyevsky]

The risk here is that there's a bug in kernel that can enable dos / local code execution by the caller. Also like others pointed out - reads can be equally harmful if you read ssh private keys and whatnot.