Wayne Thornton created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5502
## Summary <!-- Please provide as much information as possible such as error messages or attaching logs --> California Law AB-1043 (Digital Age Assurance Act) comes into effect January 1st, 2027 for new operating systems, and July 1st, 2027 for existing operating systems. This law applies to any operating system or company which seeks to be used in California. It should be noted that Colorado is implementing a similar law that has yet to be signed by the governor. It seeks to require all operating system vendors, including Linux, FreeBSD, macOS, Windows, etc. to implement an age-verification methodology with an age declaration flow and signal API that can be accessed by developers running third-party applications on the operating system. The fine for not complying is $7,500.00 per incident/user not verified. While it can be construed that this law applies to general-purpose operating systems only, due to the flexibility of RTEMS to run everywhere from spacecraft to consumer smart devices where applications can be developed by third-party companies and distributed to run on RTEMS, does it make any sense whatsoever to begin thinking about how to implement a very basic skeleton API just for compliance? ## Steps to reproduce N/A -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5502 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
