> On Jun 13, 2016, at 3:54 PM, Travis Beech via swift-evolution > <[email protected]> wrote: > > With the open sourcing of Swift and the growing concerns around security and > user privacy, Swift is lacking common crypto API’s as part of the core > libraries. I’d like to propose that we add common crypto functionality as > part of the Swift Core Libraries. I believe that something as important as > encryption, hashing, and certificate handling should come as part of the core > libraries and not provided by a 3rd party library. > > Below are examples of what I would imagine the Core Libraries would provide: > > Encryption > - Symmetric Encryption > - e.g. AES > - Asymmetric Encryption > - e.g. RSA > > Hashing > - Keyed Hashing > - e.g. HMACSHA1 > - Un-keyed Hashing > - e.g. MD5 > > Certificate Handling > - X509 Certificates > - Certificate based authentication > - Certificate import, e.g. PEM > - SSL pinning
I have a sneaking suspicion this is better discussed by lawyers than on the SE list. -- E
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
