pfSense XML config file, can we decrypt it manually?

SeaMonkey

@kevinrice Heh... oh.

KevinRice

@seamonkey Appears to be a waste of time, regardless if this is pfSense or not.

stephenw10

@kevinrice said in pfSense XML config file, can we decrypt it manually?:

Login screen sure looks familiar.

Bootstrap is omnipresent at this point!

Yeah I would be amazed if that's pfSense. It's almost certainly an ARM device to start with.

That config is not close to anything we have.

Steve

KevinRice

@stephenw10 said in pfSense XML config file, can we decrypt it manually?:

That config is not close to anything we have.

Steve

I agree. I think it was a cached favicon that led me astray.

Draco

@seamonkey I found your note when I was looking for a way to decrypt newer pfSense backups that had been encrypted. Your OpenSSL command is almost correct, at least based on my testing on Windows with OpenSSL 1.1.1. What you are missing is the -iter parameter.

As @vlurk noted earlier, the key is in the crypt.inc source code. You need -iter 50000. After I added that parameter, all my post 2.5.0 CE backup files are decrypting on Windows with OpenSLL. If you add "-a" to the command line as well, then you can skip the grep and base64 calls. The command line I use in a CMD file is:

openssl enc -d -aes-256-cbc -salt -md sha256 -pbkdf2 -salt -iter 500000 -a -in %1 -out %2

Where %1 is the input file and %2 is the output file; fewer calls so should be quicker too. I hope this saves someone else the pain I went through to figure this out. While it's possible that Unix/Linux and Windows OpenSSL behave differently w.r.t. the passphrase, I would be surprised if they are that much different. I am curious though, how what you posted could decrypt the file without the -iter argument... maybe an OpenSSL CNF file difference?

I've submitted a ticket to Netgate asking if they should update their documentation on manual backup decryption as well.

stephenw10

Where did you submit that? As a redmine bug report?

Draco

@stephenw10 No it was a TAC ticket. The support staff sent me email and suggested that I submit a feature request on Redmine. You can find all of the details on ticket # 1105865744. Everything I found, including links back to the source, a prior Redmine bug that lead to the changes to the manual, etc.

I had hoped your support team would pass along my findings. Perhaps you can do so?

Otherwise I'll get to submitting the same info via Redmine when I've dug out from under all the other items on my plate.

Cheers...

draco

rcoleman-netgate

@draco We highly recommend that you be the one that makes the redmine as you have the direct experience and knowledge and will be able to answer all the questions from engineers that review them.

Draco

Ok, I created a [Regression bug in Redmine](Redmine backup/restore document regression created: https://redmine.pfsense.org/issues/13494).

stephenw10

Thanks!

I changed it to a pfSense Docs ticket since it's specifically a documentation change.