-
Notifications
You must be signed in to change notification settings - Fork 62
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
Time to roll v0.8.2? #56
Comments
+1 |
+1
Steven Haigh <notifications@github.com> schrieb am Di., 14. Mai 2019, 03:42:
… It seems most distros will only send out new versions once an official
release is made.
Currently, from my testing of pam_mysql now - 0.8.1 only seems to support
md5(?) via crypt. From the commit history, I believe using crypt will now
also do up to sha512.
It would be good to release this (if working) as v0.8.2 so this
improvement can be put out in the distros.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#56?email_source=notifications&email_token=AFA7F2V5YW35DC7X34GXBSTPVIKKDA5CNFSM4HMUWNN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GTR4TGA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFA7F2S3FPXMIYQ7H7LNATTPVIKKDANCNFSM4HMUWNNQ>
.
|
I'm currently working on switching the build system to meson (I find autotools incomprehensible!). Once I get that going, I'll do a new release. Apologies for the delay. |
Now fixed (1.0 pre-releases are available for testing; I've successfully built and tested on Arch Linux, Mint and Centos 8 so far). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems most distros will only send out new versions once an official release is made.
Currently, from my testing of pam_mysql now - 0.8.1 only seems to support md5(?) via crypt. From the commit history, I believe using crypt will now also do up to sha512.
It would be good to release this (if working) as v0.8.2 so this improvement can be put out in the distros.
The text was updated successfully, but these errors were encountered: