Why? #5
Why? #5
Comments
Because I can. At first I played with OpenSSL and CommonCrypto, then I moved to pure Swift implementation, partly for fun, partly because I'm about to implement things that are not available in CommonCrypto. I'm touched that you compared this not to OpenSSL ;) |
|
@schwa @krzyzanowskim Also, because adding CommonCrypto to a Swift framework (not app) is broken. See http://stackoverflow.com/questions/25248598/importing-commoncrypto-in-a-swift-framework. |
Thanks for putting this library together. Love #pureswift. Keep the good work! |
Very much appreciated! Using "native" libraries invalidates the security benefits of a safe lingo... |
@hpique I think it works now https://github.com/onmyway133/CommonCrypto.swift |
Why not just use CommonCrypto from Swift?
What's the reasoning behind creating this project?
Thanks!
The text was updated successfully, but these errors were encountered: