Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[flagged]


> Recently a Rust sudo replacement (maybe this one?) got a security audit.

It is the same one. It's weird because, this article is from August. But the one you're referencing is from three days ago: https://ferrous-systems.com/blog/sudo-rs-audit/

> the severity was worse in the Rust version.

I am unsure where you got this. It's the same vulnerability.


The link you cite says it was worse in the Rust version:

> During the audit, it came to light that the original sudo implementation was also affected by [CLN-001: relative path traversal vulnerability], although with a lower security severity due to their use of the openat function.


Thank you. I literally re-read it to try and find this, and missed it somehow. Guess I need to drink even more coffee.


> Guess I need to drink even more coffee.

Have you tried green tea? It contains a substance that offsets the sideeffects of caffeine a little.

https://en.wikipedia.org/wiki/Theanine?wprov=sfla1

Disclaimer: Zero Caffeine for me either way. Makes my ADD way worse. Theanine was nice though. Okay i lied, i allow myself dark chocolate sometimes.


I don't see how openat() would help.


Re: I am unsure where you got this. It's the same vulnerability.

> During the audit, it came to light that the original sudo implementation was also affected by this issue, although with a lower security severity due to their use of the openat function.



> It not only had the same security vuln that hit the non-Rust version

The audit of the rust version is how they discovered the vulnerability in the C version.


> Like building an entirely new car company around only making side-impact collisions safer

...which still results in safer cars overall, so I don't see the problem. Especially if those cars are almost completely immune to side-impact collisions and if it's actually not a car company but a technology every manufacturer can use for future products.


You don't see the problem in starting an entirely new car manufacturer from scratch just to fix one safety issue?

> if it's actually not a car company but a technology every manufacturer can use for future products

In that case it's like every single manufacturer changing their engine design in order to have a different wiring harness with a slightly thicker shielding around a single cable. The amount of work and cost involved, and risk to every other part of the process, just to fix one tiny thing, makes no sense. It is an insane amount of work for extremely little benefit.


> it's like every single manufacturer changing their engine design in order to have a different wiring harness with a slightly thicker shielding around a single cable.

Car manufacturers improve their engine designs all the time.

It's also not uncommon that programs get rewritten in order to achieve better results, and recently Rust happens to be a popular choice where both speed and security are important. There's nothing extraordinary about it really.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: