If you read through the LO bug report, you'll see that there are many patches for this bug, affecting multiple modules.
Why? The historical files that are valid but have the wrong checksum due to having been written by the broken [OO.org-derivative] implementations when they were created, will still be accepted as valid by future versions of LO. I think they have quite an involved bug fix, with new UI dialogs for those cases, etc. On Sat, Jul 27, 2019 at 9:50 AM Peter Kovacs <pe...@apache.org> wrote: > Hi Brane, > > This is a very nice Idea. Maybe even beyond the immediate idea on fixing > the SHA implementation. > > Thanks a lot for this Idea. > > > All the Best > > Peter > > On 26.07.19 12:36, Branko Čibej wrote: > > On 25.07.2019 00:43, Peter Kovacs wrote: > >> Hello all, > >> > >> > >> I would like to ask if I or any other from OpenOffice Development team > >> can port the patch from LibreOffice to OpenOffice to fix this Issue > >> under the APL2 License, so the Issue can be fixed in OpenOffice without > >> more work then necessary. > > > > Would it be appropriate to use the hash code from APR > > (https://apr.apacha.org)? The license fits, and that code has been > > stable and well tested for ages. But I'm not sure if it fits your FIPS > > compliance requirements. > > > > -- Brane > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
