Redox OS Crash Challenge
github.com
Redox OS Crash Challenge
1–10 of 82 posts
Re: Redox OS Crash Challenge
#2Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr.
No cynicism intended, just an observation from what I see around.
Re: Redox OS Crash Challenge
#3Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. No cynicism intended, just an observation from what I see around.
Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?
( proggit's got the cynical side going: https://www.reddit.com/r/programming/comments/7ryiih/redox_o... )
Re: Redox OS Crash Challenge
#4Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. No cynicism intended, just an observation from what I see around.
> Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr.
> No cynicism intended, just an observation from what I see around.
The difference is what happens when a bug is encountered. If it is caught and panicked upon, then that is safe predictible behavior that cannot be exploited into something like privilege escallation.
Re: Redox OS Crash Challenge
#5Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. No cynicism intended, just an observation from what I see around.
Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out? ( proggit's got the cynical side going: https://www.reddit.com/r/programming/comments/7ryiih/redox_o... )
No but the machine shouldn't do something stupid, like burn down.
Re: Redox OS Crash Challenge
#6Earlier quoted context omitted.
Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out? ( proggit's got the cynical side going: https://www.reddit.com/r/programming/comments/7ryiih/redox_o... )
No but the machine shouldn't do something stupid, like burn down.
The quote is about data, & now our code is data. The computer indeed should not burn down-- even if the kernel faults
Re: Redox OS Crash Challenge
#7Earlier quoted context omitted.
No but the machine shouldn't do something stupid, like burn down.
The quote is about data, & now our code is data. The computer indeed should not burn down-- even if the kernel faults
The kernel faulting is effectively burning down. In modern systems there is the concept of "isolation", if you give bad input to one program (e.g. the shell) the kernel shouldn't fault (taking down unrelated programs with it).
Re: Redox OS Crash Challenge
#8Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. No cynicism intended, just an observation from what I see around.
> Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. > No cynicism intended, just an observation from what I see around. The difference is what happens when a bug is encountered. If it is caught a…
Crash bugs caused by a panic can't necessarily be used for privilege escalation, but they can certainly be used for DOS attacks.
Re: Redox OS Crash Challenge
#9Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. No cynicism intended, just an observation from what I see around.
> Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. > No cynicism intended, just an observation from what I see around. The difference is what happens when a bug is encountered. If it is caught a…
My point is that privilege escalation can happen from logical bugs
Re: Redox OS Crash Challenge
#10Rust being advertised as a safe language (which is true) got so much into the user's heads that they think if they write it in Rust it's safe and crash free by default. There are plenty of security/safety bugs that aren't about dereferencing a null or accessing invalid ptr. No cynicism intended, just an observation from what I see around.
I don't see anything in the link that seems to imply that they think Redox OS is going to be crash free? In fact this seems to be the opposite, it looks to me like they're looking for bugs to squash.