-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Linux Support #40
Comments
It would be great to add Linux support, but not for any price. My goal with this SDK is to make it as easy as possible to use. Therefore, if we can come up with a plan to support iOS, macOS, and Linux in a way that they can all be supported easily, I would be happy to review that! |
Yep, I would integrate it in a way s.t. nothing changes for iOS/macOS user of the sdk. |
Hi, .Package(url: "https://github.com/IBM-Swift/BlueCryptor.git", majorVersion: <majorVersion>, minor: <minor>) Hope this helps. |
I also found that there is a pure Swift implementation: https://github.com/krzyzanowskim/CryptoSwift |
Had also a look at this lib - unfortunately doesn't support ES256 which is expected by apple as signatureAlogrithm for JWT |
This issue is stale because it has been open for 30 days with no activity. Remove the Stale label or comment or this will be closed in 10 days. |
https://github.com/apple/swift-crypto could be a cool option, though it'd only work for iOS/tvOS 13+, watchOS 6.0+ and macOS 10.15+ on Apple platforms |
@aaronsky good suggestion! I don't like dropping < iOS 13 anytime soon. If there's any other way of doing this I would prefer to do that. |
To allow users to deploy the sdk on Linux servers, CommonCrypto needs to be replaced (or complemented) by a Crypto-Lib which is available on Linux (e.g OpenSSL).
Linux compatibility opens up another set of use cases, e.g. giving your SlackBot the skill to invite a new Testflight user, get Build information, etc …
Our company bot marvin - which lives in a linux environment - already uses the sdk with these changes schwmi#3. Nevertheless, if we want to merge these changes back in, we should integrate it more nuanced s.t. iOS+macOS still uses CommonCrypto and OpenSSL is only used in a Linux environment.
What do you think @AvdLee?
The text was updated successfully, but these errors were encountered: