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
app-crypt/libtpms: Bump to 0.8.2 #19630
Conversation
Pull request CI reportReport generated at: 2021-02-24 15:55 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
That's probably a candidate for a security bug. Could you file one? |
6ab955f
to
9ce145a
Compare
Pull Request assignmentSubmitter: @salahcoronya dev-libs/libtpms: @salahcoronya, @gentoo/proxy-maint Linked bugsBugs linked: 772410 In order to force reassignment and/or bug reference scan, please append Docs: Code of Conduct ● Copyright policy (expl.) ● Devmanual ● GitHub PRs ● Proxy-maint guide |
Pull request CI reportReport generated at: 2021-02-24 18:55 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
9ce145a
to
8251c72
Compare
Pull request CI reportReport generated at: 2021-02-25 04:50 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
8251c72
to
cc9c5f4
Compare
Pull request CI reportReport generated at: 2021-02-27 03:15 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
Bug: https://bugs.gentoo.org/772410 Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Salah Coronya <salah.coronya@gmail.com>
Package-Manager: Portage-3.0.13, Repoman-3.0.2 Signed-off-by: Salah Coronya <salah.coronya@gmail.com>
Upstream has release version 0.8.2 with the following note:
|
Pull request CI reportReport generated at: 2021-03-02 16:40 UTC There are existing issues already. Please look into the report to make sure none of them affect the packages in question: |
diff --git a/configure.ac b/configure.ac | ||
index 40d2c7f..809f8e0 100644 | ||
--- a/configure.ac | ||
+++ b/configure.ac | ||
@@ -304,7 +304,7 @@ if test "x$enable_hardening" != "xno"; then | ||
AC_SUBST([HARDENING_LDFLAGS]) | ||
fi | ||
|
||
-CFLAGS="$CFLAGS $COVERAGE_CFLAGS -Wall -Werror -Wreturn-type -Wsign-compare -Wno-self-assign" | ||
+CFLAGS="$CFLAGS $COVERAGE_CFLAGS -Wall -Wreturn-type -Wsign-compare -Wno-self-assign" | ||
CFLAGS="$CFLAGS -Wmissing-prototypes" | ||
LDFLAGS="$LDFLAGS $COVERAGE_LDFLAGS" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any chance to get this upstreamed? It's annoying having to carry this kind of patch around version after version.
The fact RSA keys are not as strong as they should be is disclosed in this version:
Note: The TPM 2 implementation returns 2048 bit keys with ~1984 bit
strength due to a bug in the TPM 2 key creation algo that cannot
easily be fixed. The bug is in RsaAjustPrimeCandidate, which is
called before the prime number check.
See stefanberger/libtpms#183