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
I have noticed that there are two copies of the .skywire folder on the official images, and therefor two copies of keys.json, which includes the Public Key used by the node process. The ones in /usr/local/skywire/go/.skywire/node/keys.json are used when the node process is called by the script /etc/rebuild.sh (which is called by rc.local). But if a user logs in as root and starts the node process manually (perhaps for troubleshooting, or to enable logging), it uses the Public Key stored in /root/.skywire/node/keys.json.
This is a real problem for people who have already submitted a whitelist application with their public keys. If they start any processes manually or write their own scripts or use crontab (have not tested this to see which keys would be used), they risk starting starting their Nodes with a Public Key different than the one whitelisted and their uptime will not be measured.
The text was updated successfully, but these errors were encountered:
I have noticed that there are two copies of the .skywire folder on the official images, and therefor two copies of keys.json, which includes the Public Key used by the node process. The ones in /usr/local/skywire/go/.skywire/node/keys.json are used when the node process is called by the script /etc/rebuild.sh (which is called by rc.local). But if a user logs in as root and starts the node process manually (perhaps for troubleshooting, or to enable logging), it uses the Public Key stored in /root/.skywire/node/keys.json.
This is a real problem for people who have already submitted a whitelist application with their public keys. If they start any processes manually or write their own scripts or use crontab (have not tested this to see which keys would be used), they risk starting starting their Nodes with a Public Key different than the one whitelisted and their uptime will not be measured.
The text was updated successfully, but these errors were encountered: