feat: add support for OS specific keychains - #1703
Merged
Merged
Conversation
willemneal
marked this pull request as draft
November 12, 2024 21:42
elizabethengelman
force-pushed
the
feat/os_keychain
branch
from
November 20, 2024 22:08
87a3101 to
432ca74
Compare
5 tasks
5 tasks
elizabethengelman
force-pushed
the
feat/os_keychain
branch
from
December 2, 2024 17:09
8732084 to
a6756f1
Compare
- previously we were creating a new keyring entry for each interaction with the keyring - this change will allow us use a mock keyring entry for testing
willemneal
commented
Dec 19, 2024
willemneal
commented
Dec 19, 2024
Contributor
Author
|
@elizabethengelman I can't review my own PR and can't figure out how to transfer to you, but besides my two suggestions, I think this is amazing and am excited to roll this out. I do think this should go first and then ledger since this is more widely applicable! |
elizabethengelman
force-pushed
the
feat/os_keychain
branch
from
December 20, 2024 21:45
93fa181 to
24269ce
Compare
Co-authored-by: Willem Wyndham <[email protected]>
This simplifies the lookup of the address.
willemneal
commented
Jan 7, 2025
willemneal
commented
Jan 7, 2025
willemneal
commented
Jan 7, 2025
This will allow for exporting the phrase later
elizabethengelman
approved these changes
Jan 8, 2025
Contributor
|
@willemneal I'm planning to merge this in this afternoon - what do you think? I think that the e2e test should be fixed by stellar-deprecated/system-test#109 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #1481
I updated this branch to point at main instead of feat/add_stellar_ledger so we wouldn't have too many PRs stacked on each other.
This adds support for using secrets stored in OS specific key rings.
Update to system test: stellar-deprecated/system-test#109
key generate(no fund)keys generate(fund)keys fundkeys addresskeys show: should not display the secure store's secret and instead return an error:❌ error: Secure Store does not reveal secret keytx signkeys rmandkeys addwill be addressed in Feat/os keychain followup #1770cargo run keys generate --secure-store carol --network local --no-fundcargo run keys generate --secure-store dean --network local --fundcargo run keys fund carol --network localcargo run keys address carolcargo run keys show carolcargo run contract deploy --wasm target/wasm32-unknown-unknown/test-wasms/test_hello_world.wasm --build-only --network local --source carol | \ cargo run tx sign --network local --sign-with-key carolcargo run contract deploy --wasm target/test-wasms/hello_world.wasm --build-only --network testnet --source fred-testnet | \ cargo run tx simulate --network testnet --source fred-testnetthis command is not working on a local network or with the test-wasms, it does work on testnet with wasm generated from a new contract
cargo run contract deploy --wasm target/test-wasms/hello_world.wasm --build-only --network testnet --source fred-testnet | \ cargo run tx simulate --network testnet --source fred-testnet | \ cargo run tx sign --network testnet --sign-with-key fred-testnet | \ cargo run tx send --network testnetsame as above
cargo run keys generate --secure-store --network testnet --no-fund alicecargo run keys generate --secure-store --network testnet --fund bobcargo run keys fund --network testnet alicecargo run keys address alicecargo run keys show alicecargo run contract deploy --wasm target/wasm32-unknown-unknown/test-wasms/test_hello_world.wasm --build-only --network testnet --source alice | \ cargo run tx sign --network local --sign-with-key alicecargo run contract deploy --wasm target/wasm32-unknown-unknown/test-wasms/test_hello_world.wasm --build-only --network testnet --source alice | \ cargo run tx simulate --network testnet --source alicecargo run keys generate --secure-store --network testnet --no-fund alicecargo run keys generate --secure-store --network testnet --fund bobcargo run keys fund --network testnet alicecargo run keys address alicecargo run keys show alicecargo run contract deploy --wasm target/wasm32-unknown-unknown/test-wasms/test_hello_world.wasm --build-only --network testnet --source alice | \ cargo run tx sign --network local --sign-with-key alicecargo run contract deploy --wasm target/wasm32-unknown-unknown/test-wasms/test_hello_world.wasm --build-only --network testnet --source alice | \ cargo run tx simulate --network testnet --source alice