🆕[add-on] HassOS SSH port 22222 Configurator

[adamoutler]

Do you need me to type it out in full? I can do it tomorrow at my computer, but not mobile.

Your device will be sda, sda1, and sda2 instead of mmcblk0, mmcblk0p1, and mmcblk0p2

[nickrout]

I think I can do it, but its almost bedtime, so I’ll do it at a later time.

[nappyjim (Jim)]

@adamoutler Plugged monitor into my HA blue and when I restart your add-on and check log, it says everything is good. But on the monitor, this pops up

/dev/sda1: Cant open blockdev
/dev/mmcblk0p1: Cant open blockdev

I will try the other things you asked

[nappyjim (Jim)]

@adamoutler so below for results of your requests.

[adamoutler]

can you do this command again?

Looks like you added a tilde “~” at the end of that line and caused it to fail.

so

mkdir /tmp/1
mount /dev/mmcblk0p1 /tmp/1
ls -alr /tmp/1

[adamoutler]

HassOS says this Addon gets a security rating of 6

I did some research to figure out how the security ratings are applied and was able to game the system

Add-On Security Calculation

Hi, I wanted to know how Add-On Security Rating worked. Documentation is sparse on the topic so here’s the current values All Add-ons start with a base security rating of 5. You can increase or decrease this number via methods listed below. add +2 to security rating ingress: true (overrides auth_api rating below) add +1 to security rating auth_api: true apparmor.txt present in addon add -1 to security rating apparmor: false (overrides apparmor.txt presence) privilege: contains one or …

[nappyjim (Jim)]

@adamoutler

[adamoutler]

Thanks! You should be supported with v0.3.

[nappyjim (Jim)]

when can we expect 0.3?

[adamoutler]

It’s available now.

You might need to use the reload button in the upper right of the store.

[nappyjim (Jim)]

No go for me still…

1. Uninstalled 0.2
2. Installed add-on again as 0.3
3. Used puttygen to generate public/private key combo
   
4. Copied generated public key into configuration. Saved private key to filed on my computer.
   
   
5. Restarted add-on. Below is my log
   
   
6. Restarted HA.
7. Pointed putty to the saved private key, tried to connect to HA on port 22222
   

[adamoutler]

Wait, that’s different. Please update once again. I fixed it so it won’t throw that error on your system anymore. But I think that may be irrelevant. I can see you’re connecting so that means we created the file properly. I think you may have had a copy-paste error, using the wrong key to connect, maybe you need to reboot again, or something. You are connecting, which is impossible before a key is added. So the configurator added a key for sure.

[nappyjim (Jim)]

I dont know what I can be doing wrong. If you can see an error in my process, let me know. Or else Im just gonna have to give up at this point and just chalk it up to the blue hardware not supporting SSH into port 22222

1. Open puttygen, generate new pair
2. Copy entire public key
   
3. Paste key into configurtion
   
   
4. Press save and it re-formats the key and asks me to restart add-on
   
   
5. Check my log
   
   
   
   6.Restart HA
6. In puttygen, save private key as test5.ppk
   
   
7. Open putty, set address homeassistant.local: 22222
8. Point Auth to test5.ppk
   
9. Set auto login to root
   
10. Press open
11. Tries to connect, error.
    

[adamoutler]

How are you restarting? There’s multiple levels.

1. Configuration screen restart (Server)
2. Restart core (supervisor)
3. Restart Supervisor(supervisor)
4. Reboot Host (supervisor)
5. Hard Power Off (Physical)

4 or 5 should work.

I don’t use putty, but can we try linux instead? You have an ssh-capable linux if you installed the ssh and terminal app. Try this in the ssh terminal.

1. ssh-keygen (press enter when asked, use defaults, only enter responses)
2. cat ~/.ssh/id_rsa.pub to get your key. It’s all one line and looks like this when copied properly.

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDWO0Vp1MqMbcCZeXJArsZlBX6wvXPQ1zokAdFj1flVPu3E44KVkQlTakuxDGFiWzBoRhjs7GxciKPobTrbScpCaebfAjDjYBPF925Cm/AlCorQtfMDmCEXTcUdtQ4BMzvjOmo2GXyQ+TR3ACNyBj8Nc6ZmTeHbcsUki26UB0tYmhYNuL5zt3H/sVKgOkUfkyiKwNiyWA8FeLMOxvtncf9D20sIlVxpFL8GYkuCy5w3S3uLjsG/Y57nbwcMzAY+qD2v7BOlLXLJCyYRvhmeZG6oOMMXACaanL0Ix8XLvuWA1Z439HBUW9hurC8+M6VTnaAUXmn0VrbiCg7wD5pTqur9RTI6wuyL6DE6eGJ/7znbJ+++9HBSdfhuXLLFfhikNgE+2DyBwSI/hXs/EcZHcvJ/Y2jvSe2/OiuI+BVXRC0TM+MG8WnQ2K6UDPJo1H70DgPnIUabP9GUDKL+4dZ5F1mUFMWzZA4q16wYqG079nP4goQCY+yRphuMTPOwo6jWNLc= root@a0d7b954-ssh

or like this in a terminal.

3. copy the key from step 2 into HassOS SSH port 22222 Configurator
4. restart the configurator
5. Use Reboot Host method to restart.
6. Upon restart, within the terminal app, type ssh 127.0.0.1 -p22222

If it worked, then you were able to add your SSH key using this app and we need to troubleshoot putty. If it didn’t work then we need to troubleshoot the app.

[nappyjim (Jim)]

Edit: Nvm, just copied the key to a folder I can access from samba.

Rebooting host now

[nappyjim (Jim)]

I think that worked, i tried it again because I didnt know what I should see.

[nappyjim (Jim)]

So i tried your app again, and this time it worked!!

So I did 2 things different

1. When i put the key into configuration, i surrounded it with quotes
2. I rebooted host in supervisor as opposed to restarting server in Configuration > Server Controls

[adamoutler]

That’s it. Now you’ve got to figure out the problem with Putty. If you’re using windows you can always install WSL, then use a Linux tool the same way. If you figure out the problem with Putty, let me know. I’m glad we are now supporting your platform!

[nappyjim (Jim)]

We replied at same time. See my above reply, I got it working with your add-on as well.

[adamoutler]

Hey, that’s great. I think I typed my response a little late! Good to hear!