jsre: leave out lines from history possibly containing passwords#1562
jsre: leave out lines from history possibly containing passwords#1562obscuren merged 1 commit intoethereum:developfrom
Conversation
|
This PR is adequate 👍 |
|
👎 something like: |
|
@bas-vk this is a hot fix, a quick and dirty solution for a silly problem. It's not supposed to be a all catching, ever lasting solution :-) |
|
I absolutely agree on that, the real solution would be not to pass any sensitive information through arguments. But a little bit of normalization of the input can catch basic typo's. |
|
@bas-vk is right, i will add optional whitespace typos like will still give it away, but these are really the user's fault, cannot to anything |
|
👍 |
jsre: leave out lines from history possibly containing passwords
…0-beta Fix localEndBlock nil check
Currently the js console keeps a history. If you use methods of the
personalmodule, and give your password as an argument, it ends up in the history file in cleartext.The situation is worse, since the js console currently does not even allow interactive password input, so supplying it as argument is the only option.
Ideally blanking out password arguments should result in history entries like: personal.newAccount(XXXXX), however finding the right argument is very hard, a line could look like this:
potentially several calls within complex expression.
Due to lack of a better solution, I blank the entire line if it contains a personal command just to be on the safe side.