-
Notifications
You must be signed in to change notification settings - Fork 75
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
soroban-cli: uses the same identity/account/key for everybody by default #1079
Comments
Ideas for how we could address this issue:
Anyone have other ideas? |
True, my thought was that it was useful for generating the same transactions for testing across CI and teams. But it's not that hard to generate a test account with the default seed. This was also when we thought people would use the sandbox. I vote the first option. Better to be explicit. |
For test predictability is still helpful so I think we'd still want to use some common key in tests. |
Yeah that was what I was saying.
Is equivalent to
Then you can use |
I don't think we've explicitly said here, but I believe we have agreed to remove the default identity. cc @mollykarcher if you remember otherwise. |
Yes, that's my understanding as well |
What version are you using?
What did you do?
Used the default identity:
$ soroban config identity address
What did you expect to see?
A non-shared address. Maybe randomly generated on first use.
What did you see instead?
An address and key that everybody who is using the soroban-cli will use by default.
Why is this a security bug?
It's surprising that any key is shared.
Tooling that provides any shared key runs the risk of causing someone to think they have a unique key when they don't. Somebody may use the key on mainnet thinking it is a key unique to themselves.
Why is this a general bug?
Developers who use the default identity will be contending for access to the network. The network will only allow one tx per account in each ledger.
The text was updated successfully, but these errors were encountered: