Encrypting / locking a wallet when not using a GUI / QT ?

fenghush

sr. member

Activity: 658

Merit: 250

Quote from: MoreBloodWine on January 10, 2015, 06:59:45 AM

Quote from: fenghush on January 10, 2015, 06:24:15 AM

Quote from: MoreBloodWine on January 10, 2015, 03:35:56 AM

Quote from: fenghush on January 09, 2015, 12:54:52 PM

You should run unset HISTFILE or equivalent command for resetting the history file of your shell so your wallet password wont be stored in plain text in your shell's history file before you encrypt/decrypt your wallet .

Good point, I noticed when I use the up arrow that it allows previous commands to be pulled.

So just: unest HISTFILE

?

If you're using bash unset HISTFILE will prevent bash from writing the command line history in .bash_history, to remove the 'up arrow' command history I believe the variable is HISTSIZE=0

Not sure what I'm using TBH but I def want to not "store" the unlock/lock password anywhere.

You can run echo $SHELL to figure that out. It's most likely bash.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: fenghush on January 10, 2015, 06:24:15 AM

Quote from: MoreBloodWine on January 10, 2015, 03:35:56 AM

Quote from: fenghush on January 09, 2015, 12:54:52 PM

You should run unset HISTFILE or equivalent command for resetting the history file of your shell so your wallet password wont be stored in plain text in your shell's history file before you encrypt/decrypt your wallet .

Good point, I noticed when I use the up arrow that it allows previous commands to be pulled.

So just: unest HISTFILE

?

If you're using bash unset HISTFILE will prevent bash from writing the command line history in .bash_history, to remove the 'up arrow' command history I believe the variable is HISTSIZE=0

Not sure what I'm using TBH but I def want to not "store" the unlock/lock password anywhere.

fenghush

sr. member

Activity: 658

Merit: 250

Quote from: MoreBloodWine on January 10, 2015, 03:35:56 AM

Quote from: fenghush on January 09, 2015, 12:54:52 PM

Quote from: MoreBloodWine on January 03, 2015, 06:40:55 PM

Quote from: activebiz on January 03, 2015, 05:45:43 PM

./bitcoind encryptwallet
Encrypts the wallet with .

./bitcoind walletpassphrase
Stores the wallet decryption key in
memory for seconds.

./bitcoind walletlock
Removes the wallet encryption key from
memory, locking the wallet. After calling
this method, you will need to call
walletpassphrase again before being able
to call any methods which require the
wallet to be unlocked.

Ty for this, I had a friend trying to help me figure it out but he couldn't seem to dig anything up.

You should run unset HISTFILE or equivalent command for resetting the history file of your shell so your wallet password wont be stored in plain text in your shell's history file before you encrypt/decrypt your wallet .

Good point, I noticed when I use the up arrow that it allows previous commands to be pulled.

So just: unest HISTFILE

?

If you're using bash unset HISTFILE will prevent bash from writing the command line history in .bash_history, to remove the 'up arrow' command history I believe the variable is HISTSIZE=0

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: fenghush on January 09, 2015, 12:54:52 PM

Quote from: MoreBloodWine on January 03, 2015, 06:40:55 PM

Quote from: activebiz on January 03, 2015, 05:45:43 PM

./bitcoind encryptwallet
Encrypts the wallet with .

./bitcoind walletpassphrase
Stores the wallet decryption key in
memory for seconds.

./bitcoind walletlock
Removes the wallet encryption key from
memory, locking the wallet. After calling
this method, you will need to call
walletpassphrase again before being able
to call any methods which require the
wallet to be unlocked.

Ty for this, I had a friend trying to help me figure it out but he couldn't seem to dig anything up.

You should run unset HISTFILE or equivalent command for resetting the history file of your shell so your wallet password wont be stored in plain text in your shell's history file before you encrypt/decrypt your wallet .

Good point, I noticed when I use the up arrow that it allows previous commands to be pulled.

So just: unest HISTFILE

?

fenghush

sr. member

Activity: 658

Merit: 250

Quote from: MoreBloodWine on January 03, 2015, 06:40:55 PM

Quote from: activebiz on January 03, 2015, 05:45:43 PM

./bitcoind encryptwallet
Encrypts the wallet with .

./bitcoind walletpassphrase
Stores the wallet decryption key in
memory for seconds.

./bitcoind walletlock
Removes the wallet encryption key from
memory, locking the wallet. After calling
this method, you will need to call
walletpassphrase again before being able
to call any methods which require the
wallet to be unlocked.

Ty for this, I had a friend trying to help me figure it out but he couldn't seem to dig anything up.

You should run unset HISTFILE or equivalent command for resetting the history file of your shell so your wallet password wont be stored in plain text in your shell's history file before you encrypt/decrypt your wallet .

activebiz

hero member

Activity: 518

Merit: 500

sure u can find more useful API commands here. https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: activebiz on January 03, 2015, 05:45:43 PM

./bitcoind encryptwallet
Encrypts the wallet with .

./bitcoind walletpassphrase
Stores the wallet decryption key in
memory for seconds.

./bitcoind walletlock
Removes the wallet encryption key from
memory, locking the wallet. After calling
this method, you will need to call
walletpassphrase again before being able
to call any methods which require the
wallet to be unlocked.

Ty for this, I had a friend trying to help me figure it out but he couldn't seem to dig anything up.

activebiz

hero member

Activity: 518

Merit: 500

./bitcoind encryptwallet
Encrypts the wallet with .

./bitcoind walletpassphrase
Stores the wallet decryption key in
memory for seconds.

./bitcoind walletlock
Removes the wallet encryption key from
memory, locking the wallet. After calling
this method, you will need to call
walletpassphrase again before being able
to call any methods which require the
wallet to be unlocked.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Ok, so when using Bitcoin-QT aka the fancy GUI. You can lock / encrypt the wallet that otherwise has all your addresses in it. Well, if one does not use the GUI aka Bitcoin-QT how does one go about locking / encrypting the wallet from the command line ?

Assuming it's doable from the command line, which I don't see why it wouldn't be since the GUI aka QT is just a fancy front end to the backend bitcoind as I understand it.

Ty.

Topic: Encrypting / locking a wallet when not using a GUI / QT ? (Read 1306 times)