Ancestors

Toot

Written by ✙ dcc :pedomustdie: :phear_slackware: on 2025-01-29 at 21:15

Rust mem eror'd....

thread 'tokio-runtime-worker' panicked at src/player.rs:97:55:

called Option::unwrap() on a None value

I THOUGH IT WAS MEMEORY SAFE SAAR :troll:

=> More informations about this toot | More toots from dcc@annihilation.social

Descendants

Written by Detaeper on 2025-01-29 at 21:17

@dcc yeah it stopped you from dereferencing null, and told you where it was doing it from, quite helpful actually. in C it would've just told you "Segmentation Fault" and left you to eat shit

=> More informations about this toot | More toots from nyanide@lab.nyanide.com

Written by ✙ dcc :pedomustdie: :phear_slackware: on 2025-01-29 at 21:18

@nyanide I did not do anything lol, thats the code the inv thing uses.

=> More informations about this toot | More toots from dcc@annihilation.social

Written by Detaeper on 2025-01-29 at 21:18

@dcc you may want to report this as a bug

=> More informations about this toot | More toots from nyanide@lab.nyanide.com

Written by Phantasm on 2025-01-29 at 21:18

@dcc Never talk about std::mem::forget to Rust evangelists.

=> More informations about this toot | More toots from phnt@fluffytail.org

Written by Detaeper on 2025-01-29 at 21:19

@phnt @dcc what's so bad about it

=> More informations about this toot | More toots from nyanide@lab.nyanide.com

Written by Phantasm on 2025-01-29 at 21:23

@nyanide @dcc It leaks memory, something some Rust programmers refuse to acknowledge that Rust can do.

To be more precise it takes ownership of the argument and forgets it without running it's destructor.

By it self it's basically harmless as you have to call it manually, but it could possibly be leveraged to force a specific heap order that you can then exploit if you find a way to break out of the Rust bounds checking. The chance of this getting exploited in the future is near zero.

=> More informations about this toot | More toots from phnt@fluffytail.org

Written by mr64bit on 2025-01-29 at 21:42

@phnt @dcc @nyanide I'm convinced there's basically no overlap between the rust evangelists everyone complains about and people who actually write rust. Then again, I never see the evangelists either, seems be a strawman for the most part.

=> More informations about this toot | More toots from mr64bit@p.mr64.net

Written by Phantasm on 2025-01-29 at 21:58

@mr64bit @dcc @nyanide It's been a long time since I saw someone like this. They seemingly mostly went away after the rewrite in Rust meme died out. Recently it's mostly people that actually write Rust trying to force Rust onto other projects, because muh memory safety and other stuff.

The last time I had any kind of discussion with someone that could be described as a Rust evangelist was during the Lina Linux drm threads. It was about why Rust shouldn't be used in Linux due to its non-existent ABI and other related stuff. They deleted their replies a few days after for whatever reason.

But I still like to shitpost about Rust every once in a while, because somehow barely funny posts make them react every time. That includes today's posts.

In the end, I don't have a problem when a project is written in it, but I still stand by my opinion that it shouldn't be used for low-level programming. It's just not a language for it. There's no stable ABI, interacting with Rust code outside of Rust is painful, static-linking everything is stupid and cargo is borderline garbage.

=> More informations about this toot | More toots from phnt@fluffytail.org

Written by ins0mniak on 2025-01-29 at 21:59

@phnt @dcc @nyanide @mr64bit

=> View attached media

=> More informations about this toot | More toots from ins0mniak@majestic12.airforce

Written by syzygy on 2025-01-29 at 22:03

@ins0mniak @dcc @phnt @nyanide @mr64bit

Nothing says "h4ck3r" more than a flashy rainbow diglet title that's a wrapper another script.

=> More informations about this toot | More toots from sysrq@lab.nyanide.com

Written by Detaeper on 2025-01-29 at 22:03

@sysrq @ins0mniak @dcc @mr64bit @phnt nmap poopsock.org | lolcat

=> More informations about this toot | More toots from nyanide@lab.nyanide.com

Written by syzygy on 2025-01-29 at 22:04

@nyanide @dcc @ins0mniak @mr64bit @phnt

=> View attached media

=> More informations about this toot | More toots from sysrq@lab.nyanide.com

Written by ins0mniak on 2025-01-29 at 22:06

@sysrq @dcc @phnt @nyanide @mr64bit Ikr? what the hell is the point even?

nmap works just fine, I don't see what it brings to the table.

=> More informations about this toot | More toots from ins0mniak@majestic12.airforce

Written by syzygy on 2025-01-29 at 22:11

@ins0mniak @dcc @phnt @nyanide @mr64bit

I have no fucking clue, I think it's for street cred "look at my flashy h4cker tool!". Like a few years ago I was looking into stuff like GSM and SMS spoofing and found a bunch of github repos belonging to kids all showing off their "SMS spoofing" scripts, but all of them were just the same bash script that used a free texting API but with different names/colour schemes.

=> More informations about this toot | More toots from sysrq@lab.nyanide.com

Written by Detaeper on 2025-01-29 at 22:12

@sysrq @ins0mniak @dcc @mr64bit @phnt welcome back to the wonderful world of script kiddie communities, it's changed since 2008

=> More informations about this toot | More toots from nyanide@lab.nyanide.com