• 0 Posts
  • 667 Comments
Joined 2 years ago
cake
Cake day: July 29th, 2023

help-circle
  • Someone I personally knew almost gave up on Linux because their mint install would have screen tearing issues due to an outdated driver module and kernel, since Mint follows close to Ubuntu’s kernel releases which are slow.

    Cutting edge and bleeding edge kernels is one of Linux’s biggest strengths because 99% of driver modules are in the kernel, so keeping it up to date will significantly reduce the chances of issues with your hardware, especially if its anything new.

    You dont need to know the version, but knowing that your updates are based on cutting edge latest stable is what can save you from driver headaches.



  • Do these updates not go through any rigorous testing at all

    Lol no, MSFT infamously dropped their entire Hardware QA team after WIndows 7 and instead relied on the also infamous insider hub to get QA “feedback” from home users instead, leading to the also infamous Windows 8 disaster and slightly less infamous critical CVEs that went unaddressed because MSFT ddidn’t even bother to read the insider hub posts.

    Oh and they didn’t learn anything and kept running with the insider hub well into Windows 10 & 11.









  • Same, I enjoy the classic shared library and package system which I still feel is superior to flatpak versions in most cases, even ignoring the technical aspects of each.

    Tried silverblue once and it just felt more like android to me, and I even found myself using RPM layers almost immediately for core things that dont ship as Flatpak because its infeasible.

    Plus Bazzite has its own release schedule which I feel like slightly removes the benefit of Fedora kernels being cutting edge, with critical packages updated almost as fast as Arch.

    The good thing though is that it’s much more dummy proof, so I would feel comfortable letting anyone use it with zero experience, whereas I only recommend Fedora to those who have an inherent interest in Linux.







  • This one is funny because it 100% still exists somewhere, but I haven’t had the chance to verify it again.

    Okay so basically its a data recorder box (ex: brainbox) that connects to a bunch of industrial sensors and sends the data over the network with your preferred method.

    Builtin firmware gives you an HTTP webui to login and configure the device, with a user # and password.

    I think the user itself had a builtin default admin which was #0, which everyone uses since there wasn’t really much use for other users.

    Anyway, I was looking at the small JS code for the webui and noticed it had an MD5 hashing code that was very detailed with comments. It carefully laid out each operation, and explained each step to generate a hash, and then even why hashes should be used for passwords.

    Here’s the kicker: It was all client side JS, so the login page would take your password, hash it, and then send the hash over plaintext HTTP POST to the server, where it would be authenticated.

    Meaning you could just mitm the connection to grab the hash, and then login with the hash.

    I sat there for like 10 minutes looking at the request over and over again. Like someone was smart enough to think “hey let’s use password hashing to keep this secure” and then proceeded to use it in the compleltly wrong way. And not even part of like a challenge/handshake where the server gives you a token to hash with. Just straight up MD5(password).

    It was so funny because there were like a hundred of these on a network, so getting a valid hash was laughably easy.

    I never got to check if this was fixed in a newer firmware version.




  • mlg@lemmy.worldtomemes@lemmy.worldOne media player to rule them all
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    13 days ago

    VLC sucks ass when you want to do any type of live transcoding or remuxing without setting up a video stream. Especially with multichannel audio:

    This has been an issue ever since feature added, the maximum bitrate you can set is 512 kb/s on every codec, despite codecs that support more.

    The bug thread for this was basically “stop complaining about our shit UI and use the CLI”

    Much prefer Kodi for this purpose, and an ffmpeg based player for lightweight stuff.