This article walks you through configuring the SSH Server on Vera so you can connect to it without being forced to enter a password.
This is a very handy feature for development, and testing purposes.
Note: It is very important to follow the directions closely. If you improperly configure the SSH Service, you may not be able to login, and will need to recover it.
Be sure you test before logging out! If there is a problem, its easy to reset the device back to factory. Regular disclaimer, This isn’t a supported configuration change,
and I’m not responsible if you blow up the world.
If you have questions – please ask before starting.

First step, Create Trusted Keys

This section applies to those who don’t have an existing keypair. SSH uses a public private key exchange to identify that you are who you claim to be.
Once complete, you can connect and login to the device with a simple command. Another nice feature is moving files around and executing commands all remotely.
Don’t try this on Vera, It doesn’t ship with all the tools needed. The problem is the missing command ‘ssh-gen’. No matter, You will need to generate it on another system.
If you use a Mac, you have the tools. For those using windows – Putty has a version.
The Putty download page

Generate a key on your local host, you will create a public and private key.
The public key on my box is ~/.ssh/id_rsa.pub
Here is an excellent article on GitHub on generating these keys.

Configure Vera to trust your local system

you can either scp or copy the key starting with ‘ssh-rsa’ all the way to the end.
add this to the file /etc/dropbear/authorized_keys (You will likely have to create it)

Secure the Authorized Host file – chmod 600 /etc/dropbear/authorized_keys

Configure the SSH Service to not prompting for a password

Finally the last step is to edit Vera’s ssh config file (/etc/config/dropbear).

Your config should look something like this –


config dropbear
option PasswordAuth 'on'
option RootPasswordAuth 'on'
option Port '22'
#option BannerFile '/etc/banner'

 

Change the setting ‘PasswordAuth’ to ‘off’
When done your file should close to this

config dropbear
option PasswordAuth 'off'
option RootPasswordAuth 'on'
option Port '22'
#option BannerFile '/etc/banner'

 

restart the ssh daemon, /etc/init.d/dropbear restart

But – don’t logout yet! from another terminal attempt to login. This way if there is a problem you can diagnose it without being locked out.

Important note, don’t lose the private key. Back it up somewhere…
The private key should be named id_rsa. Copy it somewhere… losing it will mean you can’t login.