Release 0.4

• Security: Refuse to run if wayland session is detected. Running pyxtrlock in a wayland session is insecure.

Release 0.3

• Fixes a memleak where the inner xcb error object stored with an XCBError exception was not freed.
• cursor files are no longer pickles but json files which are sanity checked.
• when used with xss-lock we now support the lock inhibition mechanism invoked with the xss-lock -l option.

Release 0.2

This is a security release and a feature release.

A bug was fixed that could in some circumstances lead to only the keyboard or the mouse locked instead of both. Furthermore, several security fixes are included to mitigate memory exhaustion attacks and fix memory leaks.

A feature was added that allows for changing the lock icon to custom images.

Release 0.1

This is the first stable release and a security release. A vulnerability was fixed that could allow an attacker to crash pyxtrlock and thus unlock the screen without supplying the correct password.