Kevin Backhouse

@diizzyy: I don't understand what you want me to do. Please could you give me very precise instructions? Then I will consider it.

I still don't understand what problem this would solve. If somebody is particularly concerned about verifying the authenticity of the code, surely they should get it from the git repository...

> [@nehaljwani](https://github.com/nehaljwani) [@kevinbackhouse](https://github.com/kevinbackhouse) I guess all of this needs updating again after yesterday's 0.28.1 release? See also [#2821](https://github.com/Exiv2/exiv2/issues/2821) I've made an attempt at it here: https://github.com/Exiv2/team/pull/4 I see that the...

> could we also have the list of breaking change from 0.28.0? None as far I know. All the backwards-incompatible changes happened between 0.27 and 0.28.

@rouelle: it would be helpful if you could provide a stack trace which shows where the problem is in exiv2.

@gravypod: Have you tried submitting this change to [cmark](https://github.com/commonmark/cmark)? It's in a part of the code that's mostly the same in both codebases, so I think it would probably work....

Hi! I'm a member of GitHub Security Lab and can confirm that @rgmz reached out to us a few weeks ago for advice. We also attempted to contact the maintainers...

Are you able to reproduce this in GIMP with this image? https://gitlab.gnome.org/GNOME/gimp/-/issues/12626#note_2368064 I've run exiv2 on that file from a Linux command line and it looks very boring: I don't...

By the way, I don't think this is necessarily date-related. Is that hypothesis based on the mention of `ZNK5Exiv29Exifdatum8toStringEv` in the stack trace?

> > Are you able to reproduce this in GIMP with this image? > > No, but GitLab removes most metadata due to privacy concerns. I'm happy to take a...