Closed lucca65 closed 6 years ago
Please use cleos to communicate with keosd.
I need to communicate via http because i’m building a server that signs transactions. that’s why i’m using curl instead of cleos
So turns out that cleos
requires you to use 0.0.0.0
instead of localhost
if you want keos to be able to respond to internet http calls not just local network calls. This info is nowhere to be found.
I do understand the security implications to this, as keos is designed as a isolated server to just handle your keys, and I completely agree with this behaviour. Nonetheless this options should be documented.
In my particular case my Dapp have a server that acts as a "admin" and signs some transactions. We use docker, so I need to access keos through the http option, not cleos.
I can fix this by myself through a Pull request but I'm not familiar with your policies regarding to that.
Please let me know, I've spent a lot of time in this simple issue and I think others might as well as EOS grows.
This was documented in Issue #5114. No more explicit documentation will be provided. Off-host keosd exposure is so dangerous that the ability to do it at all needs to be obscured, as well as denigrated. Very very few people should ever do it. Even though keosd no longer exposes private keys without a password, if a wallet is unlocked it will still sign transactions, including transfer transactions, without prompting.
I'm using the following
docker-compose.yml
:All commands to
nodeos
work just fine. callingkeos
from inside thenodeos
container also works.curl for nodeos works as intended:
but calls for keos fail:
No logs can be seem on Docker console when the requests are made from the host machine. Tried to open another port on the
docker-compose
file and run a simple web server and it works with no problems.Have been trying to figure this out for two days with no avail
Please help!