-
-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 6.2.2 clarification #560
Comments
I tried to take a quick look. Please check if I forgot more. I think the changelog/release note should actually look like:
Or something like that. Please check if I forgot more. And consider editing the notes on the release page accordingly. |
When building the new release I get:
The directory |
Could someone verify that the source tarball contains the right things? v6.2.1's tarball is 22MB, but 6.2.2 is only 429KB? |
6.2.4 got released and has a 21.8MB tarball again. I still would like to get a changelog and and information which CVEs got fixed in which version. |
Checkout 6.2.4, I've updated the notes and compared to 6.2.1. 6.2.2 has been deleted. |
Thanks the changes are much more informative now. |
Done! |
Great, thank you! |
I'm trying to figure out what changed in the freshly released 6.2.2.
The release note on GitHub states
ipv6 host ip address support and logfile CVE fixes
.The diff provided by et-v6.2.2...et-v6.2.1 is huge. A lot of external lib changes in it. Hard to see what actually was going on.
So I wonder, which CVEs got fixed? CVE-2022-48257, CVE-2022-48258, CVE-2023-23558? All of them? Only one?
I found #555 so that seems to be part of it.
Maybe you could help me with the rest? Maybe mentioning the CVE numbers in the respective issue (after they became public) so that it's easier to search and understand. Or maybe even having a changelog or mentioning the changes in more detail on the github release page.
For example:
Would be quite helpful. Then distributions and other interested people could easily understand what changed and also review the issues.
The text was updated successfully, but these errors were encountered: