Timeline for Account is locked. How to unlock it using json-rpc?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2017 at 7:52 | comment | added | Yogesh Karodiya | @XavierLeprêtreB9lab please answer this ethereum.stackexchange.com/questions/29904/… question | |
| Nov 5, 2017 at 20:58 | comment | added | Xavier Leprêtre B9lab | @YogeshKarodiya A locked account here means a locked private key. | |
| Nov 4, 2017 at 13:45 | comment | added | Yogesh Karodiya | is there way for unlock account using private key not using password @XavierLeprêtreB9lab | |
| Sep 3, 2016 at 20:40 | comment | added | Xavier Leprêtre B9lab | I added it in the answer, but be careful, the password is travelling in the clear. | |
| Sep 3, 2016 at 20:39 | history | edited | Xavier Leprêtre B9lab | CC BY-SA 3.0 |
Added RPC call to unlock.
|
| Sep 3, 2016 at 16:53 | comment | added | Juan Ignacio Pérez Sacristán | Thanks a lot. Using command line call to geth as you described worked like a charm. Nevertheless, I wonder if this unlock action could be also possible through json-rpc protocol, avoinding admin intervention on command line. | |
| Sep 3, 2016 at 16:51 | vote | accept | Juan Ignacio Pérez Sacristán | ||
| Sep 2, 2016 at 22:05 | comment | added | Xavier Leprêtre B9lab | I agree 100%. I just asked if both Geth are on the same computer. | |
| Sep 2, 2016 at 21:51 | comment | added | o0ragman0o |
Given that exporting personal over rpc opens up a node to exploits shouldn't they be attaching through ipc instead, e.g. geth --testnet --exec "personal.unlockAccount(eth.accounts[0], \"password\", 3600)" attach ~/<datadir>/geth.ipc?
|
|
| Sep 2, 2016 at 10:48 | history | answered | Xavier Leprêtre B9lab | CC BY-SA 3.0 |