tuns.sh update allowed-users keys while connection is active

[tionis]

The only way they seem to establish a connection is by specifying the allowed-key-fingerprints manually

[tionis]

My mistake, I made a mistake in understanding how the authentication works. It does work as expected, the only things to note are:

• It seems with ssh -R some-name:80:localhost:80 g.tuns.sh tcp-aliases-allowed-users=username tcp-alias=true the valid keys are fetched during connection establishment and do not change when the keys are changed in the configuration. This is a bit inconvenient