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
{{ message }}
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
In the bot log an error is logged when processing a message (from kssh).
Encountered error while processing message from xxxx (messageID:80): ssh-keygen error: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for '/mnt/keybase-ca-key' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "/mnt/keybase-ca-key": bad permissions (exit status 255)
The directory /mnt doesn't contain the ca-key file, however. After some searching I found it in the ../bot-ssha/docker/example-keybaseca-volume directory. CA_KEY_LOCATION is not set.
On Ubuntu 16.04LTS
Docker: 19.03.5 build 633a0ea838
VERSION= 1.1.0
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the bot log an error is logged when processing a message (from kssh).
The directory
/mnt
doesn't contain the ca-key file, however. After some searching I found it in the../bot-ssha/docker/example-keybaseca-volume
directory.CA_KEY_LOCATION
is not set.On Ubuntu 16.04LTS
Docker: 19.03.5 build 633a0ea838
VERSION= 1.1.0
The text was updated successfully, but these errors were encountered: