Bug #15178
closedACB (autoconfig backup) restore always returns could not decrypt despite proper password
0%
Description
ACB restore, using the proper password will permit viewing the encrypted and decrypted configuration, but either using the install this revision button on the xml view page or the action button on the restore tab always returns the error below, which cannot be accurate since the decrypted configuration can be viewed, subsequently copied and then used in a working configuration. It would seem copying the information into a new file and restoring or directly pasting it into the running configuration would be the only way to actually restore from an ACB backup entry.
Files
Updated by Kris Phillips 10 months ago
Tested on 24.03, I'm getting a different error:
The following input errors were detected:
SHA256 values do not match, cannot restore.
I have confirmed that the config file is properly decrypting because I can view both the encrypted and unencrypted config versions from the view button on the Restore tab.
Updated by aleksei prokofiev 10 months ago
Tested on
24.03-DEVELOPMENT (amd64)
built on Wed Jan 17 6:00:00 UTC 2024
FreeBSD 15.0-CURRENT
I am unable to reproduce.
Updated by Lev Prokofev 9 months ago
I am not able to replicate it on 24.04-DEV, but I have seen it on SC in ticket #2322652504 (23.09.1). After manual config restores the issue does not occur.
Updated by Kris Phillips 9 months ago
Re-tested this with a factory defaulted 24.03 box, manually configured ACB, and then re-tested. I can still produce, reliably, errors on attempting to restore config backups.
Updated by Christopher Cope 7 months ago
I am unable to reproduce on either
24.03-BETA (amd64) built on Fri Apr 5 16:53:00 UTC 2024 FreeBSD 15.0-CURRENT
or
23.09.1-RELEASE (amd64) built on Wed Dec 20 13:27:00 EST 2023 FreeBSD 14.0-CURRENT
However, a customer seems to have hit a similar issue. Is anyone else still able to reproduce this failure?
Updated by Danilo Zrenjanin 7 months ago
- Status changed from New to Confirmed
Yes, I was able to reproduce the described behavior.
Tested against the following versions:
23.09.1-RELEASE (amd64) built on Wed Dec 6 20:22:00 UTC 2023 FreeBSD 14.0-CURRENT
24.03-RC (amd64) built on Wed Apr 10 17:29:00 UTC 2024 FreeBSD 15.0-CURRENT
Updated by Danilo Zrenjanin 4 months ago
- Status changed from Confirmed to Feedback
I couldn't reproduce this issue on:
24.08-DEVELOPMENT (amd64) built on Thu Jul 18 6:00:00 UTC 2024 FreeBSD 15.0-CURRENT
I would appreciate another confirmation before marking this case resolved.