Lock htauth gem version to 2.0.0 #34
Conversation
|
@torjeh funnily enough - the reason that I updated htauth was because of the need for bcrypt2 htpasswd files from folks using chef cookbook (copiousfreetime/htauth#12). I haven't been a chef user in a long time, do you have any suggestions on a solution to support everyone? The only one that immediately comes to mind is to use a pure ruby bcrypt library, and I don't think there is one. |
|
I got some feedback form the bcrypt folks in bcrypt-ruby/bcrypt-ruby#224
I don't know if that helps or not. Of if that is even applicable to chef cookbooks |
|
Thank you so much for looking into this! I guess I should have created an issue instead of a pull request, maybe. The discussion is certainly helpful for us. I guess for us we will first constrain the version of the gem to 2.0.0 in our wrapper cookbooks, and do a proper upgrade at a later point. I am not 100% sure how we will proceed. We were a bit surprised that our chef clients suddenly tried to install a newer version of a gem, since we have our coookbook versions locked in a Chef policyfiles. So we were not expecting any changes, but we forgot about the gems :) |
|
would be great to have this on default - i have to edit this atm on my own |
|
I believe #41 has resolved this and has been released as 1.0.0. Please re-open if that isn't the case. |
htauth was upgraded April 2nd 2020 to version 2.1.1 and now requires bcrypt that needs to be compiled at runtime. Currently this breaks the cookbook for environments where this is not possible.
This is a workaround to make sure that we keep using the same version of htauth that has been used for a long time now.