• Content
  • Comments (3)
  • Related articles
Mar
13
2012

CentOS 6.2 – autologin and login keyring password for VNC sessions Tuesday, 13 March 2012

To establish an VNC session you need auto-login at system start. Auto-login in CentOS 6.2 GNOME can be done by adding only two lines on:
/etc/gdm/custom.conf

[daemon]
AutomaticLoginEnable=True
AutomaticLogin=username

 

By default Linux Cent OS 6.2 doesn’t come with Seahorse Manager – Passwords and Encryption Keys. To install it just:

  • go to System > Administration > Add/Remove Software
  • search for [seahorse]
  • select [A GNOME application for managing encryption keys] and install it with all dependencies

 

In order to connect to VNC session you need to ovoid [Unlock login keyring] dialog. Which is the master password that encrypts all local passwords. After fresh reboot, auto-login works perfectly only that is not unlocking the keyring even if the user, vnc and keyring passwords are the same. Despite all advices that i found where some people recommend that the login password to be same as keyring one, i’ve tested all possible combination but nothing happend and makes sense since the keyring container  that keeps all the local passwords is protected by a master password that encrypts all the passwords from container. Seem that the only way to establish a successful VNC connection even after system restart without local login is blank_password on Passwords and Encryption Keys > Passwords: login

 

3 Comments

  1. dron says:

    thanks for this help. there is a little simpler method

    1) add to /etc/gdm/custom.conf

    [daemon]
    AutomaticLoginEnable=True
    AutomaticLogin=username

    2) erase your gnome keyring for your user. for example

    rm /home/user/.gnome2/keyrings/login.keyring

    3) continue with picture #1, when you will try to enter vnc password you will be prompted to enter new keyring password – enter empty password and accept you are using “unsafe storage”. then enter your vnc password.

    4) do not forget to configure your firewall to accept connections on 5900/tcp. for example by adding

    -A INPUT -m state –state NEW -m tcp -p tcp –dport 5900 -j ACCEPT

    to /etc/sysconfig/iptables before last reject everything rule (-A INPUT -j REJECT –reject-with icmp-host-prohibited)

  2. Q says:

    Seem to me like the same method done slightly different. Anyway the point was that is the only way for now. I mean, once that all settings are done, in case of server reboot you can connect remote via VNC without been blocked by the keyring. I forgot about iptables but wasn’t the case since every VNC tutorial on the net covers that.

    Anyway thanks for input Dron, appreciated.

  3. albanyeye says:

    that was great! thanks a lot..

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*

Sorry but there are no similar articles at this time.