Skip to content
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

fix: load keystore even if --insecure flag is set #1276

Merged
merged 1 commit into from Aug 7, 2018

Conversation

nikonov1101
Copy link
Member

This commit fixes a problem when --insecure flag is used
with the CLI and some sub-command wants to load a key or
obtain a default eth address from the key store.

Therefore, now we'll load keystore prematurely for any command.
Now if insecure mode is activated, only TLS credentials creation
will be skipped for gRPC's client connection.

This commit fixes a problem when `--insecure` flag is used
with the CLI and some sub-command wants to load a key or
obtain a default eth address from the key store.

Therefore, now we'll load keystore prematurely for any command.
Now if insecure mode is activated, only TLS credentials creation
will be skipped for gRPC's client connection.
@nikonov1101 nikonov1101 added 💩 T: bug This PR/Issue fixes a bug S: CLI This PR/Issue changes CLI P: medium This PR/Issue has normal priority V: patch This PR/Issue requires patch version to be bumped labels Aug 7, 2018
@nikonov1101 nikonov1101 added this to the v0.4.8 milestone Aug 7, 2018
@3Hren 3Hren merged commit 0ab78d0 into master Aug 7, 2018
@3Hren 3Hren deleted the fix/node/insecure-keystore branch August 7, 2018 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: medium This PR/Issue has normal priority S: CLI This PR/Issue changes CLI 💩 T: bug This PR/Issue fixes a bug V: patch This PR/Issue requires patch version to be bumped
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants