• 10 Posts
  • 1.77K Comments
Joined 2 years ago
cake
Cake day: July 31st, 2023

help-circle



  • You can disable UAC (thinking practical, not necessarily security minded - but for an auto login w/o password, what’s security?)

    It’s not just the UAC prompt. Any window created by an elevated process will block synthetic input events created by lower privilege processes.

    Popups: yes. But then you’d need to actively use other software besides steam. Why would you do that, if using only a controller?

    • Game launchers installed as part of the Steam game.
    • Driver software automatically installed by Windows.
    • Windows itself, sometimes.

    Also that can happen in Linux, too.

    It depends on your DE and configuration. In KDE with Wayland, you can set it up to strictly enforce focus stealing prevention. The way that works is essentially by only allowing another program to steal focus if it’s the result of some user interaction.

    For the logoff or shutdown: Set or createHKEY_CURRENT_USER\Control Panel\Desktop\AutoEndTasks to 1 to auto kill hanging/not ending processes automagically. Also you can use WaitToKillAppTimeout there to define how long windows should wait before killing the processes (in milliseconds).

    The fact that these are buried in the registry… thanks, though. These will be useful. I concede this point.

    And regarding bitlocker after a bios update: why would you use bitlocker on such a machine (auto login on boot which would allow access to all files anyways)?

    Because it’s the default that is forced onto the user.

    Anyways, set or create HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BitLocker\PreventDeviceEncryption to 1 to prevent bitlocker from running after an upgrade. With Pro, you could also leverage GPOs for that.

    Call me cynical, but I don’t think this will work forever. Microsoft has been boiling the frog with local accounts over Windows 11’s entire lifetime, at first allowing them, then hiding them, then making the bypass command only work under specific circumstances, etc.

    All it takes to destroy the UX is force-enabling BitLocker exactly once, and most of the people using the device won’t know how to undo it (or worse, be locked out without the recovery key)


  • Also not a lawyer, but in the past, I did a lot of research into how intellectual property works in the United States.

    I’ve heard it over and over that trademark owners are legally required to defend their trademarks from potential violators like this, or they can lose the trademark.

    This isn’t entirely true. As long as the trademark is actually renewed, it doesn’t need to be aggressively defended.

    There are a couple of reasons why they might choose to defend it regardless. One of the major ones is to deter other entities from thinking they too could get away with violating it. An actual, legally-relevant reason to defend it would be to prevent the mark from genericization. That’s when a trademark like a brand name colloquially becomes used to refer to an entire class of products, such as with the Escalator™.

    For an example of a company whose trademark was at risk of genericization, look no further than Nintendo. They saved it by defending the trademark tooth and nail while using marketing to reinforce that their product is the Nintendo and not a Nintendo. If people had kept referring to video game consoles as “Nintendos” like they used to back in the 80s and 90s, another company may have been able to successfully challenge the trademark and opened the flood gates for products like the “Microsoft® Xbox 720 nintendo”. Nintendo the corporation is still a bunch of overly-litigous assholes, but back then, they actually needed to be.

    In Eminem’s case, it’s probably as a deterrent. Unless people have started referring to Caucasian rappers as “eminems” without me noticing, his brand is at absolutely no risk of being genericized.



  • Agreed. The call trace shows it occurred as part of a drm_ function, which is related to the DRM (Direct Rendering Manager) subsystem.

    There’s a chance it might not be the root cause, but the more obvious answer is that the Nvidia driver managed to corrupt a kernel data structure.