Cybersecurity

5695 readers

232 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Be respectful. Everyone should feel welcome here.
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
No Ads / Spamming.
No pornography.

Community Rules

Idk, keep it semi-professional?
Nothing illegal. We're all ethical here.
Rules will be added/redefined as necessary.

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !cybersecurity@lemmy.capebreton.social !securitynews@infosec.pub !netsec@links.hackliberty.org !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 1 year ago

MODERATORS

kid@sh.itjust.works

Lanky_Pomegranate530@midwest.social

223

GitHub disables XZ Repository (www.phoronix.com)

submitted 7 months ago by wyre@sh.itjust.works to c/cybersecurity@sh.itjust.works

19 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] sugar_in_your_tea@sh.itjust.works 8 points 7 months ago (1 children)

It looks like someone made a Rust implementation, which is a lot slower and only does decompression, but it's at least a rival implementation should zstd get some kind of vulnerability.

[–] Killing_Spark@feddit.de 8 points 7 months ago (1 children)

Yep that would be me :)

There is also an independent implementation for golang, which even does compression iirc (there is also a golang implementation by me but don't use that. It's way way slower than the other one and unmaintained since I switched to rust development)

[–] sugar_in_your_tea@sh.itjust.works 1 points 7 months ago (1 children)

Awesome! It's impressive that it's decently close in performance with no unsafe code. Thanks for your hard work!

And that Go implementation is pretty fast too! That's quite impressive.

[–] Killing_Spark@feddit.de 1 points 7 months ago (1 children)

Sadly it does have one place with unsafe code. I needed a ringbuffer with an efficient "extend from within" implementation. I always wanted to contribute that to the standard library to actually get to no unsafe.

[–] sugar_in_your_tea@sh.itjust.works 1 points 7 months ago (1 children)

Ah, I saw a PR from like 3 years ago that removed it, so it looks like you added it back in for performance.

Have you tried contributing it upstream? I'm not a "no unsafe" zealot, but in light of the xz issue, it would be nice.

[–] Killing_Spark@feddit.de 1 points 7 months ago (1 children)

Have you tried contributing it upstream?

I didn't yet just because I didn't get around to it (and because I am not sure the std lib even wants this feature).

I’m not a “no unsafe” zealot, but in light of the xz issue, it would be nice.

I don't think the two relate. I wouldn't drop any dependency, the ringbuffer is implemented in the same repo.

[–] sugar_in_your_tea@sh.itjust.works 1 points 7 months ago

Yeah, they're not really related. I'm just thinking there might be more scrutiny on compression due to the exploit.

That said, yours doesn't support encoding anyway, so it's kind of moot.