Difference between revisions of "SSH Access - Almond+ 2014"

From SecuriWiki
Jump to: navigation, search
Line 19: Line 19:
 
uid=1001(pwilson) gid=1002(pwilson) groups=1002(pwilson),27(sudo),139(wireshark)
 
uid=1001(pwilson) gid=1002(pwilson) groups=1002(pwilson),27(sudo),139(wireshark)
 
pwilson@pwilsonlt:~$ ssh root@almondplus
 
pwilson@pwilsonlt:~$ ssh root@almondplus
 
 
  
 
BusyBox v1.17.3 (2014-03-11 18:45:01 IST) built-in shell (ash)
 
BusyBox v1.17.3 (2014-03-11 18:45:01 IST) built-in shell (ash)
Line 32: Line 30:
  
 
S E C U R I F I  Home Automation
 
S E C U R I F I  Home Automation
 +
 
root@AlmondPlus:~$ pwd
 
root@AlmondPlus:~$ pwd
 
/root
 
/root
Line 43: Line 42:
 
/home/pwilson
 
/home/pwilson
 
pwilson@pwilsonlt:~$
 
pwilson@pwilsonlt:~$
 
  
 
You'll note that it did not prompt for the "root" password.  This is because I took the time to add my Laptop's SSH Public key to the Routers Authorized Keys.  
 
You'll note that it did not prompt for the "root" password.  This is because I took the time to add my Laptop's SSH Public key to the Routers Authorized Keys.  

Revision as of 06:01, 21 March 2014

SSH access to Almond+

The Almond+ supports Dropbear as it's SSH client. By default it is only enabled on the LAN interface, but you can open to all interfaces, if you need remote access to it.

  1. Access the Almond+ WebUI (default: http://192.168.1.1/
  2. Select the Management tile:

Management Tile

  1. Enable SSH on the correct interface

SSH Access

   (Note I chose unspecified so it connects to all interfaces):
  1. Test Dropbear to ensure you can gain access..
   Here is code segment of my access from my Linux laptop.

pwilson@pwilsonlt:~$ pwilson@pwilsonlt:~$ pwilson@pwilsonlt:~$ pwd /home/pwilson pwilson@pwilsonlt:~$ id uid=1001(pwilson) gid=1002(pwilson) groups=1002(pwilson),27(sudo),139(wireshark) pwilson@pwilsonlt:~$ ssh root@almondplus

BusyBox v1.17.3 (2014-03-11 18:45:01 IST) built-in shell (ash) Enter 'help' for a list of built-in commands.

______   _      __  __   _____   __   _   ____       __ 

| __ | | | | \/ | | _ | | \ | | | _ \ __| |__ | |__| | | | | | | | | | | \| | | | \ \ | | | __ | | |__ | |\/| | | |_| | | |\ | | |_/ / |__ __| |_| |_| |____| |_| |_| |_____| |_| \__| |____/ |__|

S E C U R I F I Home Automation

root@AlmondPlus:~$ pwd /root root@AlmondPlus:~$ id uid=0(root) gid=0(root) root@AlmondPlus:~$ exit Connection to almondplus closed. pwilson@pwilsonlt:~$ id uid=1001(pwilson) gid=1002(pwilson) groups=1002(pwilson),27(sudo),139(wireshark) pwilson@pwilsonlt:~$ pwd /home/pwilson pwilson@pwilsonlt:~$

You'll note that it did not prompt for the "root" password. This is because I took the time to add my Laptop's SSH Public key to the Routers Authorized Keys.

Authorized Keys

Both OS X and Linux provide an "SSH" command, which can be accessed from "Terminal", "XTerm" etc. Microsoft isn't so kind, but Windows users can download PuTTY (a freely available SSH client for multiple platforms) and use that as the SSH client.

See also: http://forum.securifi.com/index.php/topic,886.msg1922/topicseen.html#msg1922