** Changed in: vlock (Ubuntu)
Importance: Undecided = Low
--
vlock = root cannot unlock
https://bugs.launchpad.net/bugs/76379
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vlock in ubuntu.
--
Ubuntu-server-bugs mailing list
** Changed in: vlock (Ubuntu)
Importance: Undecided = Low
--
vlock = root cannot unlock
https://bugs.launchpad.net/bugs/76379
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Just in case since the bug is still open. Add youself to the unix group
vlock and it works as expected using vlock 2.2.2.
--
vlock = root cannot unlock
https://bugs.launchpad.net/bugs/76379
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
vlock uses the vlock PAM service, defaulting to other as every PAM
application does. Just provide an /etc/pam.d/vlock that does allow root
to authenticate.
--
vlock = root cannot unlock
https://bugs.launchpad.net/bugs/76379
You received this bug notification because you are a member of Ubuntu
The problem is if your root account does not have a password (which is by
default on Ubuntu). If you do :
$ sudo -s
# vlock
On a standard Ubuntu installation you can not unlock vlock.
--
vlock = root cannot unlock
https://bugs.launchpad.net/bugs/76379
You received this bug notification because
Then you probably should put something like
# comment out the following line if you have a root password set
# and want to lock as root
authsufficient pam_rootok.so
@include common-auth
into /etc/pam.d/vlock. That way users will at least be unable to lock
themselves out of their
Confirming, but I do not see how we could deal with that.
** Changed in: vlock (Ubuntu)
Status: Unconfirmed = Confirmed
--
vlock = root cannot unlock
https://launchpad.net/bugs/76379
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
