-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think it falls under the security vs. convenience category. Ideally,
everyone would use a different multi-word pass phrase for every account they
deal with. However, that's not very convenient. I like having the option to
allow sites to set up
On Tue, Jul 3, 2012 at 3:15 PM, Dmitri Chebotarov wrote:
> Hi
>
> Would LDAP authentication be better choice? In this case password policy
> already enforced by central LDAP server.
> Users would login to reservations using the same credentials as for VCL
> front-end (which uses LDAP auth)
> ...
Hi
There seems to be an issue with pGina and VCL.
One of the reservation steps for Windows image is to auto-login user 'root' on
1st boot to configure SSHD service.
Current version of pGina (3.0.12.1) doesn't support auto-login, so reservation
fails.
I've contacted pGina developers about auto-
Hi
Would LDAP authentication be better choice? In this case password policy
already enforced by central LDAP server.
Users would login to reservations using the same credentials as for VCL
front-end (which uses LDAP auth)
Linux already has built-in support for LDAP authentication.
pGina work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dmitri,
I like this idea as well. I think to do it right, there should be password
strength enforcing criteria in place to make sure users have strong passwords.
I also agree with others that it should be a configurable options. Can you go
ahead
I agree with Mark for the same reasons.
I would add, though, that there are ways to make "auto-connect" work.
We have a single-click, auto-connect system working in our VCL installation.
The basic principal is to define a protocol handler and format the URI so that
it is understandable to the t
In general, I would rather keep things as they are. But if that
capability is added, I would prefer to have it be an option as the
current one-time random password is much more secure. (Our experience
is that users generally pick poor passwords. Perhaps this can be a
development-only option?)
Mark
Hi
Would it be possible, and is it good idea in general due to possible security
risks, to add "Preferred Password" field on User Preferences page (under RDP
File Preferences or Personal Information?) to allow user to provide a password
for all his/her reservations?
Then VCL would use this p
