Problems ssh to windows only from homebridge terminal

[reckedpr]

Backstory

I have followed steps from the wiki for the shutdown command and everything works apart from when I try run the command from the homebridge terminal it doesnt work but when I run it from normal terminal then it works fine

Issue

My homebridge folder thing is in the home folder not sure why, I cant create folders in the root drive so yeah. When I run it in homebridge terminal this shows up, I went and check the permissions tho and it says that everyone can read and write. why is it not working? Obviously if I type the password it works but it should be keyless ssh so I can just flip the switch on my iphone.

Load key "/home/homebridge/id_rsa": Permission denied

Environment

- os and os version: Linux mint xfce , LinuxMint Victoria (21.2) 
- node version: v18.18.2 not the latest but not sure if its relevent to this issue
- homebridge version:v1.7.0 latest
- homebridge-wol version: v4.54.1 latest

Configuration

No response

Logs

When I follow these steps:
1. Make sure `logLevel` is set to `Debug` on all `NetworkDevice` accessories
2. Run `homebridge`
3. Let it run for a couple of minutes
4. Try to turn a device on or off using the plugin
5. Wait one minute
6. Repeat step 4

I get the following log:

Please paste your log here

homebridge@dexter-9500-0446A:/var/lib/homebridge $ ssh -i /home/homebridge/id_rsa [email protected] shutdown /s

Load key "/home/homebridge/id_rsa": Permission denied

[email protected]'s password:

### Notes

_No response_

[AlexGustafsson]

When you say type your password, is that when you try to use the key? A key can be created either with encryption by specifying a password or without by not specifying a password. If a password is selected, it will have to be manually entered every time the key is used. I doubt, however, that you would get "Permission denied" in that case.

I think this has to do with file permissions. The user running the homebridge process doesn't seem to have the right to access the file. You'll have to identify what user homebridge is running as (should probably be documented somewhere). You can for example try to run ps on your docker host. You should be able to see homebridge listed there somewhere, along with a user id and pid. You can also check the file permission of the other files created by homebridge. The file permissions of the key must match those.