Don't upgrade to KDBX 4 when CustomData are present only in meta data section#1568
Conversation
53b2b9b to
f6662f7
Compare
|
I recommended this a while ago 😛 |
f6662f7 to
6a0e890
Compare
|
Update: there is another way more severe bug. When the file format is upgraded implicitly, we lose the challenge-response component of the key (see #1584). |
6a0e890 to
e8c7e2a
Compare
TheZ3ro
left a comment
There was a problem hiding this comment.
seems fine, good catch for the re-transformation
|
Well, that should have never happened. I'll work on some extra challenge-response tests. Our problem is that we cannot really test the real thing, so we need some mock CR key. |
|
I agree but it's not very simple to test |
- Fix unnecessary automatic upgrade to KDBX 4.0 and prevent challenge-response key being stripped [#1568] - Abort saving and show an error message when challenge-response fails [#1659] - Support inner stream protection on all string attributes [#1646] - Fix favicon downloads not finishing on some websites [#1657] - Fix freeze due to invalid STDIN data [#1628] - Correct issue with encrypted RSA SSH keys [#1587] - Fix crash on macOS due to QTBUG-54832 [#1607] - Show error message if ssh-agent communication fails [#1614] - Fix --pw-stdin and filename parameters being ignored [#1608] - Fix Auto-Type syntax check not allowing spaces and special characters [#1626] - Fix reference placeholders in combination with Auto-Type [#1649] - Fix qtbase translations not being loaded [#1611] - Fix startup crash on Windows due to missing SVG libraries [#1662] - Correct database tab order regression [#1610] - Fix GCC 8 compilation error [#1612] - Fix copying of advanced attributes on KDE [#1640] - Fix member initialization of CategoryListWidgetDelegate [#1613] - Fix inconsistent toolbar icon sizes and provide higher-quality icons [#1616] - Improve preview panel geometry [#1609]
Description
Fixed KeePassXC incorrectly (unnecessarily) upgrading to KDBX 4 if CustomData are available on the meta data section.
Resolves #1563 , #1565 and #1584.
Motivation and context
KDBX 4 upgrade should only be done for CustomData in entries or in the KDBX header, not in database meta data. Although an upgrade in itself is not a bad idea, it shouldn't be done automatically if it's not strictly needed.
I know I fixed this bug before and it must have been re-introduced somewhere along the way.
How has this been tested?
Manually and with updated upgrade tests.
Types of changes
Checklist:
-DWITH_ASAN=ON. [REQUIRED]