I'm running VBox 1.6.4 on Ubuntu desktop 8.04.1 AMD64 updated @ Aug 13 2008.
I've enabled auth logging with export VRDP_AUTH_DEBUG_FILENAME=/home/vbox/log, as suggested in another thread in this forum.
I started VM with VBoxHeadless -s dev & and in log I obtained:
u[vbox], d[dev2.lan], p[4]
vrdpauth_pam_init: dlopen libpam.so failed
vrdpauth_pam_init failed 4
Good, I made ln -s /lib/libpam.so.0 /lib/libpam.so, as suggested in same thread, and it worked
u[vbox], d[dev2.lan], p[4]
init ok
Using PAM service: vrdpauth
start ok
conv: num 1 u[vbox] p[4]
conv: 0 returning password [4]
auth ok
access granted
vrdpauth_pam_close completed
After this I tried unhautorized userid/pwd, and I got segmentation faults [1]+ Segmentation fault VBoxHeadless -s dev in all casese below:
u[leo], d[], p[0]
init ok
Using PAM service: vrdpauth
start ok
conv: num 1 u[leo] p[0]
conv: 0 returning password [0]
u[leo], d[], p[6]
init ok
Using PAM service: vrdpauth
start ok
conv: num 1 u[leo] p[6]
conv: 0 returning password [6]
u[vbox], d[], p[0]
init ok
Using PAM service: vrdpauth
start ok
conv: num 1 u[vbox] p[0]
conv: 0 returning password [0]
In other words , if user is allowed, all is ok, but if user si NOT allowed the VM crashes with segmenattion fault.
Am I making smtg wrong or is it a Virtualbox bug?