The entire purpose of this snap is to monitor the Bluetooth connection
status of a paired device (typically the user’s smartphone) in order to
automatically lock and unlock the screen based on proximity.
Without bluez, the snap cannot detect any Bluetooth devices and is
completely non-functional.
Interface 2: login-session-control
The snap locks and unlocks the user’s session by calling
org.freedesktop.login1.Session.Lock and Session.Unlock on the
system D-Bus.
Without login-session-control, the snap can detect the device but
cannot perform the lock/unlock action, which is its primary function.
Both interfaces are essential for the core functionality of the snap.
The snap has no other purpose than proximity-based screen locking,
so the use of both interfaces is directly tied to what the user
installs the snap for.
Hi everyone,
i hadn’t noticed the package hadn’t been uploaded, but now it’s uploaded with public visibility.
Compare the notice that manual verification is required.
This is also a +1 (#voteFor) from me for granting auto-connect of the bluez and login-session-control interfaces for the mate-smart-lock snap. Agreed that these are both necessary to provide core functionality, and would both be reasonably expected by a user. Thanks!
Hello @Nabhay. @yomonokio above and I are part of the security snap reviewers team at Canonical, welcome to the forum!
We are here to review requests like this, and then grant the relevant permissions in the snap store. We appreciate your thoughts and enthusiasm, but unfortunately any comments or ‘votes’ made by non-reviewers will not be considered when granting requests. We apologize for any confusion, I know there is no reliable way of telling us apart from regular users here on the forum! Thanks!
