ShortN0te

It is not about the drivers, framework has most likely not the capability to develop drivers for their Laptops, it is the manufacturer's job. All framework can do is selecting parts that are already supported by the kernel. Also a driver can take several years until it actually gets into a not rolling release distro like Ubuntu or mint since they do not use the newest kernel.

This collab is more about making sure, that when you install those distros everything works out of the box which is not a given, depending on the compile flags for the kernel they used or what packages are coming installed by default.

Open standards are the first step of a functional transition to an open government. From there Open Source Software can compete against commercial software, once the ppl see that the FOSS offers the same features then the proprietary paid software they can easily switch to it. With open standards they only need to train the users, no data to migrate etc.

Focus instead on enforcing standards' compliance so i can open a .docx with any program and be usable anywhere.

That's an impossible task. Not even Microsoft manages that. Do not want to count how often i used libreOffice to repair or convert an older MSOffice file so it can be opend with modern Versions of MSOffice.

Once there was a 500MB Excel Sheet with lime 500-1000 used Cells, opened and saved it to.a xlsx file using libreOffice and reduced it to a few MB while still being fully functional.

Would it be not much easier (and more portable) if you create a Linux VM in for example VirtualBox? From there you could just follow any Linux guide.

The cheap models can not be flashed with openwrt since they use some proprietary drivers or something.

The complete Opal series is not supporte iirc.

You should have read the post more carefully. The CVE affects every OS. Just the first shown example is Windows only.

Also, the relevant commits are outlined in the first paragraph. This article is not for the stupid user it's a technical analysis on a few ways to exploit it and for those cases the commits are more relevant than the version. Also saying which versions are affected is not that easy, commits can be backported into an older version by for example the packager.

You want the mail-crypt-plugin in dovecot.

Extracting the key from a TPM is actually trivial but immense time consuming.

Basically this with probably more modern chips and therefore even smaller cells. https://youtu.be/lhbSD1Jba0Q

Also sniffing is a thing since the communication between CPU und TPM is not encrypted.

TPM is not only used by the system encryption. But no i do not use it for it. Not because of privacy, cause of security reasons.

Basically, when you do not run server side transcoding and instead rely on client side support you will run from time to time into issues. Jellyfin does not have the ppl to get every client to work with all the different formats on every hardware.

1080 h264/h265 does not say much about the media format. Those codec differentiate in things like Chroma (4:2:0; 4:4:4, etc) or in color depth like 8 or 10 bit. So not every h264 media file does run on the same hardware. Audio codecs are even more complicated.

I think since i setup my hardware transcoding I ran into a not playable file once. But depending on the hardware it can be worse. On android TV you may have to play around with the settings.

I understand that this can be a deal breaker for some ppl.

1. Not sure what you mean by that. Jellyfin has had an up to date version in the play store for years.
2. Yes every Profile is separated into its own account, that's by design and will most likely never change. An easy PIN option in the local network existed for years. Now you can even login with your phone app by entering a displayed PIN.
3. I remember very few media that i had issues with in the past. Depending on the transcode hardware you have some things can be tricky

Any software potentially has security issues. The matter is how they deal with it.