1. Jul 21, 2023
    • Vincent Bernat's avatar
      Rename XSECURELOCK_SAVER_STOP_ON_DPMS (#157) · 8a448bd5
      Vincent Bernat authored
      The correct name should be XSECURELOCK_SAVER_STOP_ON_BLANK. We also
      starts children when screensaver is on, but screen is not blanked, or
      when screensaver is one and screen is blanked, but this option is not
      enabled.
      8a448bd5
  2. Oct 18, 2022
  3. Sep 22, 2022
  4. Jul 07, 2022
    • vuori's avatar
      Support wakeup on SIGUSR2. (#120) · 7949d302
      vuori authored
      Useful for waking up the locker on system resume from suspend and
      similar events not visible to X.
      7949d302
    • Vincent Bernat's avatar
      Optionally sleep before mapping windows (#138) · 1f29bd88
      Vincent Bernat authored
      This enables children some time to initialize and prepare their
      content. They are started before the main loop, we sleep
      XSECURELOCK_SAVER_DELAY_MS, then map the windows. The saver window is
      mapped first, then the background window and the obscurer window. This
      order works fine for me and I don't get a black flash anymore, despite
      the saver being written in Python.
      
      On shutdown, the order is also a bit altered to reduce the flash due
      to the obscurer window in white.
      
      The multiplexer is left untouched as its parent window is not mapped.
      
      Fix #94
      1f29bd88
    • Joshua Trees's avatar
      592c8504
  5. Feb 22, 2022
  6. Aug 12, 2021
  7. Jun 28, 2021
  8. May 24, 2021
  9. Jul 21, 2020
    • Sarius's avatar
      Update README.md · 53efba4c
      Sarius authored
      added annotation to where to find date format
      53efba4c
  10. May 06, 2020
  11. Jan 15, 2020
  12. Jan 08, 2020
  13. Dec 06, 2019
  14. Sep 06, 2019
  15. Jul 30, 2019
  16. Jun 04, 2019
  17. Jun 03, 2019
    • Rudolf Polzer's avatar
    • Dor Kleiman's avatar
      Password prompt choices (#79) · 5862c27f
      Dor Kleiman authored
      * Implement disco mode
      
      * Add option to hide the password completely
      
      * Update README.md
      
      * Update README with new version of env variables (not yet implemented)
      
      * Fix const-correctness
      
      * Add XSECURELOCK_PASSWORD_PROMPT flag + 3 bonus prompts
      
      * Remove XSECURELOCK_PASSWORD_PROMPT from readme
      
      * Add "REMOVE IN v2" inside XSECURELOCK_PARANOID_PASSWORD setting name
      
      * Revert accidental PARANOID_PASSWORD_MIN_CHANGE change
      
      * Wrap _Static_assert in a macro
      
      * Replace emoji escape codes with actual values
      
      * Rename ShowFromArray function
      
      * Use ++ as prefix operator
      
      * Remove useless parentesis
      
      * Move flag variables inside main
      
      * Update README with samples for the different XSECURELOCK_PASSWORD_PROMPT values
      5862c27f
  18. May 29, 2019
    • Rudolf Polzer's avatar
      Move blanking from saver_blank to main.c. · d4a817ae
      Rudolf Polzer authored
      Behaves somewhat better if the value is low; still could not get a zero value
      to work, as X11 then still wakes up the screen on key-release events.
      
      Note that after this change, SIGUSR1 is only sent if
      XSECURELOCK_SAVER_RESET_ON_AUTH_CLOSE is enabled, and savers
      should ideally handle it by soft-resetting the saver (implemented in
      saver_xscreensaver only for now); not handling it will cause a hard-reset
      of the saver by restarting it from scratch.
      
      Fixes #75.
      d4a817ae
  19. May 18, 2019
  20. May 14, 2019
  21. Apr 13, 2019
  22. Apr 03, 2019
  23. Feb 22, 2019
    • Rudolf Polzer's avatar
      New signal: SIGUSR1. · baf87544
      Rudolf Polzer authored
      This signal is now sent from the main program to the saver to reset possible
      idle timers in the savers, without intending to restart the saver.
      
      This is part of the effort to make the auth child protocol more flexible and to
      properly run auth on top of the saver as a window.
      baf87544
  24. Jan 10, 2019
  25. Jan 03, 2019
  26. Dec 21, 2018
  27. Dec 11, 2018
  28. Dec 04, 2018
    • divVerent's avatar
      Thou shalt have no other screen lockers · 0471192b
      divVerent authored
      Multiple screen lockers can interfere in various ways:
      
      - First of all, log spam: only the first locker is usually able to lock at all. Any others will usually fail getting the required input grabs.
      
      - Some lockers, e.g. light-locker, also have specific countermeasures against failing to lock and may interfere with xsecurelock. This has in the past caused issues such as having to unlock twice, having to unlock on a black screen because the graphics output broke, or losing all input focus after unlocking (yes, including alt-tab) and thus having a broken environment until clicking another window.
      
      - Also, potential race conditions during startup of both at the same time might cause deadlocks (e.g. if one grabs mouse first and one grabs keyboard first, while retrying indefinitely).
      
      - Even if they're not retrying indefinitely (xsecurelock isn't), this can slow down suspend to the point that systemd gives up and suspends before the screen is locked.
      0471192b
  29. Nov 30, 2018
  30. Nov 17, 2018
  31. Nov 14, 2018
  32. Oct 30, 2018