this post was submitted on 24 Aug 2024
380 points (98.5% liked)

Linux

47337 readers
1323 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

There's been some Friday night kernel drama on the Linux kernel mailing list... Linus Torvalds has expressed regrets for merging the Bcachefs file-system and an ensuing back-and-forth between the file-system maintainer.

you are viewing a single comment's thread
view the rest of the comments
[–] solrize@lemmy.world 94 points 3 weeks ago (62 children)

Can someone say why bcachefs is interesting? Btrfs I can sort of understand. I haven't much kept track of most others.

[–] pimeys@lemmy.nauk.io 53 points 3 weeks ago* (last edited 3 weeks ago) (15 children)

For me the reason was that I wanted encryption, raid1 and compression with a mainlined filesystem to my workstation. Btrfs doesn't have encryption, so you need to do it with luks to an mdadm raid, and build btrfs on top of that. Luks on mdadm raid is known to be slow, and in general not a great idea.

ZFS has raid levels, encryption and compression, but doesn't have fsck. So you better have an UPS for your workstation for electric outages. If you do not unmount a ZFS volume cleanly, there's a risk of data loss. ZFS also has a weird license, so you will never get it with mainline Linux kernel. And if you install the module separately, you're not able to update to the latest kernel before ZFS supports it.

Bcachefs has all of this. And it's supposed to be faster than ZFS and btrfs. In a few years it can really be the golden Linux filesystem recommended for everybody. I sure hope Kent gets some more help and stops picking fights with Linus before that.

[–] LemmyHead@lemmy.ml -5 points 3 weeks ago (2 children)

Encryption and compression don't play well together though. You should consider that when storing sensitive files. That's why it's recommended to leave compression off in https because it weakens the encryption strength

[–] nous@programming.dev 5 points 3 weeks ago (1 children)

How does that work? Encryption should not care at all about the data that is being encrypted. It is all just bytes at the end of the day, should not matter if they are compressed or not.

[–] ThanksForAllTheFish@sh.itjust.works 4 points 3 weeks ago (1 children)

Disabling compression in HTTPS is advised to prevent specific attacks, but this is not about compression weakening encryption directly. Instead, it’s about preventing scenarios where compression could be exploited to compromise security. The compression attack is used to leak information about the content of the encrypted data, and is specific to HTTP, probably because HTTP has a fixed or guessable structure.

[–] nous@programming.dev 4 points 3 weeks ago* (last edited 3 weeks ago)

Looks to be an exploit only possible because compression changes the length of the response and the data can be injected into the request and is reflected in the response. So an attacker can guess the secret byte by byte by observing a shorter response form the server.

That seems like something not feasible to do to a storage device or anything that is encrypted at rest as it requires a server actively encrypting data the attacker has given it.

We should be careful of seeing a problem in one very specific place and then trying to apply the same logic to everything broadly.

[–] pimeys@lemmy.nauk.io 4 points 3 weeks ago (2 children)

It is only in TLS where you have to disable compression, not in HTTP.

https://security.stackexchange.com/questions/19911/crime-how-to-beat-the-beast-successor/19914#19914

Could you explain how a CRIME attack can be done to a disk?

[–] nous@programming.dev 4 points 3 weeks ago

There is also the BREACH which targets gzip/deflate compression on http as well. But also, don't see how that affects disk encryption.

[–] LemmyHead@lemmy.ml 2 points 3 weeks ago

I can't explain, perhaps due to my limited knowledge about the subject. I understood that compression was a weakening factor for encryption years ago when I heard about it. Always good to do your own research in the end 🙃

load more comments (12 replies)
load more comments (58 replies)