Accessing Autobuilders

Connecting to Autobuilders

We use an ssh jumphost called access.yoctoproject.org/access.yocto.io to connect to the autobuilders. Jumphosts enhance security by removing the threat of hijacked ssh-agents and limiting the services running on Internet exposed hosts.

Generate keys

In order to access any of the autobuilders your ssh public keys must first be installed. The preferred key type is ECC. RSA with 4096 bits is also acceptable. Please put your e-mail, the date of generation, and the host the key lives on in the comment. Please set a passphrase even if it's a simple one! Ideally your private key will never leave the host it is generated on - so if you have multiple machines please generate multiple keys. E-mail your public key named ~/.ssh/id_ed25519.pub or id_rsa.pub to helpdesk@yoctoproject.org. Keep id_ed25519 or id_rsa(the private key) super safe. Please never share it with anyone or copy it onto the Internet. Don't e-mail it to yourself either.

 ssh-keygen -t ed25519 -C "your_email@example.com_2012-05-30_localhostname"

Substitute your own e-mail and your computer's hostname in the command above. Setting these helps with troubleshooting in the future.

Configure ssh

Edit ~/.ssh/config on your local machine and add:

Host access.yoctoproject.org access-vk.yoctoproject.org
   # Make sure your username matches your account on the autobuilder
   #User [username]
   # Give the full path to the proper public key if needed
   #IdentityFile /home/[username]/.ssh/id_rsa
   # If your network requires you to use a SOCKS proxy enable it here
   # ProxyCommand nc -X5 -x [proxyserver.address.company.com:1080] %h %p
   # If your system uses 'ncat', rather than 'netcat', use these options to enable a SOCKS proxy
   # ProxyCommand nc --proxy-type socks5 --proxy [proxyserver.address.company.com:1080] %h %p
     
# Typhoon workers are on a private network. Proxy through the bastion. 
Host *-ty-*.yocto.io *-arm-*.yocto.io
   ProxyJump access.yoctoproject.org
   # Correct username and key repeated from above.
   #User [username]
   #IdentityFile /home/[username]/.ssh/id_rsa
   # We don't need strict checking on the private network.
   StrictHostKeyChecking no
   VisualHostKey no
   # Don't bother saving hostkeys we don't check
   UserKnownHostsFile /dev/null

# Valkyrie proxy through a bastion to simplify key management.
# SSH host keys should be verified automatically via DNS
# If you don't have native IPv6 you must proxy through a dual-stack worker.
Host *-vk-*.yocto.io
   ProxyJump access-vk.yoctoproject.org
   StrictHostKeyChecking no

Verify Fingerprints

Now actually ssh to access.yoctoproject.org and verify that the fingerprint you receive matches a fingerprint below.

access.yocto.io
256 SHA256:d3eQ8azExpEKfcJExpUSpgw9D7gZgVDZ6gl4Bt5r6cQ (ED25519)
256 SHA256:jKW/rkm3+bNdtJ5CepVyHsxnbY8T78hk7lLwB0or0uA (ECDSA)
2048 SHA256:Qpvu4aUBox4eaYTeneRx5zMjwKTsZrJnn5VS9N5w+Fo (RSA)

access-vk.yoctoproject.org
ED25519 key fingerprint is SHA256:eDGzlYP3G+io9ylXmE6HMwtLMJ3eV82DveBnbM2mgJo.

Connect!

Now that you've added access.yoctoproject.org to your known hosts you don't need to worry about fingerprints anymore. Time to connect to a builder. Run:

 ssh centos8-ty-1.yocto.io

If all worked correctly you are now logged in. Build workers are listed on the controller. Append .yocto.io to the name to ssh.

Need to work on the build scripts?

If you are on the SWAT team you can access pokybuild using this sudo command:

 sudo -iu pokybuild

keywords: ssh access auto builder accessing autobuilders