Originally posted by mSparks
View Post
Really the google source you gave in fact shows it. You said xsecurelock only has a 2015 certificate. Why do other actively developed projects from google that had 2015 certificates that you can see in the wayback machine are now 2018 and newer. xsecurelock and other parts that cannot pass are outliers if you spend time reading. Yes the fact it had old certificate and majority of everything else had newer certificates should have had alarm-bells ringing in you head mSparks. Companies with well run 27000 process normally don't have outdated certificates unless they cannot get new versions. Yes the companies define of outdated change some are 3 some are 5 some are 10. Google is 5 years. So the 2017 certificates will be updated this year. 2015 certificate should have already been replaced. So 2 years ago the problem was show..
You said refer to this without noticing bugger me it proves that even google cannot make a X11 solution that can pass current 27000 series.
27000 has a lag between when the standard comes into existence and when at the latest you absolutely must follow it. We are in the lag at the moment.
In fact the screenlocker you picked the developer of that is clear that X11 screenlocker functionality is broken and google has no interest in fixing it. Yes google will migrate to Wayland at some point for their Linux workstations by what google developers are saying.
mSparks get me a ISO 27001:2022 Control A.7.7 screen locker for X11. Problem for you I know they don't exist and cannot exist without X11 protocol changes that no one is willing to fund..
Comment