I made a mistake in my question;
I wanted to ask: What is the editor that dooglus uses?
But That wallet drug that did not show me the 12 words, all the others show, except this wallet, I'll move on to mycelium which is better. But the Mycelium problem is just the PIN of only 6 numbers, I find it rather insecure a password with only 6 numbers. And what do you have to say about Mycelium and your PIN?
|
|
|
Which dooglus editor did you use?
|
|
|
I did not find my words in any line, I checked more than 5x There must have been some mistake, I do not understand, it was to appear my 12 words too ... I searched line by line
|
|
|
To make sure I made another backup with the same password as yours and I used the same command and it worked! Decrypted!
I was opening with the windows notepad and it was totally unreadable.
Instead I used notepad ++ on the desktop
But I could not find the words of the seed of the wallet. In yours, the words of the seed are on line 2, and mine are not, I am now trying to find my words...
In which line do words usually stay??
|
|
|
Já tinha feito outro backup com a senha: 12345678 ( ou seja, sem chance de erros) e ele deu a mesma mensagem: senha errada
|
|
|
It almost worked: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 -pass ************************ > bitcoin-wallet-decrypted-backup I entered the correct password, it is correct, but the program accuses it is wrong, I did not even type the password, just copied it into the notepad and then typed my password into git-bash, and it did not take all My password, as my password has 24 characters, it only recognized only 10 characters as you can see below in the log: [1] 2736 bash: MwCtyRWU: command not found Invalid password argument "**********" Error getting password [1]+ Exit 1 openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017 -02-24 -pass ********** Can the program decrypt at most one file with a 10-character password? I'll make another backup with 10 characters and confirm this.
|
|
|
Quase que deu certo: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 -pass ************************ > bitcoin-wallet-decrypted-backup Eu digitei a senha certa, está correta mesmo, mas o programa acusa que está errado, eu nem digitei a senha, só copiei ela no notepad e em seguida digitei minha senha no git-bash, e ele não levou em consideração todos os caracteres da minha senha, como minha senha tem 24 caracteres, ele apenas reconheceu apenas 10 caracteres como pode ver em baixo no log: [1] 2736 bash: MwCtyRWU: command not found Invalid password argument "**********" Error getting password [1]+ Exit 1 openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017 -02-24 -pass ********** Será que o programa consegue descriptografar no máximo um arquivo com uma senha de 10 caracteres?? Vou fazer outro backup com 10 caracteres e confirmar isso.
|
|
|
Me desculpe, Onde devo colocar o ":" ?
|
|
|
No software de descriptografia ele pediu para eu selecionar a opção "AES 256 bit Symmetric-key Algorithm" então por isso não está dando certo, então o Git-bash pode descriptografar o backup mesmo? Muito bem, ele pediu para eu colocar o backup na mesma pasta do Git, então eu deixei lá e depois dei o comando. GiRiNo, qual comando você pode me indicar ? Vou dar uns exemplos: open enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 > bitcoin-wal let-decrypted-backup bash: open: command not found Como você diz que todos os comandos devem ser dados ANTES do simbolo de ">". então deve ficar: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 -pass: "Minha senha" > bitcoin-wallet-decrypted-backup ?? todos esses dois comandos não deu certo: unknown option: -pass Depois que eu teclei enter apareceu as opções de comando: options are -in <file> input file -out <file> output file -pass <arg> pass phrase source ...
|
|
|
Obviamente coloquei o nome do arquivo do backup da carteira certinho e também a data: "bitcoin-wallet-backup-2017...." na hora de dar o comando.
|
|
|
Estou seguindo as regras desse tópico: https://bitcointalk.org/index.php?topic=1822148.0Estava tentando descriptografar usando o Git-bash e seguindo os comandos: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-01-01 > bitcoin-wallet-decrypted-backup -pass:testpassword não deu certo, depois usei o software: VSEncryptor.exe onde eu selecionei o backup e em seguida cliquei em decrypt, depois coloquei a senha do backup e não deu certo também, deu erro. Difícil.
|
|
|
Use this software to decrypt the file from the wallet, I did everything as you requested, however when I click on Decrypt, I put my password and a message appears in red: Decryption failed (error: 80090005,581). Invalid data.
I've even followed your last gitbash tip up and Did not work either.
Is a lot of unsuccessful attempt, I do not know what is the problem of this dev of not leaving the keys with the users themselves. I'm almost using Mycelium, but Mycelium's problem is that I do not trust that PIN Of 6 numbers It seems easy to be broken by brute force
By the way in bitcoin wallet I had put a PIN before backing up, which part does that PIN enter?
You really are willing to help me thank you for now.
I'm a little grateful.
|
|
|
Não consigo decifrar, esse que é o problema. Além disso, e o PIN dá carteira onde entra? Não vai precisar dele ? BitcoinJ é uma ferramenta necessária???
|
|
|
Olá, prezados! A carteira que estou me referindo é essa: https://play.google.com/store/apps/details?id=de.schildbach.wallet&hl=pt-BRSegui todos os passos do post a seguir: https://bitcointalk.org/index.php?topic=1822148.0 Mas sem sucesso. Eu sei que vocês me recomendaria a transferir moedas para outra carteira em vez de ter o trabalho de exportar chaves privadas dessa carteira. Mas gostariam que me entendesse, não só eu, mas acho que se eu sou dono dos meus bitcoins, eu como dono tenho direito de ter acesso as chaves privadas, caso eu quiser importar no Electrum ou Bitcoin-qt por exemplo. Eu sei que será muito difícil essa carteira sair do ar, mas mesmo assim, porque ter um backup que só pode ser usado nessa carteira se eu posso ter posse das chaves privadas e usar a seed ou xprivkey dentro do backup criptografado na wallet que eu quiser. Obrigado, Senhores.
|
|
|
After I transferred the backup to a folder C: \ Git \ bin I gave the command: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 > bitcoin-wallet-decrypted-backup It returned me this error message: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 > bitcoin- wallet-decrypted-backup bitcoin-wallet-backup-2017-02-24: No such file or directory 3496:error:02001002:system library:fopen:No such file or directory:bss_file.c:40 2:fopen('bitcoin-wallet-backup-2017-02-24','rb') 3496:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:404: Yes, The name of the backup I have never changed since when I saved this backup and transferred to other devices. Yeah, you're right, there should be the option to export private keys without coding. Until recently, you could use the bitcoin wallet backup in the multibit classic, or the classic multibit transfer to the Andreas Schildbach's bitcon wallet.
|
|
|
Thanks for replying dear user When I type in software git bash: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 > bitcoin-wallet-decrypted-backup It returns: unknown option '-aes256-cbc' options are -in <file> input file -out <file> output file -pass <arg> pass phrase source -e encrypt -d decrypt -a/-base64 base64 encode/decode, depending on encryption flag -k passphrase is the next argument -kfile passphrase is the first line of the file argument -md the next argument is the md to use to create a key from a passphrase. One of md2, md5, sha or sha1 -S salt in hex is the next argument -K/-iv key/iv in hex is the next argument -[pP] print the iv/key (then exit if -P) -bufsize <n> buffer size -nopad disable standard block padding -engine e use engine e, possibly a hardware device. Cipher Types -aes-128-cbc -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-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 -idea -idea-cbc -idea-cfb -idea-ecb -idea-ofb -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 Then I type the backup password: -k ****************** It returns something like an error. Surely I did it wrong? Please if you can explain the right command, because I did according: DECRYPTING
You now have your backup file on your PC. Wallet backups are encrypted. Let's decrypt it using:
openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-testnet-2014-11-01 > bitcoin-wallet-decrypted-backup
It will ask you for a decryption password, which is your backup password. If it prints "bad password" you've got the wrong password, but if it doesn't print anything your password might still be wrong. We can only be sure by looking at the decrypted data.
|
|
|
Well, I saw in this topic many requests for help on how to decode the backup that contains the private keys of this wallet mobile, since the wallet only allows you to send and receive, but you can not sign addresses Well there should be this option: Export private keys without Encrypt this export file. For if the private keys are mine, I have the right to export the privkeys of this wallet, for I am the sole owner of them. I know you have a means of decoding the backup by following this manual: https://raw.githubusercontent.com/bitcoin-wallet/bitcoin-wallet/master/wallet/README.recoverBut you have to understand that not everybody understands programming, and this manual is difficult to follow, would not it be easier to have an option in the app: "Export private keys"? We users know that handling the private keys is dangerous and so. Is there no way I can backup if this backup is only for this wallet, and if I want to import the private keys into Bitcoin core or Electrum? To sign addresses for example ?? It seems that there was this option in older versions but why did they remove it? I really like this wallet because it seems to be the simplest and most practical. But I only have this criticism. Please leave the option to export the private keys if we need to import into other alternative clients. Thanks.
|
|
|
Eu pensei em me especializar em programação, aprender linguagens de programação só pra receber btc de frillas, quem sabe ainda esse ano... Meu sonho é que o BTC se torne de fato uma moeda em que a maioria da população esteja usando, não vejo a hora de todo mundo olhar pro potencial dessa tecnologia, não sei se será com o BTC, mas que o BTC foi pioneiro isso ninguém deve negar!
|
|
|
Crie uma carteira na Smart Wallet da coinBR, ela paga as taxas de envio além de ter um layout bem amigável, é uma das soluções no momento!
|
|
|
|