Get maintained about pam_pkcs11 HOT 9 CLOSED

Sorry I don't think I noticed your proposal before.
Do you still volunteer to maintain pam_pkcs11?

from pam_pkcs11.

Hi! Probably, yes.

I've made a special version for Sisyphus with many new configuration options, configurable prompts, and low-level modules (a card-specific implementation to get an exact number of PIN attempts, for instance).

However, I don't think all of that is really needed in the mainstream pam_pkcs11 project. So, what are the criteria of updating / maintaining the mainstream version?

from pam_pkcs11.

I just sent you an invitation to join the "pam_pkcs11 maintainers" group.

It is now up to you to decide what you want to do with pam_pkcs11 :-)
You can even include card specific code. Maybe with the possibility to disable it or not enable it by default.

from pam_pkcs11.

@wolneykien please create a new release, because there were some security issues discovered (https://www.x41-dsec.de/lab/advisories/x41-2018-003-pam_pkcs11/). I've fixed all of them upstream, but I'll leave the testing, packaging and write up of some release notes to you. Maybe you also want to cherry-pick some of your more generic changes.

from pam_pkcs11.

Thanks, Frank! Where are these security fixes for now?

from pam_pkcs11.

they are available as commits in master

from pam_pkcs11.

Hi, guys! Note the #48 issue!

from pam_pkcs11.

@frankmorgner I see nothing new in master since the 0.6.11 release I made in May 2019.
I guess the commits your are talking about are already present in release 0.6.11.
If that is not the case then please be more specific.

from pam_pkcs11.

@wolneykien I propose you to create Pull Requests with your changes rebased on the current master. Since you created different branches it should be easy to create different PR. Of course the order is important since some patches depend on other ones.

If nobody complains after some days you can merge/apply them yourself.

from pam_pkcs11.