glib, gnutls and libgcrypt security updates #4010
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I don't know if there is interest in this; instead of loosing the work I thought I would share. Many packages dated quite a bit or where based on unstable releases (e.g. |
th0ma7
force-pushed
the
glib-misc-updates
branch
from
c7f44b5 to
af69364
Compare
th0ma7
force-pushed
the
glib-misc-updates
branch
from
af69364 to
a8120f6
Compare
This was referenced Oct 5, 2020
th0ma7
added a commit
to th0ma7/spksrc
that referenced
this pull request
Oct 7, 2020
th0ma7
changed the title
55 tasks
ymartin59
approved these changes
Oct 12, 2020
th0ma7
force-pushed
the
glib-misc-updates
branch
2 times, most recently
from
450cc47 to
9ab8499
Compare
th0ma7
added a commit
to th0ma7/spksrc
that referenced
this pull request
Oct 12, 2020
th0ma7
force-pushed
the
glib-misc-updates
branch
from
791dcbc to
d5ce51d
Compare
|
@ymartin59 Now ready for a merge. Feel free to have another look at it before I squash & merge but should now build with no more errors (leaving github-action running to confirm). |
ymartin59
approved these changes
Oct 13, 2020
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation: While investigating issue #4006 and trying to find the root cause I ended-up updating various dependencies. In the process I noticed multiple old versions of various key libraries that needed to be updated due to multiple CVE advisories. This PR is in direct relation to #4155 where newer version addresses security issues.
Linked issues: #4006, #4008, #3998, #4155
Checklist
all-supportedcompleted successfullyIMPORTANT NOTES
GLIB
https://www.cvedetails.com/vulnerability-list/vendor_id-283/product_id-16275/version_id-260024/Gnome-Glib-2.56.1.html
glibupdate from 2.55 to 2.58 (was using an old and unstable version using odd versioning)glibmmupdate from 2.34 to 2.58 (should always be in sync withglibin terms of versioning)glibandglibmmversion 2.58.x is the last version supporting autoconf/autobuild tools. Starting with version 2.60 only meson/ninja are supportedgnutls & libgcrypt
https://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-4433/GNU-Gnutls.html
https://www.cvedetails.com/vulnerability-list/vendor_id-4711/product_id-25777/Gnupg-Libgcrypt.html
Needed to be updated to accommodate above version updates
libsigc++update from 2.4.0 to 2.10libxml++update from 2.36 to 2.40.1Others
rmlint&jpcre2aresynocli-filedependencies to which trivial updates where available (relates on PR openssl: update to version 1.1.1h #4155)--
jpcre2update from version 10.31.03 to 10.32.01--
rmlintupdate from 2.9 to 2.10.1sslhUpdate from 1.19c to 1.21cgnupgupdate from 2.1.6 to 2.2.23libassuanUpdate from 2.2.1 to 2.5.3 (forgnupg)libksbaUpdate from version 1.3.3 to 1.4.0 (forgnupg)