 Show Posts
|
|
Pages: [1]
|
I store my seed in txt flle as well, and this file is in my phone, and noone can read it (except me). It's very easy... I have packed the file in 7zip with a password, the password is more than 20 characters long.
Have you personally reviewed the code of 7zip to ensure there are no flaws in its encryption algorithms? Did you take steps to mitigate against known vulnerabilities such as this one: https://twitter.com/3lbios/status/1087848040583626753? Did you make sure to build the app yourself from the source code you reviewed to ensure you haven't downloaded a fake or malicious one? Did you make sure to delete all the temporary files it creates in the archiving process, and then write over those sections of your phone's memory with junk data? Did you make sure to delete the unencrypted text file you would have first loaded on to your phone before encrypting it, and then write over that section of your phone's memory with junk data? Do you never unencrypt it unless your phone is offline, and then again delete and over write the temporary files it creates? There is a reason that everyone tells you to write down your seed phrase on paper and keep it offline. I encrypted my file a few years ago on my linux debian computer, I do not use this comp now. I have only this encrypted file in my phone and in two usb sticks that are in a metal safe, and I have learnt my seed by heart. Everything else is paranoia... |
|
|
|
Unfortunately I stored my seed in .txt file, because I was fucking dumb, and that's probably my issue.
I store my seed in txt flle as well, and this file is in my phone, and noone can read it (except me). It's very easy... I have packed the file in 7zip with a password, the password is more than 20 characters long. |
|
|
|
it does have PGP signatures! but since ISO is big (Ubuntu 18.04 is nearly 2 GB) they use SHA hashes and then sign the hashes with their PGP private key and release the signature of that file instead.
so what you do is that you first check the signature of the hashes to see if you have the correct hash list file and then hash the file itself to see the file is correct.
in other words it is a combination of authenticity and integrity with 2 steps.
For this you need to know fingerprint of signature. For example, I exactly know fingerprint for electrum files, because I watched a video with this fingerprint and Thomas V standing beside. To be fair, why do you trust the video you've seen? There's probability the video is edited. The reality 100% trustless environment is impossible and you're forced to trust someone at some point. You are right! And you need to trust Thomas V! He is only a human and can change his mind...  |
|
|
|
|
Moreover, you cannot verify google chrome file with signature, you cannot verify avast antivirus exe file with signiture, and most of known apps haven't got any signatures to verify them! And if they do have got such signatures, you cannot trust them without checking reality of their fingerprints. But how can you do it? You need to be sure that fingerprints are real!
|
|
|
|
~
For example, ubuntu iso hasn't any signiture, only checksum...
it does have PGP signatures! but since ISO is big (Ubuntu 18.04 is nearly 2 GB) they use SHA hashes and then sign the hashes with their PGP private key and release the signature of that file instead. so what you do is that you first check the signature of the hashes to see if you have the correct hash list file and then hash the file itself to see the file is correct. in other words it is a combination of authenticity and integrity with 2 steps. For this you need to know fingerprint of signature. For example, I exactly know fingerprint for electrum files, because I watched a video with this fingerprint and Thomas V standing beside. |
|
|
|
No need to check the signature since I already downloaded from the original website. Electrum.org and I double verified before I downloaded. Also, I changed the name of the setup. thing is really weird because I am not connecting to this server at all. I get this msg even when I am into a different server.
What kind of verification that you did? Checking the site name twice? Remember that it is also possible that your DNS was hijacked, so you've download a malicious app. I'd rather verify it just to be safe. Excuse me... So even you cannot be sure in security! For example, before installing electrum you need to install a correct OS. How can you be sure your OS is real! Maybe you downloaded your OS ( for example, ubuntu) not from real ubuntu.com, but someone hijacked your DNS... that is why the concept of checking the authenticity of a downloaded file was invented. which means you download anything from the internet and then check its authenticity with a key that you trust. under the hood the (asymmetric) cryptography that is used gives an easy way of verifying that with virtually zero chance of fault. the most common case is usage of PGP signatures. which means when you download Ububtu for example you verify the ISO file signature against the public key using the cryptographic scheme that was used and if you get a "thumbs up" you can be sure it was the real OS. so now it doesn't matter where you download the file from, you don't even have to go to ubuntu.com, you can go to anywhereelseevenafakesite.com and download the ISO and as long as you verify its signature with the real public key and get the valid signature you will be good to go. For example, ubuntu iso hasn't any signiture, only checksum... |
|
|
|
No need to check the signature since I already downloaded from the original website. Electrum.org and I double verified before I downloaded. Also, I changed the name of the setup. thing is really weird because I am not connecting to this server at all. I get this msg even when I am into a different server.
What kind of verification that you did? Checking the site name twice? Remember that it is also possible that your DNS was hijacked, so you've download a malicious app. I'd rather verify it just to be safe. Excuse me... So even you cannot be sure in security! For example, before installing electrum you need to install a correct OS. How can you be sure your OS is real! Maybe you downloaded your OS ( for example, ubuntu) not from real ubuntu.com, but someone hijacked your DNS... |
|
|
|
|
Cannot use Memory-pool based fee estimation! I choose this option and close the settings window, after that I open the settings window again... and see ETA chosen instead of Memory-pool everytime! I cannot choose Memory-pool, Electrum doesn't remember my selection! My OS is Linux Debian 9.
|
|
|
|
Hi,
I am not planning to do anything with BCH. Can I just use my electrum wallet normally for now? If I send some BTC to my coinbase would that in any way mean I would lose my BCH linked to the same address as coinbase doesn't support BCH?
Basically, I want to make sure I can use my BTC normally using the same electrum wallet that I have been using, and my BCH would be still there if I ever decide to use BCH sometime in future.
I am asking this because in the case of Ethereum it was a convoluted process to separate ETH and ETC, as I sent some ETH to the exchange and the exchange received both ETH and ETC.
Please, read this guide http://upup.ml/22 |
|
|
|
no no need for sudo. start electrum from a terminal and repeat the process of whole wallet file encryption. electrum will post debugging messages in the terminal. upload those onto pastebin.com and share the link here so we can take a look.
The terminal shows only this "sni-qt/10318" WARN 14:12:21.422 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE
** (python:10318): WARNING **: Invalid borders specified for theme pixmap:
/usr/share/themes/Breeze/gtk-2.0/../assets/line-h.png,
borders don't fit within the image
** (python:10318): WARNING **: invalid source position for vertical gradient
** (python:10318): WARNING **: invalid source position for vertical gradient
** (python:10318): WARNING **: invalid source position for vertical gradient
** (python:10318): WARNING **: invalid source position for vertical gradient
After that Electrum stops responding! And I have to kill Electrum process! That's all! |
|
|
|
|
I use Linux Debian and Electrum 2.9. When I try to encrypt only seed and private keys everything is ok... but when I try to check Encrypt Wallet file, Electrum stops responding! When I start Electrum again, it starts without any password. And I have again only my seed and private keys encrypted. Maybe I should try to start Electrum using sudo to encrypt Wallet file?
|
|
|
|
Can anybody explain me which fork will my coins in electrum belong to, if bitcoin forks to bitcoin unlimited and old bitcoin? I think they will have different prices.... and I would like to use more precious coins  |
|
|
|
|
It doesn't matter to me what fork to use. I am not a supporter of any. I only don't want to lose my coins in this fork chaos. That's all. And if I understand well - all I need to do is to not worry, simply keep my coins in Electrum wallet and everything will be fine with them despite Bitcoin forking. Am I right?
|
|
|
|
|
What do you mean, saying: you could spend/sell them on both chains?
I think I will be able to do it without any doubts, otherwise it will mean that servers (that will decide to use Bitcoin Classic, for example) will not support my Electrum wallet and they will show me that I have 0 coins, and only servers (which use old Bitcoin, for example) will allow me to have and spend my money!
|
|
|
|
So If Bitcoin Classic comes to reality, Its cost may be not the same as Bitcoin's. And I will be able to choose which fork (server) to use, for example, for selling my coins with the best profit, won't I?  |
|
|
|
Thank you |
|
|
|
|
Which fork will my coins belong to (that are in my Electrum wallet), If Bitcoin classic get 75% support and Bitcoin is forked to Bitcoin and Bitcoin Classic? Will they become Bitcoin Classic coins or stay the same Bitcoin coins?
|
|
|
|
|
