How to convert protobuf wallet format to private key

I did this step "enc -d -aes-256-cbc -a -in-bitcoin-wallet-backup> bitcoin_decrypted" in openssl and typed in the password that org.bitcoin.production gave me, so I think that my password works I can see 2 lines of foreign language with a few letters and numbers in between, so I assume it's the protobuf format.
Now as listed is the second step
Install bitcoinj:
Git clone
cd bitcoinj
Git Git –all
Git Checkout v0.14.4
MVN installation (fails on GroupTest in Windows Bash, but works anyway)
CD Tools

But my question is, where should I enter all these commands? in the same opensll page where I see the foreign language or elsewhere?

Why Protobuf is called a binary format, although we write it in text format similar to json

This is clearer when you compare two similar data items to non-text data components.

For example, the following JSON is ALL text:

"NumberOfClients": 20

The 20 consists of two separate characters, but would be represented in Protobuf as an actual binary integer, which in this case would be a single byte: 00010100

Also, I'm not sure if you understand Protobuf correctly when you compare apples and oranges in your question. They compare JSON dates to a protéguf scheme

Networking – Protobuf Vs. Flat buffer for games?

I've done some research on protopuffers and flat buffers, but I've seen conflicting and potentially outdated information.

Is it correct to say that the main tradeoff is that protobuffers have a smaller wire size, while flat buffers are more accessible?

So, if a project depends more on network performance than on local data read times, would protobuffers be the obvious choice? Or do I still miss other factors?

Protobuf: compile spec once, use generated code anywhere?

Once written, a protobuf specification can be created using Protoc to a variety of implementations in different languages ​​(eg Python, C ++, go). That's great. To compile the generated code, you need a protobuf development library, and if I am not mistaken, it will take some running time.

Is there a way to generate the implementation code in a pure linguistic, self-contained way? For example, I would compile and distribute my implementation in C ++ and Python, and users could use it simply by using the standard library.

If not, are there frameworks (similar in principle to Protobuf) that produce a serialization code in a specification that is self-contained and does not require other non-standard libraries for a particular language?

This question arises from the fact that lately I had to use protobuf on different systems and that there was a different development library available for each one. Should the specification be created separately on each system? What if the compilers have different versions?

Serialization – Can I add a new function for the struct generated by protobuf?

I use protobuf definitions to define message types.
Structure looks like

message1 {
Message2 {
Bytes msg1 = 1

So Message2 has a field that is a byte array representation of message1. I am:

  1. Create a msg1 structure instance
  2. serialization
  3. Encrypt byte array obtained in step 2
  4. Calculate the digital signature of the cipher generated in step 3

I want to see if it's possible to add a function for protobuf message1 that returns a serialized message1.