Hi Andrew, > On Jul 27, 2016, at 10:25 PM, Andrew Z <form...@gmail.com> wrote: > And why do I want this?
Maybe you don't =). Just incase it helps, I'll try to elaborate on the two main features we mentioned. 1. We needed to lock desktops without hiding the graphical applications / displays that are running on that desktop. Even though the screen is locked, the desktop and whatever applications are running remain visible and keep updating. 2. We needed to allow a group of users (rather than just the user that happened to be logged in graphically) to unlock the screen. The screen can be configured to be unlocked by any set of users or groups recognized by the OS. They use their own username and password, so there's no need to share passwords. This is useful for us in operations where graphical applications and screens need to remain running through shifts, need to be locked when not actively used, and need to be unlock-able by whoever the current operator is. Any more comments or questions are always welcome. Thanks! Devin > On Jul 15, 2016, at 11:41 AM, Devin A. Bougie <devin.bou...@cornell.edu> > wrote: > > Cornell's Laboratory for Accelerator-based ScienceS and Education (CLASSE) is > pleased to share our Transparent Screen Lock for Enterprise Linux. Tested on > SL6/7 and GPLv2 licensed, this software provides a transparent screen lock > over one's desktop. A configurable list of groups are able to unlock the > screen, and logs document who unlocked the screen when. > > This software has been used for over two years and proven useful in kiosk and > operational environments where graphical displays need to stay running, > updating, and visible, but to comply with various security policies the > screen must lock after defined periods of inactivity. > > To download the code or contribute to the project, please visit us on github. > Additional issue reports and any code contributions would be greatly > appreciated. > > https://github.com/CLASSE-CornellUniversity/EnterpriseLinux-TransparentScreenLock
