AES-256-GCM Coinbase backup

[ob1]

known encryption type doesnt help if you dont know how coinbase generates the input for the encryption or compute the output of the decryption, there are so many more blackboxes like secret? iterations?

but to crack a password you need full knowledge of the processing pipline from input to output

you have unknown input > next unknown processing pipeline (password could be part of the input message like a salt, as well as part of the processing line, or the password itself generates the secret for the message for encrypting/decrypting, if so next blackbox how is the secret generated?
in terms of an equation

output = known_encryption( f1(unknown_data) + f2(unknown_secret) + f3(unknown_iterations) + .. + f4(known_password + ... + f*)

there are so many unknown parts

i mean when it would be so simple, why you dont decrypt your given test output with your known password and take a look at the output? (without using the app aka balckbox)

I agree, and there may be an initialization vector component as well. I was hoping that someone may have figured out a way to reverse engineer the process. To solve the problem, I would need to know all of the above and then I still have the problem of cracking the password.