Project

General

Profile

Actions

Bug #10178

closed

crypt.inc: crypt_data() legacy mode using wrong message digest

Added by Jim Pingle almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Backup / Restore
Target version:
Start date:
01/10/2020
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.5.0
Affected Architecture:
All

Description

On 2.4.x with OpenSSL 1.0.x, the default message digest (md) value was "md5" (eew). On 2.5.0 with OpenSSL 1.1.1 we manually set sha256.

Between the hardcoded md value and the difference in OpenSSL defaults between the versions, it needs a nudge before it could possibly decrypt an old config on a new system ("legacy" mode in the function). Old syntax examples like on the forum would not work as-is on 2.5.0.

So when $legacy is true, the OpenSSL command should pass -md md5 which should let it work fully.

Actions #1

Updated by Jim Pingle almost 2 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #2

Updated by Viktor Gurov almost 2 years ago

  • Status changed from Feedback to Resolved

tested on 2.5.0.a.20200110.1822 with 2.4.4-p3 and 2.5 encrypted backups

Actions

Also available in: Atom PDF