[swift-evolution] Crypto routines as part of the core library

[Travis Beech]

Core libraries would be a great place, I just think this is a huge oversight in the language itself. I don’t think libraries found out on Github should be trusted, I think crypto should be done in an organized effort to ensure that the implementations are proper.

Travis Beech | Principal Developer | Unwired Revolution | c: 1 (209) 535-5357
Optimizing Operations for Mobile and Distributed Systems

From: <milseman at apple.com<mailto:milseman at apple.com>> on behalf of Michael Ilseman <milseman at apple.com<mailto:milseman at apple.com>>
Date: Thursday, April 14, 2016 at 2:33 PM
To: Travis Beech <tbeech at unwiredrevolution.com<mailto:tbeech at unwiredrevolution.com>>
Cc: David Waite <david at alkaline-solutions.com<mailto:david at alkaline-solutions.com>>, "swift-evolution at swift.org<mailto:swift-evolution at swift.org>" <swift-evolution at swift.org<mailto:swift-evolution at swift.org>>
Subject: Re: [swift-evolution] Crypto routines as part of the core library

Why would it need to be built into the language proper instead of the core libraries? I am not too familiar with the core libraries, but perhaps swift-corelibs-dev<https://lists.swift.org/mailman/listinfo/swift-corelibs-dev> is the more appropriate mailing list here?

On Apr 13, 2016, at 7:24 PM, Travis Beech via swift-evolution <swift-evolution at swift.org<mailto:swift-evolution at swift.org>> wrote:

So what would it take to get a standard set of crypto API's built into the language?

Travis Beech  |  Principal Developer  |  Unwired Revolution  |  c: 1 (209) 535-5357
Optimizing Operations for Mobile and Distributed Systems

On Apr 13, 2016, at 10:11 AM, David Waite <david at alkaline-solutions.com<mailto:david at alkaline-solutions.com>> wrote:

I don’t know if we need a boost-like parent project in order to start building core code to be brought for inclusion.

I think success will naturally bring such a project structure - people seeking a curated and integrated set of frameworks to get common functionality.

-DW

On Apr 13, 2016, at 12:16 PM, Tino Heth via swift-evolution <swift-evolution at swift.org<mailto:swift-evolution at swift.org>> wrote:

This seems like a great candidate for a library that could be developed in the community and then possibly brought into Corelibs in a future version
true — but sadly, there seems to be either no interest or manpower for a boost-like infrastructure…
Like many other fundamental topics, I don't think crypto belongs to the stdlib, but none the less, there should be a standard library for encryption/hashing.
_______________________________________________

_______________________________________________
swift-evolution mailing list
swift-evolution at swift.org<mailto:swift-evolution at swift.org>
https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160414/2449038e/attachment.html>