-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement external signer for dataposter #1919
Merged
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
a619d43
Implement external signer for dataposter
anodar 62801eb
Merge branch 'master' into external-signer
anodar 4269470
merge master
anodar c3ed563
Drop accidentally added server binary for manual testing
anodar c177f02
Fix linter errors
anodar fa2f6fa
Merge branch 'master' into external-signer
anodar 2f7b867
Make signing method configurable to allow both eth_signTransaction an…
anodar cfb4bc7
Merge branch 'external-signer' of github.com:OffchainLabs/nitro into …
anodar c27cb4b
Update arbnode/dataposter/data_poster.go
anodar 73eb315
Merge branch 'master' into external-signer
anodar 4661888
Check that signed transaction is the one sent for signing
anodar 3816204
Merge branch 'external-signer' of github.com:OffchainLabs/nitro into …
anodar c551ff5
List transactions in correct order in the log line
anodar 412a7e0
Merge branch 'master' into external-signer
anodar 34fe2d0
Add default method for external signer
anodar 1e9b588
Merge branch 'external-signer' of github.com:OffchainLabs/nitro into …
anodar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to add a safety check that this is the same transaction we requested to be signed. I think there's potential security issues without that, where a remote signer MITM returns a different tx with a bad signature, and then convinces the data poster to request that different tx be signed against the real remote signer.
The ideal way to do this would be to get a geth
types.Signer
(really confusingly named, it's more of a signature verifier than a signer, it doesn't have a private key or anything), and use its Hash method which returns the pre-signature hash, to verify that aside from the signature the txs are the same. I think we can get a "signer" by callingtypes.LatestSignerForChainID
with the parent chain chain id from the config (we'll probably add that as a constructor argument to the data poster).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point! Added the check, although doing the lazy initialization, otherwise passing the signer (or chain ID) all the way from nitro.go would unnecessarily pollute call chain.