Topic: How to safely encrypt your Private Key!! (Read 224 times)
Public key cryptography is a system which is combined with pair of two keys as Public Key and Private Key. The strength of both public key and private key is depends on the degree of computational impracticality. As per the name Public Key is known to everyone who relates with it and Private Key is knows only to the owner of it. In Public key cryptography a person can encrypt message with receiver’s public key and it can only be decrypted with the private key of the receiver.
Why use this?
The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
why not just use (or implement) BIP38 encryption? The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
if someone used your program, he will be very dependent on your program
but by utilizing standard BIP38 encryption, this will help user acceptance and assurance on future support and help
I just want you know to help them out make an easy GUI and easy use of a software many of people don't even aware about encryption of their data and yet they are finding an easy solution I just wanna help them out with this to provide a user friendly thing
but yes accepted your suggestions
help me out so much thanks the problem I want to address that there are lot of people that are not that techy can't follow the techy things so mean that providing them a simple GUI to encrypt their data is a great idea right but yes I will look for BIP38 and make an easy GUI provided.
suggestions helps a lot 
When you need to protect the privacy of email messages, encryption and only accepting those who have private keys that match the public key are used to log in to emails as well as our data encryption on every existing smart device. Therefore many important personal data is in it. So always keep the encryption key in a safe place and also always use f2f.
Why use this?
The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
why not just use (or implement) BIP38 encryption? The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
if someone used your program, he will be very dependent on your program
but by utilizing standard BIP38 encryption, this will help user acceptance and assurance on future support and help
+1
An IF you REALLY do not want to use bip38 encryption, i'd rather just encrypt my private key using openssl (but my primary choice would be Thirdspace's suggestion: bip38 encryption):
Code:
echo "my private key" | openssl enc -aes-256-cbc -a
and to decrypt
Code:
echo "encrypted private key" | openssl enc -aes-256-cbc -a -d
you can even pick the cypher type you want to use... For example:
Code:
-aes-128-cbc -aes-128-cbc-hmac-sha1 -aes-128-cbc-hmac-sha256
-aes-128-ccm -aes-128-cfb -aes-128-cfb1
-aes-128-cfb8 -aes-128-ctr -aes-128-ecb
-aes-128-gcm -aes-128-ofb -aes-128-xts
-aes-192-cbc -aes-192-ccm -aes-192-cfb
-aes-192-cfb1 -aes-192-cfb8 -aes-192-ctr
-aes-192-ecb -aes-192-gcm -aes-192-ofb
-aes-256-cbc -aes-256-cbc-hmac-sha1 -aes-256-cbc-hmac-sha256
-aes-256-ccm -aes-256-cfb -aes-256-cfb1
-aes-256-cfb8 -aes-256-ctr -aes-256-ecb
-aes-256-gcm -aes-256-ofb -aes-256-xts
-aes128 -aes192 -aes256
-bf -bf-cbc -bf-cfb
-bf-ecb -bf-ofb -blowfish
-camellia-128-cbc -camellia-128-cfb -camellia-128-cfb1
-camellia-128-cfb8 -camellia-128-ecb -camellia-128-ofb
-camellia-192-cbc -camellia-192-cfb -camellia-192-cfb1
-camellia-192-cfb8 -camellia-192-ecb -camellia-192-ofb
-camellia-256-cbc -camellia-256-cfb -camellia-256-cfb1
-camellia-256-cfb8 -camellia-256-ecb -camellia-256-ofb
-camellia128 -camellia192 -camellia256
-cast -cast-cbc -cast5-cbc
-cast5-cfb -cast5-ecb -cast5-ofb
-des -des-cbc -des-cfb
-des-cfb1 -des-cfb8 -des-ecb
-des-ede -des-ede-cbc -des-ede-cfb
-des-ede-ofb -des-ede3 -des-ede3-cbc
-des-ede3-cfb -des-ede3-cfb1 -des-ede3-cfb8
-des-ede3-ofb -des-ofb -des3
-desx -desx-cbc -id-aes128-CCM
-id-aes128-GCM -id-aes128-wrap -id-aes192-CCM
-id-aes192-GCM -id-aes192-wrap -id-aes256-CCM
-id-aes256-GCM -id-aes256-wrap -id-smime-alg-CMS3DESwrap
-rc2 -rc2-40-cbc -rc2-64-cbc
-rc2-cbc -rc2-cfb -rc2-ecb
-rc2-ofb -rc4 -rc4-40
-rc4-hmac-md5 -seed -seed-cbc
-seed-cfb -seed-ecb -seed-ofb
-aes-128-ccm -aes-128-cfb -aes-128-cfb1
-aes-128-cfb8 -aes-128-ctr -aes-128-ecb
-aes-128-gcm -aes-128-ofb -aes-128-xts
-aes-192-cbc -aes-192-ccm -aes-192-cfb
-aes-192-cfb1 -aes-192-cfb8 -aes-192-ctr
-aes-192-ecb -aes-192-gcm -aes-192-ofb
-aes-256-cbc -aes-256-cbc-hmac-sha1 -aes-256-cbc-hmac-sha256
-aes-256-ccm -aes-256-cfb -aes-256-cfb1
-aes-256-cfb8 -aes-256-ctr -aes-256-ecb
-aes-256-gcm -aes-256-ofb -aes-256-xts
-aes128 -aes192 -aes256
-bf -bf-cbc -bf-cfb
-bf-ecb -bf-ofb -blowfish
-camellia-128-cbc -camellia-128-cfb -camellia-128-cfb1
-camellia-128-cfb8 -camellia-128-ecb -camellia-128-ofb
-camellia-192-cbc -camellia-192-cfb -camellia-192-cfb1
-camellia-192-cfb8 -camellia-192-ecb -camellia-192-ofb
-camellia-256-cbc -camellia-256-cfb -camellia-256-cfb1
-camellia-256-cfb8 -camellia-256-ecb -camellia-256-ofb
-camellia128 -camellia192 -camellia256
-cast -cast-cbc -cast5-cbc
-cast5-cfb -cast5-ecb -cast5-ofb
-des -des-cbc -des-cfb
-des-cfb1 -des-cfb8 -des-ecb
-des-ede -des-ede-cbc -des-ede-cfb
-des-ede-ofb -des-ede3 -des-ede3-cbc
-des-ede3-cfb -des-ede3-cfb1 -des-ede3-cfb8
-des-ede3-ofb -des-ofb -des3
-desx -desx-cbc -id-aes128-CCM
-id-aes128-GCM -id-aes128-wrap -id-aes192-CCM
-id-aes192-GCM -id-aes192-wrap -id-aes256-CCM
-id-aes256-GCM -id-aes256-wrap -id-smime-alg-CMS3DESwrap
-rc2 -rc2-40-cbc -rc2-64-cbc
-rc2-cbc -rc2-cfb -rc2-ecb
-rc2-ofb -rc4 -rc4-40
-rc4-hmac-md5 -seed -seed-cbc
-seed-cfb -seed-ecb -seed-ofb
Do I need to do this things? It is like letting some links scan all you profile in your computer, haha, as for me I just printed my password in a paper, keep copy on gmail, and put the Microsoft document with my private key with a password I will never forget, simple thing.
Such a great information.Its a great help for everyone who wants to secure their private key.Some people here might not yet aware on how to safely encrypt their private keep so the post you made is very useful.
Why use this?
The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
why not just use (or implement) BIP38 encryption? The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
if someone used your program, he will be very dependent on your program
but by utilizing standard BIP38 encryption, this will help user acceptance and assurance on future support and help
Thank you for this information that you gave sir specially to all beginners here in bitcointalk like me. All beginners must read this thread to get idea how to safely encrypt their private key. Thank you sir continue helping people that doesn't have knowledge.
thank you for passing by in this thread hope you can inform more of your friends and spread awareness to all of the people around the forum.This will help them alot
Well I can that you are willing to help the other people to be secured their private keys and I'm so glad because there's people like you, well that is great to give them an information on how to safely encrypt our private keys.
thanks for reading my thread hope that people will have idea how risky the cyber world is and I am doing my best to spread awareness to everyone and inform everyone this is the only thing I can do
HOW TO SECURE YOUR PRIVATE KEY BY ENCRYPTING IT!!
good day everyone here I am again SnowAngel as what I tell in my previous threads always suggest that you should back up your private key you must have a hard copy then yes that is great but most of us not saving the private key using a hard copy we will just save it in a text file in our computer and then leave it there then the risk of this is when an exploit got into your device then the attacker can dig in your computer files and analyse the files and get the important files so the risk there is that you just save your private key in a plain text state meaning it's a valid Private key so he can use it immediately without any hassle.
So in today's tutorial I will tell your how to encrypt your private key!! easily and safely
I am working with this encryption software for quite time so this are just a simple reminder
1. This tool is 100% free
2. this tool is offline to avoid hesitation
3. this tool can only encrypt 1 private key but I am working with multiple private keys.
4. this is a virus free software:
You can scan the file using Kaspersky online scanner: https://virusdesk.kaspersky.com
What is the programming language use in this program?
I use Python Programming since python supports lot of encryption method or algorithm.
Why should I trust you?
you don't have to trust me what I am doing is helping you to get more security as much as possible.
Why use this?
The problem is that when a hacker gets your text file containing your PK then he can use it but if you encrypt it then he will only see a jumbled and unreadable characters in the file and the only way to decrypt it is using a password and the key so are more way safe.
How to use the software?
1. download the file from : https://github.com/SnowAngelDevs/ArchAngel.git
2. Download and install Python 3.6 or higher here : https://www.python.org/downloads/
3. download as zip and extract
4. run the snowangel-encrypt.exe
USAGE
1.select a to encrypt
-run the exe file add your password and key.
-input your private key.
-then hit enter
-press any key to exit
2.select b to decrypt
-input your password and key
-copy the decrypted text
-press any key to exit
REMINDERS
1. Don't edit or delete the lib folder or else the encryption will not work.
2. Never forget your password and key.
Notes:
1. You can test the program
2. share your comments and suggestion to improve the sofware
that's all for today if you have question you can comment below
Jump to: