[qca] [Bug 432519] CryptographicMessageSyntax test fails with 2.3.2

2021-02-14 Thread Heiko Becker
https://bugs.kde.org/show_bug.cgi?id=432519 Heiko Becker changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|---

[qca] [Bug 432519] CryptographicMessageSyntax test fails with 2.3.2

2021-02-05 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=432519 --- Comment #5 from Albert Astals Cid --- good find, so they made that verifying an empty message always succeeds now, will update the tests. -- You are receiving this mail because: You are watching all bug changes.

[qca] [Bug 432519] CryptographicMessageSyntax test fails with 2.3.2

2021-02-05 Thread Heiko Becker
https://bugs.kde.org/show_bug.cgi?id=432519 --- Comment #4 from Heiko Becker --- I investigated a bit. Turns out the behaviour change is between 1.1.1h and 1.1.1i, bisecting led me to https://github.com/openssl/openssl/commit/6f1bee08cf80b9473496991b51f1f4a0decd96de While the title sounds like i

[qca] [Bug 432519] CryptographicMessageSyntax test fails with 2.3.2

2021-02-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=432519 --- Comment #3 from Albert Astals Cid --- Right, so there's some behaviour change down the line that broke this :/ I'll investigate soon, but honestly not a good reason not to package 2.3.2, since 2.3.1 fails in the your system anyway :D -- You are r

[qca] [Bug 432519] CryptographicMessageSyntax test fails with 2.3.2

2021-02-04 Thread Heiko Becker
https://bugs.kde.org/show_bug.cgi?id=432519 --- Comment #2 from Heiko Becker --- (In reply to Albert Astals Cid from comment #1) > CI says it passes https://invent.kde.org/libraries/qca/-/jobs/90348 > > can you re-confirm that 2.3.1 works for you? maybe it's an updated > dependency that makes th

[qca] [Bug 432519] CryptographicMessageSyntax test fails with 2.3.2

2021-02-04 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=432519 --- Comment #1 from Albert Astals Cid --- CI says it passes https://invent.kde.org/libraries/qca/-/jobs/90348 can you re-confirm that 2.3.1 works for you? maybe it's an updated dependency that makes the result of this change? -- You are receiving thi