You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SSH connection to the running fabric all in one container cannot be established despite having access to the private key of which the public key is already placed in the authorized_keys file.
To Reproduce
Launch the fabric aio container and try to SSH in
Observe that your attempt is rejected by the open-ssh server despite presenting the correct private key.
This came up during the development of the Fabric contract deployment endpoint which depends on having a working SSH connection in order to fulfill its duties.
Fixeshyperledger#631
The root user account was locked (assuming by default)
so had to give it a password just so that we can log
in with it via SSH.
Since we don't actually plan on using the root password
I just set it to a UUID to make it a little less trivial
to recover it (which shouldn't matter anyway since we
strictly advise against using the AIO images in production
anyway).
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Fixeshyperledger#631
The root user account was locked (assuming by default)
so had to give it a password just so that we can log
in with it via SSH.
Since we don't actually plan on using the root password
I just set it to a UUID to make it a little less trivial
to recover it (which shouldn't matter anyway since we
strictly advise against using the AIO images in production
anyway).
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Fixes#631
The root user account was locked (assuming by default)
so had to give it a password just so that we can log
in with it via SSH.
Since we don't actually plan on using the root password
I just set it to a UUID to make it a little less trivial
to recover it (which shouldn't matter anyway since we
strictly advise against using the AIO images in production
anyway).
Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Describe the bug
The SSH connection to the running fabric all in one container cannot be established despite having access to the private key of which the public key is already placed in the
authorized_keys
file.To Reproduce
Expected behavior
SSH works.
Logs/Stack traces
N/A
Screenshots
N/A
Cloud provider or hardware configuration:
Dev machine
Operating system name, version, build:
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
ecd63b9
Hyperledger Cactus Plugins/Connectors Used
Fabric
Additional context
This came up during the development of the Fabric contract deployment endpoint which depends on having a working SSH connection in order to fulfill its duties.
cc: @takeutak @sfuji822 @hartm @jonathan-m-hamilton @AzaharaC @jordigiam @kikoncuo
The text was updated successfully, but these errors were encountered: