Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#72347 - [tpm2-pkcs11] Using as PKCS11Provider for ssh causes core dump

Attached to Project: Community Packages
Opened by Xuanrui Qi (xuanrui) - Tuesday, 05 October 2021, 01:57 GMT
Last edited by Jonas Witschel (diabonas) - Tuesday, 05 October 2021, 08:43 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonas Witschel (diabonas)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Using /usr/lib/pkcs11/libtpm2_pkcs11.so as PKCS11Provider for ssh causes a core dump:

malloc(): invalid next size (unsorted)

Steps to reproduce:
* use libtpm2_pkcs11.so as PKCS11Provider. For example, add to ~/.ssh/config

Host *
PKCS11Provider /usr/lib/pkcs11/libtpm2_pkcs11.so

* ssh into any server
This task depends upon

Closed by  Jonas Witschel (diabonas)
Tuesday, 05 October 2021, 08:43 GMT
Reason for closing:  Not a bug
Additional comments about closing:  A manual database upgrade using "tpm2_ptool dbup" was required
Comment by Jonas Witschel (diabonas) - Tuesday, 05 October 2021, 08:01 GMT
Is this a fresh installation, or did you upgrade tpm2-pkcs11 from a previously installed version? If the latter is the case, the automatic database update might have gone wrong. Try backing up the database file (usually ~/.tpm2_pkcs11/tpm2_pkcs11.sqlite3), then run "tpm2_ptool dbup" and report the output back here.
Comment by Xuanrui Qi (xuanrui) - Tuesday, 05 October 2021, 08:39 GMT
OK, now this worked. Thanks!
Comment by Jonas Witschel (diabonas) - Tuesday, 05 October 2021, 08:42 GMT
No problem! Since this is not an Arch Linux packaging problem, but an issue with the upstream database upgrade process, I am going to close the bug report here.

Loading...