mirror of
https://github.com/apple/swift-crypto
synced 2026-11-22 04:30:39 +00:00
## Motivation Xcode 27 is now available[^1] so it's time to merge in our 5.x branch to main and release 5.0. ## Modifications See "Release Notes" section below for overview of changes and links to the PRs that landed on the 5.x branch during the beta period. ## Result The main branch will be ready to tag a 5.0 release. [^1]: https://developer.apple.com/download/all/?q=Xcode%2027 --- ## Release Notes Swift Crypto 5.0 aligns the cross-platform API surface with CryptoKit as shipped in Xcode 27 (CryptoKit-383.2.1), and takes the opportunity to streamline the package for both adopters and maintainers. Most users will be able to depend on the 1.0.0, 2.0.0, 3.0.0, 4.0.0, or 5.0.0 series of releases. To do so, please use the following dependency in your `Package.swift`: ```swift .package(url: "https://github.com/apple/swift-crypto.git", "1.0.0" ..< "6.0.0"), ``` ### Requires Swift 6.2 The package now declares 6.2 as the minimum Swift version in its package manifest. ### New span-based API CryptoKit's new non-allocating, span-based entry points are now available cross-platform: - `SymmetricKey` gains `bytes: RawSpan`, `init(copying: RawSpan)`, `init(copyingWithZeroing: inout MutableRawSpan)`, and `init(size:initializingWith:)` which initializes the key through an `inout OutputRawSpan`. - `HashFunction` gains `update(bytes: RawSpan)` and `hash(bytes: RawSpan)`, and `Digest` gains `init?(copying: RawSpan)`. - `HMAC` gains `authenticationCode(for: RawSpan, using:)`. - `HKDF` gains `deriveKey(inputKeyMaterial:salt:info:output:)` writing into an `inout OutputRawSpan`, along with span-based `extract` and `expand`. The existing `DataProtocol` overload now has a fast path for contiguous salt and info. - `AES.GCM` and `ChaChaPoly` gain in-place `seal(inPlace:using:nonce:authenticating:tag:)` and `open(inPlace:using:nonce:authenticating:tag:)` over `MutableRawSpan`, and their `Nonce` types gain `bytes: RawSpan` and `init(copying: RawSpan)`. ### Single-use KEM keys A new `KEMOneTimePrivateKey` protocol, refining `~Copyable` and `Sendable`, provides a `consuming func decapsulate(_:)` so a decapsulation key cannot be reused. Conforming types are `MLKEM768.OneTimePrivateKey`, `MLKEM1024.OneTimePrivateKey`, and `XWingMLKEM768X25519.OneTimePrivateKey`. ### Extensible enums Historically Swift Crypto needed a new major version each time CryptoKit added a case to a non-frozen enum, because Swift Crypto is not built with library evolution. All public non-frozen enums are now marked `@nonexhaustive` (SE-0487), which should remove that reason for future major bumps. Adopters who do not switch over these enums should not need to widen their version constraints again. ### Other changes - Symbols that were previously marked `@_spi(...) public` have been made internal; they were never intended to be available. - `@available` annotations have been removed from `Crypto`; they are unused in all supported compilation modes. - Some internal reference types are now marked `final` - Some unused code, e.g. `ECDSASignature.derBytes`, is removed. ### Build and packaging - The `CCryptoBoringSSLShims` target is removed, along with all `bindMemory(to:)` calls. - The `.gyb` templates for nonces, digests, ECDH, ECDSA, MLDSA, and MLKEM are removed and the generated Swift is checked in. The BoringSSL backend templates for MLDSA and MLKEM remain. - Conditional compilation is simplified to `#if canImport(CryptoKit)`; branches that could never be taken are gone. - Developing the BoringSSL backend on macOS is no longer supported. Use the Dev Container configuration now shipped in the repository, or build on the target platform. - Warnings are silenced for vendored C sources: `-Wshorten-64-to-32` for BoringSSL and `macro-redefined` for XKCP. CI builds with `-warnings-as-errors`. ### Commits The changes in this release were reviewed and merged to the 5.x branch during the beta period: -0a26a9e3[5.x] Align with CryptoKit APIs from Xcode 27 beta 1 (#442) -8ee9962f[5.x] Align with CryptoKit APIs from Xcode 27 beta 2 (#444) -ce8db476[5.x] Align with CryptoKit APIs from Xcode 27 beta 4 (#453) -15b0fb5b[5.x] Adopt CheckImplementationOnly and CI with -warnings-as-errors (#454) -b3746b14[5.x] Remove bindMemory(to:) calls and the CCryptoBoringSSLShims target (#455) -57782dc6[5.x] Remove duplicate imports from gyb-generated MLDSA backend code (#458) -2c45ca2f[5.x] Remove unused internal code path: ECDSASignature.derBytes (#457) -33785f67[5.x] Mark some class types as final (#456) -2e074efb[5.x] Remove native SwiftPM build-system workaround in CI (#461) -20f90497[5.x] Align with CryptoKit from Xcode 27 beta 6 (#462) --------- Co-authored-by: Dmitry <45711841+darkdi@users.noreply.github.com> Co-authored-by: Cory Benfield <lukasa@apple.com>
179 lines
7.9 KiB
Swift
179 lines
7.9 KiB
Swift
//===----------------------------------------------------------------------===//
|
||
//
|
||
// This source file is part of the SwiftCrypto open source project
|
||
//
|
||
// Copyright (c) 2019-2020 Apple Inc. and the SwiftCrypto project authors
|
||
// Licensed under Apache License v2.0
|
||
//
|
||
// See LICENSE.txt for license information
|
||
// See CONTRIBUTORS.txt for the list of SwiftCrypto project authors
|
||
//
|
||
// SPDX-License-Identifier: Apache-2.0
|
||
//
|
||
//===----------------------------------------------------------------------===//
|
||
|
||
#if canImport(CryptoKit)
|
||
@_exported import CryptoKit
|
||
#else
|
||
extension Insecure {
|
||
/// An implementation of SHA1 hashing.
|
||
///
|
||
/// The ``SHA1`` hash implements the ``HashFunction`` protocol to produce a
|
||
/// SHA1 digest (``SHA1Digest``).
|
||
///
|
||
/// You can compute the digest by calling the static ``hash(data:)`` method
|
||
/// once. Alternatively, if the data that you want to hash is too large to
|
||
/// fit in memory, you can compute the digest iteratively by creating a new
|
||
/// hash instance, calling the ``update(data:)`` method repeatedly with
|
||
/// blocks of data, and then calling the ``finalize()`` method to get the
|
||
/// result.
|
||
///
|
||
/// - Important: This hash algorithm isn’t considered cryptographically
|
||
/// secure, but is provided for backward compatibility with older services
|
||
/// that require it. For new services, prefer one of the secure hashes, like
|
||
/// ``SHA512``.
|
||
public struct SHA1: HashFunctionImplementationDetails, Sendable {
|
||
/// The number of bytes that represents the hash function’s internal
|
||
/// state.
|
||
public static let blockByteCount: Int = 64
|
||
|
||
/// The number of bytes in a SHA1 digest.
|
||
public static let byteCount: Int = 20
|
||
|
||
/// The digest type for a SHA1 hash function.
|
||
public typealias Digest = Insecure.SHA1Digest
|
||
var impl: DigestImpl<SHA1>
|
||
|
||
/// Creates a SHA1 hash function.
|
||
///
|
||
/// Initialize a new hash function by calling this method if you want to
|
||
/// hash the data iteratively, such as when you don’t have a buffer
|
||
/// large enough to hold all the data at once. Provide data blocks to
|
||
/// the hash function using the ``update(data:)`` or
|
||
/// ``update(bufferPointer:)`` method. After providing all the data,
|
||
/// call ``finalize()`` to get the digest.
|
||
///
|
||
/// If your data fits into a single buffer, you can use the
|
||
/// ``hash(data:)`` method instead, to compute the digest in a single
|
||
/// call.
|
||
public init() {
|
||
impl = DigestImpl()
|
||
}
|
||
|
||
/// Incrementally updates the hash function with the contents of the
|
||
/// buffer.
|
||
///
|
||
/// Call this method one or more times to provide data to the hash
|
||
/// function in blocks. After providing the last block of data, call the
|
||
/// ``finalize()`` method to get the computed digest. Don’t call the
|
||
/// update method again after finalizing the hash function.
|
||
///
|
||
/// - Note: Typically, it’s safer to use an instance of
|
||
/// <doc://com.apple.documentation/documentation/foundation/data>, or
|
||
/// some other type that conforms to the
|
||
/// <doc://com.apple.documentation/documentation/foundation/dataprotocol>,
|
||
/// to hold your data. When possible, use the ``update(data:)`` method
|
||
/// instead.
|
||
///
|
||
/// - Parameters:
|
||
/// - bufferPointer: A pointer to the next block of data for the ongoing
|
||
/// digest calculation.
|
||
public mutating func update(bufferPointer: UnsafeRawBufferPointer) {
|
||
impl.update(data: bufferPointer)
|
||
}
|
||
|
||
/// Finalizes the hash function and returns the computed digest.
|
||
///
|
||
/// Call this method after you provide the hash function with all the
|
||
/// data to hash by making one or more calls to the ``update(data:)`` or
|
||
/// ``update(bufferPointer:)`` method. After finalizing the hash
|
||
/// function, discard it. To compute a new digest, create a new hash
|
||
/// function with a call to the ``init()`` method.
|
||
///
|
||
/// - Returns: The computed digest of the data.
|
||
public func finalize() -> Self.Digest {
|
||
return impl.finalize()
|
||
}
|
||
}
|
||
|
||
/// An implementation of MD5 hashing.
|
||
///
|
||
/// The ``MD5`` hash implements the ``HashFunction`` protocol to produce an
|
||
/// MD5 digest (``MD5Digest``).
|
||
///
|
||
/// You can compute the digest by calling the static ``hash(data:)`` method
|
||
/// once. Alternatively, if the data that you want to hash is too large to
|
||
/// fit in memory, you can compute the digest iteratively by creating a new
|
||
/// hash instance, calling the ``update(data:)`` method repeatedly with
|
||
/// blocks of data, and then calling the ``finalize()`` method to get the
|
||
/// result.
|
||
///
|
||
/// - Important: This hash algorithm isn’t considered cryptographically
|
||
/// secure, but is provided for backward compatibility with older services
|
||
/// that require it. For new services, prefer one of the secure hashes, like
|
||
/// ``SHA512``.
|
||
public struct MD5: HashFunctionImplementationDetails, Sendable {
|
||
/// The number of bytes that represents the hash function’s internal
|
||
/// state.
|
||
public static let blockByteCount: Int = 64
|
||
/// The number of bytes in an MD5 digest.
|
||
public static let byteCount: Int = 16
|
||
|
||
/// The digest type for a MD5 hash function.
|
||
public typealias Digest = Insecure.MD5Digest
|
||
var impl: DigestImpl<MD5>
|
||
|
||
/// Creates a MD5 hash function.
|
||
///
|
||
/// Initialize a new hash function by calling this method if you want to
|
||
/// hash the data iteratively, such as when you don’t have a buffer
|
||
/// large enough to hold all the data at once. Provide data blocks to
|
||
/// the hash function using the ``update(data:)`` or
|
||
/// ``update(bufferPointer:)`` method. After providing all the data,
|
||
/// call ``finalize()`` to get the digest.
|
||
///
|
||
/// If your data fits into a single buffer, you can use the
|
||
/// ``hash(data:)`` method instead, to compute the digest in a single
|
||
/// call.
|
||
public init() {
|
||
impl = DigestImpl()
|
||
}
|
||
|
||
/// Incrementally updates the hash function with the contents of the
|
||
/// buffer.
|
||
///
|
||
/// Call this method one or more times to provide data to the hash
|
||
/// function in blocks. After providing the last block of data, call the
|
||
/// ``finalize()`` method to get the computed digest. Don’t call the
|
||
/// update method again after finalizing the hash function.
|
||
///
|
||
/// - Note: Typically, it’s safer to use an instance of
|
||
/// <doc://com.apple.documentation/documentation/foundation/data>, or
|
||
/// some other type that conforms to the
|
||
/// <doc://com.apple.documentation/documentation/foundation/dataprotocol>,
|
||
/// to hold your data. When possible, use the ``update(data:)`` method
|
||
/// instead.
|
||
///
|
||
/// - Parameters:
|
||
/// - bufferPointer: A pointer to the next block of data for the ongoing
|
||
/// digest calculation.
|
||
public mutating func update(bufferPointer: UnsafeRawBufferPointer) {
|
||
impl.update(data: bufferPointer)
|
||
}
|
||
|
||
/// Finalizes the hash function and returns the computed digest.
|
||
///
|
||
/// Call this method after you provide the hash function with all the
|
||
/// data to hash by making one or more calls to the ``update(data:)`` or
|
||
/// ``update(bufferPointer:)`` method. After finalizing the hash
|
||
/// function, discard it. To compute a new digest, create a new hash
|
||
/// function with a call to the ``init()`` method.
|
||
///
|
||
/// - Returns: The computed digest of the data.
|
||
public func finalize() -> Self.Digest {
|
||
return impl.finalize()
|
||
}
|
||
}
|
||
}
|
||
#endif // canImport(CryptoKit)
|