Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add instructions for root access #116

Closed
rwaldron opened this issue May 12, 2015 · 13 comments
Closed

Add instructions for root access #116

rwaldron opened this issue May 12, 2015 · 13 comments

Comments

@rwaldron
Copy link
Contributor

OSX:

brew install dterm;
dterm /dev/tty.usbmodem1412 
# or `dterm /dev/tty.usbmodem1422

Others?

@johnnyman727
Copy link
Contributor

It's probably worth noting that you can also SSH into the Tessel once it's connected to your network. The CLI uses SSH internally after you run t2 provision and it uses the key within ~/.tessel. That means you can also manually do ssh root@YOUR_IP -i ~/.tessel/id_rsa

Or you can manually copy your regular SSH key into /etc/dropbear/authorized_devices and then use ssh without the -i option. We have a t2 root command planned to copy it for you but it hasn't been implemented yet.

@rwaldron
Copy link
Contributor Author

$ ssh [email protected] -i ~/.tessel/id_rsa
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for '/Users/rwaldron/.tessel/id_rsa' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
bad permissions: ignore key: /Users/rwaldron/.tessel/id_rsa

@johnnyman727
Copy link
Contributor

This key issue will be fixed with #154.

@nodebotanist
Copy link

Heads up: if you don't include the baudrate, it can hang on macs:

dterm /dev/tty.usbmodem**** 115200

@johnnyman727
Copy link
Contributor

@nodebotanist I hadn't seen that happen before but it's good to know in case it doesn't work!

@Frijol
Copy link
Member

Frijol commented Jul 14, 2015

Where should this be documented?

@johnnyman727
Copy link
Contributor

IMO, it should be in the https://www.github.com/tessel/onboarding docs because only Team Members actually have hardware. Some folks who use the CLI use it with the VM so doesn't necessarily belong here.

@Frijol
Copy link
Member

Frijol commented Jul 14, 2015

Want to be more futureproof than "x are the only people who have hardware".

@johnnyman727
Copy link
Contributor

Yes, but it will soon be [semi] obselete when #80 is finished.

@Frijol
Copy link
Member

Frijol commented Jul 14, 2015

ah sure

@flaki
Copy link

flaki commented Aug 2, 2015

So I took a stab at this on Linux/Ubuntu x64. dterm is not included, and is not in the binary distros either which complicates things a bit so first one has to:

Compiling dterm from source

Fetch the source from knossos.net.nz, I used dterm-0.3.tgz. You would then go on to:

tar -xzvf dterm-0.3.tgz
cd dterm-0.3
make
sudo make install

For any build prequisites you should refer to the ubuntu community howto.

There is then one more pitfall I bumped into, on ubuntu the socket is referenced as ttyACM0, so you use:

dterm /dev/ttyACM0

It worked without a baudrate for me.

Once connected via dterm

Find /etc/dropbear/authorized_keys, and add your public key ~/.tessel/id_rsa.pub (t2 provision should have alredy created this for you):

nano /etc/dropbear/authorized_keys

SSH in!

Use your private key to jump in:

ssh root@<TESSEL_2_IP> -i ~/.tessel/id_rsa

If you need to find out your Tessel's network ip, use ifconfig from the dterm console.

@johnnyman727
Copy link
Contributor

Thanks for putting this together, @flaki! Hope the learning wasn't too painful :)

@johnnyman727
Copy link
Contributor

Closing because now we have t2 root.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants