SATOSHI LEGACY RPCPASSWORD RECONSTRUCT

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

Quote from: Chilltime on September 27, 2022, 02:15:45 PM

any other finds? , the valid password ( is a 20 byte, 40 char hex string supplied in .upper()) also resolved using decodescript to an address.. but I think I am looking for a MD5 hash, almost as if it was a --Digest-Auth hash but Bitcoin stuck to Basic?..... the hunt continues...

I didn't perform additional research, since i doubt i'll find something useful within short time. But if you really want to dig that deep by yourself, i'd recommend to either
1. Use Ninjastic Space search feature[1] to find post with certain keyword or from certain time range.
2. Read old documentation[2] written by user @bitrick.
3. Open Bitcoin Core repository page[3] and explore source code on older version of Bitcoin Core/Bitcoin Qt.
4. Search relevant question on Bitcoin Stack Exchange[4]. There's tag "json-rpc"[5], but remember there's no guarantee everyone use that tag when ask question about Bitcoin Core/Bitcoin Qt RPC.

[1] https://ninjastic.space/search
[2] https://bitcointalksearch.org/topic/satoshi-client-operation-overview-41718
[3] https://github.com/bitcoin/bitcoin
[4] https://bitcoin.stackexchange.com/
[5] https://bitcoin.stackexchange.com/questions/tagged/json-rpc

Chilltime

newbie

Activity: 3

Merit: 0

NICE ONE! THX!

immediately I took a step forward again, just not there yet, defo valid password, double quotes no single !!! @json.txt !!! yes all in the detail, got it.... more testing and playing and learning to do...

I also get 'Warning: Couldn't read data from file "json.txt", this makes an empty POST.' as well but might have some ideas there..

any other finds? , the valid password ( is a 20 byte, 40 char hex string supplied in .upper()) also resolved using decodescript to an address.. but I think I am looking for a MD5 hash, almost as if it was a --Digest-Auth hash but Bitcoin stuck to Basic?..... the hunt continues...

Chilltime

newbie

Activity: 3

Merit: 0

Really appreciate your comments:

Oddly HTTP delivers the best success.

I get 401, 404, 405 errors and think my issues are about structuring the statement correctly, my HTTP scripting knowledge is poor at best, and information seems thinner than my hairline.

http://user:[email protected]:8332/ came afterwards, I have a password which appears to login with any rpcusername, as implied by Satoshi earliest rpc server but the URL returns malformed error for HTTP/GET? statements also had browser issues simply not wanting to play but think that is solved.

Any idea how an HTTP POST would have be structured in this period, examples may be a big help ... just your best guess?

thx

ABCbits

legendary

Activity: 2870

Merit: 7490

Crypto Swap Exchange

With such legacy client (older than Bitcoin-Qt 0.8), you can't even perform full blockchain sync. But answering your question, any HTTP application or library which support sending user-definited JSON data should work. cURL might work, but i doubt about HTTP/GET since cURL example on Bitcoin Core always use POST.

Chilltime

newbie

Activity: 3

Merit: 0

Satoshi wrote and explained the early RPC format:

https://bitcointalk.org/index.php?topic=461.0;1

Let assume I was to have a legacy rpc password and would like to log in again, is it possible?? HTTP/GET? , Bitcoin-cli?, cURL? can anyone educate me or redirect me to the documented process please?.

Thx

Topic: SATOSHI LEGACY RPCPASSWORD RECONSTRUCT (Read 183 times)