> On Dec 1, 2017, at 10:37 PM, Xiaodi Wu via swift-evolution > <[email protected]> wrote: > > That said, I am not sure that this proposal should give any pretense of being > suitable for cryptographic use. On implementation, the code will not have > been audited for that purpose, although the author very rightly attempts to > use the "best" possible sources of entropy available for each platform. > Perhaps explicitly _not_ supporting cryptographic operations is the more > Swifty way to go (in the sense that, where possible, Swift API design aims to > help users avoid footguns).
People will use it for crypto whether we want them to or not. None of the proposals involve actually writing cryptographic primitives, just calling out to well-known functions like `arc4random()` or reading from special devices like `/dev/urandom`. I would hope that Apple's security team can spare the time to review the security-critical parts and sign off on them, and I'd be perfectly happy to see this proposal be approved but the final merge into the language be deferred until they've taken a look at it. -- Brent Royal-Gordon Architechies
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
