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
Replace/fork security gem with a more suitable alternative for fastlane #11637
Comments
It seems like you have not included the output of To make it easier for us help you resolve this issue, please update the issue to include the output of |
Are there other users of this gem that would benefit from a maintained version as well or just fastlane? |
@janpio It all depends on tight the integration with fastlane we want. Example: with the |
I just took a look at this issue, and went to see the reverse dependencies of security on ruby gems. https://rubygems.org/gems/security/reverse_dependencies
So it looks like the only real use of this gem besides fastlane and fastlane-related projects is credential storage in github_bus_factor and u3d. The first, github_bus_factor seems not to be maintained for a couple of years, the latter, u3d is maintained by @lacostej and myself but we use it only in a very limited fashion and we could implement that manually if need be, or stay with the security gem as is now. So @janpio right now I see no other users of the gem that could benefit from a maintained version! |
All the non- |
Perfect, so it makes total sense what @lacostej suggested. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest |
This definitely think this needs to get done at some point! I created an issue that was caused by this gem a few months back - #10746 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest |
This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍 |
The security gem used primarily for interaction with the Mac keychain is not maintained.
The gem has a few limitations that we want to fix (fastlane-community/security#4, fastlane-community/security#5). There are also lots of places where actions interact with the security program and could benefit from a supporting layer in fastlane.
This issue describes an approach to solve this problem.
Proposal
The first step is to fork the gem and remove all functions not used within fastlane. We aim at keeping a similar API for the remaining implementation in order to use migration if any external action depending on it want to use it.
The second step [optional] is to add features to the new API to help implementing functionality. A nice functionality might be to provide proper error handling (see fastlane-community/security#5 as example of extra information available).
Analysis:
gem usage
The gem is required in 2 places
API usage
As of 2018-01-19, fastlane only uses the following methods:
Security::InternetPassword.find|add|delete
(identified running
git grep Security::
)Direct calls to security program
NOTES
The text was updated successfully, but these errors were encountered: