658
California introduces age verification law for all operating systems, including Linux and SteamOS — user age verified during OS account setup (www.tomshardware.com)
submitted 8 months ago by to c/technology@lemmy.world
386 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 8 months ago (6 children)

You are right, it just says whoever "controls the OS", which is very vague. Even without going to open source, a user still controls the OS even on Windows or macOS. To a lesser degree of course, but in the same way a driver controls a car even if they can't or won't try to modify it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 8 months ago (5 children)

    The windows user uses the OS. The windows user does not control the OS. They only have access to the functions that Microsoft has provided. The Attorney General of California won't be able to argue that the sysadmin is the OS Provider of a Windows installation. The OS Provider of Windows is Microsoft.

    The Attorney General of California would easily be able to argue that the OS Provider of a particular Linux instance is the sysadmin of that instance.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 8 months ago* (4 children)

    They only have access to the functions that Microsoft has provided.

    And a user of Ubuntu only has access to the functions that Canonical has provided.

    Unless they have root access and modify the OS. Or they have administrator access on Windows and modify the OS. Which is the case for both by default. I don't really see the distinction. There is clearly a provider company behind both, and in both cases the user could add this age check functionality by themselves by installing an utility that provides it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 0 points 8 months ago* (last edited 8 months ago) (3 children)

    And a user of Ubuntu only has access to the functions that Canonical has provided.

    That is not at all accurate.

    Administrator access to Windows is not at all comparable to root access on Linux. Windows "root" access is held solely by Microsoft, and granted only to Microsoft employees and contractors. They are the only ones with the capability of changing Microsoft's binary blobs.

    Canonical doesn't restrict root access. Everyone who installs Ubuntu has root access by default.

    Suppose Canonical adds this capability to Ubuntu. Suppose I take an Ubuntu install, and remove this capability. Who is the provider of the resulting OS, Canonical, or me? Obviously, I am responsible for the changes; I am obviously the OS Provider in this scenario.

    What I am saying is that I was the OS provider before I made the changes.

    Let's remember that the law distinguishes between the OS and Applications running on that OS. They require that the signalling apparatus be included in the OS. Technologically, the distinction between OS and Application is somewhat arbitrary. For commercial OSes, it's pretty simple: The OS is what Microsoft declares to be part of "Windows" is the OS; everything else is an application.

    Suppose Microsoft refuses to include this signaling apparatus. The end user cannot modify Windows, so does not become liable as the "OS Provider". The user can bolt on the functionality as an application, but cannot make it part of the OS. Microsoft is the one facing the fines under this law.

    For FOSS software, the end user's root access gives them the ability to add this signaling capability to the OS running on their machines, even if Canonical refuses to distribute a compliant OS. The user's ability to make their own OS compliant with California law makes them the party liable for non-compliance.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 8 months ago* (last edited 8 months ago) (2 children)

    What does the comparability of root/admin access change in this situation?

    Suppose Microsoft adds this capability to Windows, and you edit the registry to disable it. How is that any different?

    I can see the argument for something like iOS. But on Windows you would be able to add or remove such functionality. What is the difference that makes the user the OS Provider on Ubuntu but not on Windows, in your eyes?

    Let's say you own a computer store in California, you sell Windows laptops, and you setup your preinstalled Windows image with the registry edit made, because customers don't like the silly age prompt. How are you not the OS Provider?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 8 months ago* (last edited 8 months ago) (1 child)

    Suppose Microsoft adds this capability to Windows, and you edit the registry to disable it. How is that any different?

    By allowing the end user to change it instead of locking it down, they are not making a good faith effort to comply, and they lose their liability protection. To maintain their immunity, at the very least they will need to prohibit Californians from disabling the feature.

    Canonical is prohibited from adding comparable terms.

    I can see the argument for something like iOS.

    How is iOS any different from Windows here?

    Let's say you own a computer store in California, you sell Windows laptops, and you setup your preinstalled Windows image with the registry edit made, because customers don't like the silly age prompt. How are you not the OS Provider?

    Again, to maintain their immunity under this law, they would have to prohibit me from doing this in their licensing agreement. My violation is what protects Microsoft. I would, indeed, be the OS provider in that scenario.

    But in the scenario you describe, I'm not the end user.

    Neither Canonical nor I can include the same restrictive terms in our OS offerings. We can simply inform our users that the OS is not California compliant. Our users become their own OS Providers as soon as they decide to use them in California.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 8 months ago

    All right, then your argument relies on the licensing difference, not any technical differences between Linux root / Windows admin or source code access. Which makes sense, but it's all hypothetical since neither company addressed this yet, either in the product or in the licensing.

  • permalink
  • fedilink
  • source
  • parent