hashpwn

Home | Donate | GitHub | Matrix Chat | PrivateBin | Rules

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Systems Programming: Memory Safety

Solved General Discussion

2 Posts 1 Posters 777 Views 1 Watching

C Offline
C Offline
cyclone
Admin Trusted
wrote on last edited by cyclone

#1
With a significant number of CVEs stemming from memory safety issues in C systems programming, what is the best path forward?
1. Adopt better C practices
2. Enhance C with memory safety
3. Zig
4. Rust
Also, vote in my Mastodon poll:
https://infosec.exchange/@cyclone/114320672977305492
Sysadmin by day | Hacker by night | Go Dev | hashpwn
3x RTX 4090 3x RTX 2080ti
Forum Rules
1 Reply Last reply

0
C Offline
C Offline
cyclone
Admin Trusted
wrote on last edited by cyclone

#2

Thanks to everyone who played along!

Rust is the clear favorite out of the 59 responses.
https://www.rust-lang.org/

With Zig trailing behind for second place.
https://ziglang.org/
Sysadmin by day | Hacker by night | Go Dev | hashpwn
3x RTX 4090 3x RTX 2080ti
Forum Rules
1 Reply Last reply

0
C cyclone has marked this topic as solved on

Hello! It looks like you're interested in this conversation, but you don't have an account yet.

Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

With your input, this post could be even better 💗