I have installed different Linux distros in 4-5 devices in the last year, including a laptop with an Nvidia GPU and a random NUC off Aliexpress. In all cases everything worked out of the box after a fresh installation--and as far as I remember the situation was the same ~10 years ago, when I first started using it. There are hiccups here and there, but nothing I cannot live with. I do tech support for my girlfriend'd mac, and there are just as many small issues there.
All this wall of texts to say that, respectfully, when you write
>Earlier this year I built a new desktop and installed my normal Linux distro and the screen wouldn’t work after login
the issue might simply be that you are doing something very wrong and/or not following the proper instructions for whatever distro you are using.
For me:
- Easier access to books in other languages or out of print
- Quick access to a dictionary
- Backlight for reading in bed or in the evening
- Pocketability
- Way cheaper if you read a lot of public domain books (or have a parrot sitting on your shoulder)
That said, I have a jailbroken Kindle, but I am not giving a cent to Amazon. Should it break I'd just get a Kobo.
Nowadays AA [1] is IMO a better choice for users, but aside from that I cannot imagine these changes making much of a difference. There's plenty of ebook sources (Kobo, public libraries, etc) whose DRM are trivial to break (meaning Adobe and, as of a few weeks ago, LPCM). For what little content is exclusive to Kindle, it will just end up like WEB-DL content from streaming services: a handful of knowledgeable uploader with a KU subscription ripping content en masse—and good luck stopping them.
So what would be the best practice in a situation like that? I would (naively?) imagine that a null pointer would mostly result from a malloc() or some other parts of the program failing, in which case would you not expect to see errors elsewhere?
Unless I am misunderstanding the discussion on GitHub, the attacker would still need to know the exact path where the file is saved, and the name of the file itself. Even then, all they can do is download the file from your device--which they could just torrent themselves for a fraction of the effort.
The absolute worst thing I can see in there is that an third party who somehow managed to get a link to one of your library items (either directly from you or from one of your users--or by spending the next decade bruteforcing it I guess) could stream said item:
https://github.com/jellyfin/jellyfin/issues/5415#issuecommen...
Everything else looks to me like unimportant issues, that would provide someone who's already logged in as a user minor details about your server.
If you expose Jellyfin on 443, have HTTPS properly set up (which Caddy handles automatically), your admin password is not pswd1234 (or you straight up disable remote admin logins), and use a cheap .com domain rather than your IP--what is the actual attack surface in that case?
As far as I can remember that is more or less what is usually suggested by Jellyfin's devs, and I have yet to see something that convinces me about its inadequacy.
For whatever reason people here and on Reddit will tell you that you need to have Jellyfin pass through five VPNs, otherwise nasty things will happen. Meanwhile the actual devs suggests simply setting up a reverse proxy, which you can do in two lines with Caddy:
https://jellyfin.org/docs/general/post-install/networking/re...
All this wall of texts to say that, respectfully, when you write >Earlier this year I built a new desktop and installed my normal Linux distro and the screen wouldn’t work after login the issue might simply be that you are doing something very wrong and/or not following the proper instructions for whatever distro you are using.