Feature to unlock only for staking about clams

[l0rdicon]

Apparently this is already part of the client, you just need to have an encrypted wallet to see it.

Closing.

[dooglus]

I didn't know about that, so checked.

I use the RPC interface, not the GUI.

Encrypting your wallet removes this from the list of available commands:

encryptwallet <passphrase>

and adds these:

walletlock
walletpassphrase <passphrase> <timeout> [stakingonly]
walletpassphrasechange <oldpassphrase> <newpassphrase>

and here's the doc:

$ cc help walletpassphrase
walletpassphrase <passphrase> <timeout> [stakingonly]
Stores the wallet decryption key in memory for <timeout> seconds.
if [stakingonly] is true sending functions are disabled.

[dooglus]

I also noticed that "sending functions are disabled" isn't all:

$ cc dumpprivkey x96EFZRESguy2s8yd3D5Pybj8oZfGy62hG
error: {"code":-13,"message":"Error: Please enter the wallet passphrase with walletpassphrase first."}

$ cc walletpassphrase "$x" 60 true

$ cc dumpprivkey x96EFZRESguy2s8yd3D5Pybj8oZfGy62hG
error: {"code":-13,"message":"Error: Wallet is unlocked for staking only."}

I can't dump a private key when unlocked for staking only, either.

[l0rdicon]

That would be the correct behaviour it seems.

Most of the functionality should remain locked. It doesn't really provide
true protection as your still entering the master password so all the
normal avenues of attack would still work there, aka key loggers etc.

What it does do is allows you to 'unlock' your wallet without worrying
about someone potentially using your physical computer and sending from
your wallet. Rpc has other ways to be secured but it wouldn't hurt to leave
your wallet unlocked for staking and full fully unlock when you need access
the other functionality.
On Jul 25, 2014 2:33 PM, "Chris Moore" [email protected] wrote:

I also noticed that "sending functions are disabled" isn't all:

$ cc dumpprivkey x96EFZRESguy2s8yd3D5Pybj8oZfGy62hG
error: {"code":-13,"message":"Error: Please enter the wallet passphrase with walletpassphrase first."}

$ cc walletpassphrase "$x" 60 true

$ cc dumpprivkey x96EFZRESguy2s8yd3D5Pybj8oZfGy62hG
error: {"code":-13,"message":"Error: Wallet is unlocked for staking only."}

I can't dump a private key when unlocked for staking only, either.

—
Reply to this email directly or view it on GitHub
#7 (comment).

[dooglus]

Right, I wasn't saying the behaviour was wrong, just that it is kind of different than the documentation.

if [stakingonly] is true sending functions are disabled

would be better stated as something like:

if [stakingonly] is true decrypted private keys are only available for staking

Note that even without a keylogger it would be quite easy to use a debugger to change the value of fWalletUnlockStakingOnly from true to false in a running instance of the wallet. But any protection is better than none.

[l0rdicon]

Rereading I get that now. Head was still grogy from waking up.

I actually was thinking the same thing, the return message could be more
descript.

It's a quick change, I'll get it merged in to staging once I get the
staging branch cleaned up today.
On Jul 25, 2014 6:33 PM, "Chris Moore" [email protected] wrote:

Right, I wasn't saying the behaviour was wrong, just that it is kind of
different than the documentation.

if [stakingonly] is true sending functions are disabled

would be better stated as something like:

if [stakingonly] is true decrypted private keys are only available for staking

Note that even without a keylogger it would be quite easy to use a
debugger to change the value of fWalletUnlockStakingOnly from true to false
in a running instance of the wallet. But any protection is better than none.

—
Reply to this email directly or view it on GitHub
#7 (comment).