7
votes
Accepted
does using a remote-signer or a ledger really improve security?
tezos-signer supports --require-authentication, --magic-bytes, and --check-high-watermark options. You should understand these.
$ tezos-signer man -v 3
...
-A --require-authentication: Require a ...
- 2,506
6
votes
How to check if remote-signer is working as expected?
I figured out that you can use the --dry-run option in the transfer statement so that node will send transaction to remote-signer to sign, and you can check the remote-signer logs to see if everything ...
- 1,115
4
votes
Accepted
How to check if remote-signer is working as expected?
I just prefer to do this...it's a direct request to sign data without any possibility of forgetting to add the --dry-run flag.
tezos-client sign bytes 0x03 for <tz alias or tz address>
Here ...
- 1,123
3
votes
Preferred remote signer protocol to use
I recommend using HTTP or HTTPS as it is a standard protocol so easier to handle, debug and test. Using a TCP socket means you have to understand that protocol and write specific tools for monitoring (...
- 443
3
votes
Remote signer crashes when asked to sign bytes
0x03 is for generic operations, like transfers. The ledger baking app cannot sign 0x03; it will only sign bytes beginning with 0x01, and 0x02 (blocks, endorsements). You need to exit the baking app ...
- 3,422
3
votes
Accepted
How can I test the Ledger signer without signing a block or endorsement?
edit: only tried locally, not remote.
I suggest you try signing dummy bytes. This will fail. But the way how it fails will tell you if your ledger is connected in the right way and if your signer ...
- 376
3
votes
How to run a baker with ledger (remote signer)
It's outlined in the tezos docs here: https://tezos.gitlab.io/mainnet/introduction/various.html#signer
One thing you need to think about is setting up a VPN or ssh tunnel or some secure connection ...
- 1,973
2
votes
Accepted
Why my endorser did not endorse the block 316956?
The error logs clearly suggest that the ENOTTY error for the "auth" key is your problem.
You cannot directly use an encrypted key to authenticate the docker daemons to a remote signer, because you ...
- 2,506
1
vote
Error while signing transaction from remote-signer after updating mainnet.sh script
I had the exact same error. My install is not the Docker-images but the classic install documented here: https://github.com/tezoscommunity/FAQ/blob/master/Compile_Mainnet.md
My issue turned out to be ...
- 961
1
vote
Error while signing transaction from remote-signer after updating mainnet.sh script
If you use tezos-signer remotely, and set the option to require authentication, then you probably updated the node to the latest mainnet but you did not update the remote signer code, be sure it is ...
- 223
1
vote
How can I test the Ledger signer without signing a block or endorsement?
I answered a similar question previously. My previous answer was not specific to a ledger, but it should work just fine all the same.
tezos-client sign bytes 0x03 for <tz alias or tz address>
...
- 1,123
1
vote
How to check if remote-signer is working as expected?
Another option would be to use Kiln. Kiln monitors your baker and will notify you if you miss any baking or endorsement opportunities (which will indicate that the signer is down).
It can be found ...
- 1,973
Only top scored, non community-wiki answers of a minimum length are eligible