-
Notifications
You must be signed in to change notification settings - Fork 51
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
Get maintained #27
Comments
Sorry I don't think I noticed your proposal before. |
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? |
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 :-) |
@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. |
Thanks, Frank! Where are these security fixes for now? |
they are available as commits in master |
Hi, guys! Note the #48 issue! |
@frankmorgner I see nothing new in master since the 0.6.11 release I made in May 2019. |
@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. |
Hi Ludovic!
I currently maintain the package in Sisyphus and already have a number of patches I want to integrate. If you're really looking for a new maintainer, I can take it over.
The text was updated successfully, but these errors were encountered: