usbarmory
totally-safe-transmute | usbarmory | |
---|---|---|
17 | 22 | |
245 | 1,338 | |
- | 0.7% | |
0.0 | 5.8 | |
over 1 year ago | 15 days ago | |
Rust | Ruby | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
totally-safe-transmute
-
Sudo Replacement
For example, there is this (pure safe Rust) code: https://github.com/ben0x539/totally-safe-transmute/blob/main... which accesses external resources (/proc/self/mem) in order to violate the safety guarantees.
-
A rust crate that lets you compress ASCII text to a single Unicode "character"
The first is the totally_safe_transmute crate. I mean, who wouldn't love library code that has .expect("welp") and .expect("oof") as its error handling? But that's not even the really scary part. Issue #2 ("i hate this") remains open to this day, but for obvious reasons there's no chance of resolution. This post has some context and a line-by-line explanation of how it works.
-
What do you expect from Rust in 2023?
You mean like this?
-
In C# you can transmute without `unsafe`
You can also do that in rust on linux: https://github.com/ben0x539/totally-safe-transmute/blob/master/src/lib.rs
-
Why choose Rust
I want to correct this statement: Rust can be safer, but not if a library you use contains unsound code. Unsoundness is most often caused by unsafe code, but not always (totally_safe_transmute, anyone?). There is a misconception that unsafe code blocks are always unsound and should be avoided at all costs, but they're completely fine if the safety contracts are upheld. In fact, unsafe blocks isolate the potential issues to make it easier to identify where undefined behavior may be occurring. unsafe code blocks are a feature of the language, and their usage should not be viewed as opting out of any safety the language provides, imo.
-
"# NONONONONONO DON'T YOU FUCKIN' DARE the safety features are there so that your programs aren't filled to the brim with security vulnerabilities. Unless you care A LOT(And I mean A LOT A LOT) about compile times, never use `unsafe`."
Just reimplement totally_safe_transmute in Zig. No need for unsafe.
-
I mean, it solves most library conflicts
Why transmute() when you can totally_safe_transmute()?
- Safe Transmute
-
Static Analyzer Rudra Found over 200 Memory Safety Issues in Rust Crates
Well, there is always the totally-safe-transmute.
-
// SAFETY: NO
They should use https://github.com/ben0x539/totally-safe-transmute
usbarmory
-
Go: What We Got Right, What We Got Wrong
Niklaus Wirth, rest his soul, would disagree.
Like would the the selling USB Armory, with Go written firmware.
https://www.withsecure.com/en/solutions/innovative-security-...
Back in my day, writing compilers and OS services were also systems programming.
-
What's Zig got that C, Rust and Go don't have? [video]
Not only you can fit Go into a kernel, there is at least two products that do so.
TamaGo, used to write the firmware used in USB armory.
https://www.withsecure.com/en/solutions/innovative-security-...
TinyGo, which even has official Arduino and ARM support, and is sponsored by Google
https://tinygo.org/
Ah but that isn't proper Go! Well neither is the C code that is allowed to be used in typical kernel code, almost nothing from ISO C standard library is available, and usually plenty of compiler specific language extensions are used instead.
-
Bare Metal Rust in Android
> Since 80s everybody designs systems on top of C.
More like since the 1990's, and mostly thanks to the GNU Manifesto and FOSS uptake that took the steam out of C++ adoption being pushed by Apple, IBM and Microsoft.
There is firmware in production written in Go,
https://www.withsecure.com/en/solutions/innovative-security-...
- USB armory – small secure computer from WithSecure (previously F-secure)
-
How is Go used in Linux based environments in various companies?
Not exactly but close. No gocoin, but custom (minimal) client based on btcsuite libs. And it is run on USB Armory SoC.
-
avbroot: Re-lock bootloader with Magisk installed!
Relocking with your own key is only for experts, it's similar to the USB Armory device for embedded electronics. If you get it wrong you can brick the device, the purpose of doing it is to protect against certain types of boot attacks (like if somebody can get temporary physical access to your phone or even just plant a malicious USB cable which could potentially push malware. If you don't know what you're doing, stay on stock OS.
-
Google: C++20, How Hard Could It Be
Plenty of software that is written in C and C++, can be easily done in Go as well, in fact in any AOT compiled managed language.
C++ was born to write distributed systems, nowadays it hardly matters on cloud native infrastructure beyond the OS and hypervisors layer.
This is how Go can be a competitor to C and C++, just like Inferno was basically Plan 9 with Limbo for userspace and very little C beyond the kernel.
And then there are those crazy folks that believe they should ship bare metal AOT compiled languages regardless of others think.
https://www.withsecure.com/en/solutions/innovative-security-...
-
Rust 2024 the Year of Everywhere?
Of course it can, there are companies shipping products written in bare metal Go.
https://www.withsecure.com/en/solutions/innovative-security-...
https://github.com/usbarmory/tamago
- Generics can make your Go code slower
- Rust Compiler Ambitions for 2022
What are some alternatives?
tinyvec - Just, really the littlest Vec you could need. So smol.
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
tamago - TamaGo - ARM/RISC-V bare metal Go
SkyFM
rust - Rust language bindings for TensorFlow
go-is-not-good - A curated list of articles complaining that go (golang) isn't good enough
advisory-db - Security advisory database for Rust crates published through crates.io
zerosharp - Demo of the potential of C# for systems programming with the .NET native ahead-of-time compilation technology.
UnsoundCrates - Black list of all crates that promotes unsoundness
project-safe-transmute - Project group working on the "safe transmute" feature
biscuit - Biscuit research OS