334 Commits
Author SHA1 Message Date
Charles ZablitandCory Benfield ac5e08be49 [CMake] Require CMake 3.29 and drop the CMP0157 checks (#325)
Follow-up to #324: require CMake 3.29 instead of checking for CMP0157,
and leave `CMAKE_Swift_COMPILATION_MODE` to the caller. The toolchain
build passes it (swiftlang/swift#94066).

Tracking: swiftlang/swift#93995

assisted by Claude

Co-authored-by: Cory Benfield <lukasa@apple.com>
2026-11-20 19:02:07 +00:00
Cory Benfield 8d6849435f Correctly require no padding bits in bit strings for signatures (#329)
Motivation

We have a check that requires that the bit strings for Ed25519
signatures don't have any padding bits. That check is good, but the same
check should have been applied to all the signatures, and it wasn't.

There is no particular security risk with this: while it allows moderate
signature malleability (as we accept multiple signatures that have
different bits as equally valid), there is no way we can conceive of to
launch an attack based on this malleability: the signature itself needs
to remain valid. The only note is that the representation differs.

Modifications

Centralise the check and apply it to all the code paths. Make sure the
OCSP code doesn't lose track of whether there was any padding.
Add tests for the OCSP verifier and the signature code directly.

Result

No more signature malleability.
2026-11-20 16:23:44 +00:00
Franz Busch 8789d7e78f Guard Security.framework usage with canImport(Security) (#327)
The certificate validation code only needs the `Security` framework, not
`Darwin`.
2026-11-09 10:17:52 +01:00
Charles Zablit 5e9d180069 [CMake] Enable CMP0157 and keep whole-module builds for optimized configs (#324)
Enable CMP0157 so Ninja compiles each Swift module in its own step,
separate from the link. Optimized configurations keep `-wmo`, as under
the old policy.

Tracking: swiftlang/swift#93995

assisted by Claude
2026-11-05 13:43:34 +00:00
Si Beaumont 84f03fafec Widen accepted versions of swift-crypto dependency (#323)
## Motivation:

Swift Crypto 5 is released, but this package only accepts Swift Crypto
versions below 5.0.0, so projects cannot use the two together.

## Modifications:

Widen the accepted Swift Crypto versions to `..<"6.0.0"`, keeping the
existing lower bound.

## Result:

Projects can use Swift Crypto 5 with this package.
1.21.1
2026-10-26 10:47:18 +00:00
apple-ospo[bot] 715a2f4371 Housekeeping: replace repo-level CODE_OF_CONDUCT (#320)
Replace repo-level CODE_OF_CONDUCT file with the inherited org-wide
[Code of
Conduct](https://github.com/apple/.github/blob/main/CODE_OF_CONDUCT.md)
in .github repo.

Co-authored-by: apple-ospo[bot] <326325757+apple-ospo[bot]@users.noreply.github.com>
2026-10-07 16:00:02 +01:00
Jeff LenamonandRaphael Hiesgen ff86b924ea Treat a /0 ipAddress name constraint as covering the whole address space (#317)
### Motivation

`NameConstraintsPolicy` read an all-zero CIDR mask as matching nothing.
An all-zero mask constrains no bits, so it matches every address: the
CA/Browser Forum Baseline Requirements express "this subordinate CA must
not issue for IP addresses" as `excludedSubtrees` of `0.0.0.0/0` and
`::/0`, and against this code those exclusions constrained nothing, so a
leaf with an IP SAN under such a CA verified.

### Modifications

The leading-zero shortcut in `isValidCIDRMask` is removed and the
general leading-ones-then-zeros check decides. The two
`IPAddressNameTests` rows that pinned the old reading now expect a
match. `testAllZeroMaskIsValidCIDRMask` asserts the IPv4 and IPv6
all-zero masks directly, and two `RFC5280PolicyTests1` tests run
`RFC5280Policy` with `0.0.0.0/0` and `::/0` as permitted and as excluded
subtrees. All of them fail on main.

### Result

A `/0` iPAddress constraint covers the whole address space, as RFC 5280
4.2.1.10 defines it. `swift test` passes under the CI flags (`-Xswiftc
-warnings-as-errors --explicit-target-dependency-import-check error
-Xswiftc -require-explicit-sendable`) on Swift 6.1.2; `swift-format lint
--strict` is clean on the changed files.

---------

Co-authored-by: Raphael Hiesgen <r_hiesgen@apple.com>
1.21.0
2026-09-22 14:03:05 +01:00
9ad45b63b0 Make _TinyArray compatible with library evolution (#313)
### Motivation:

Building `_CertificateInternals` with library evolution enabled fails
because `_TinyArray` and its `@usableFromInline` storage are referenced
from `@inlinable` code while their layout and cases are not fixed.

### Modifications:

- Marked `_TinyArray` as `@frozen`.
- Marked its nested `Storage` enum as `@frozen`.

### Result:

`_CertificateInternals` now builds with library evolution enabled in
both Swift 5 and Swift 6 language modes.

Co-authored-by: Volodymyr Klymenko <ceo@build-succeeded.io>
Co-authored-by: Cory Benfield <lukasa@apple.com>
Co-authored-by: Raphael Hiesgen <r_hiesgen@apple.com>
2026-09-18 13:58:44 +00:00
Francesco Paolo Severino 630b5f50f6 Accept Swift Crypto 5 final release (#319)
Motivation:

The final release of Swift Crypto 5 is now available, so we don't need
the `SWIFT_CERTIFICATES_ALLOW_SWIFT_CRYPTO_BETA` env flag anymore and we
can accept the version range `"3.12.3"..<"6.0.0"`

Modifications:

Remove the `SWIFT_CERTIFICATES_ALLOW_SWIFT_CRYPTO_BETA` env var logic
and accept Swift Crypto `"3.12.3"..<"6.0.0"`

Result:

Projects can require both the final release of Swift Crypto 5 and the
latest Swift Certificates release
2026-09-18 13:23:02 +00:00
emaloney c8aece90ea Fix CMSSignerInfo's unsignedAttrs tag (#307)
### Motivation

`CMSSignerInfo` could not round-trip `unsignedAttrs`: it serializes them
as `[1] IMPLICIT SET` but the DER and BER parsers asked for the inner
set with implicit tag `[0]`, so parsing any SignerInfo with unsigned
attributes threw `unexpectedFieldType: [1]`.

### Changes

Fixes issue #306 by:

- Correcting the `unsignedAttrs` inner set identifier from `[0]` to
`[1]` in the DER and BER initializers of `CMSSignerInfo`.
- Adding a round-trip unit test for a `CMSSignerInfo` carrying
`unsignedAttrs`.

### Result

`unsignedAttrs` now round-trip correctly; no behavior change to the
(already correct) serialized output.
1.20.0
2026-08-27 20:07:04 +01:00
Aryan Shah 449dbbecd0 Reject chains where directoryName name constraints are involved (#305)
### Motivation:

[`NameConstraintsPolicy`](https://github.com/apple/swift-certificates/blob/a12bcbc0df9770fe3b0439f38f16b74f37c896c7/Sources/X509/Verifier/RFC5280/NameConstraintsPolicy.swift#L24)
(used as part of
[`RFC5280Policy`](https://github.com/apple/swift-certificates/blob/a12bcbc0df9770fe3b0439f38f16b74f37c896c7/Sources/X509/Verifier/RFC5280/RFC5280Policy.swift#L144))
determines whether a certificate is valid under the `directoryName` name
constraints that are present in its issuing CA's `nameConstraints`
extension. It currently does so by [checking for *exact*
equality](https://github.com/apple/swift-certificates/blob/a12bcbc0df9770fe3b0439f38f16b74f37c896c7/Sources/X509/Verifier/RFC5280/DirectoryNames.swift#L23-L26)
between the constraint (which appears in either the `permittedSubtrees`
or `excludedSubtrees` field) and the certificate's subject DN (or any
`directoryName` value in its SAN).

However, per [RFC 5280
§4.2.1.10](https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.10) and
[§7.1](https://www.rfc-editor.org/rfc/rfc5280#section-7.1), a
subordinate certificate's DN is within the subtree if it has at least as
many RDNs as the subtree DN and the two DNs *match* when trailing RDNs
in the subordinate's DN are ignored. Additionally, per [RFC 5280
§7.1](https://www.rfc-editor.org/rfc/rfc5280#section-7.1), DN attribute
values must first be normalized through the [LDAP
StringPrep](https://www.rfc-editor.org/rfc/rfc4518) algorithm before
being compared. `NameConstraintsPolicy` only checks exact equality; it
does not check whether the subordinate's DN is *within the subtree* per
[RFC 5280 §7.1](https://www.rfc-editor.org/rfc/rfc5280#section-7.1) nor
applies the StringPrep normalization.

We currently do not correctly validate directoryName name constraints.
Performing the validation correctly involves implementing a complex
algorithm. We should therefore just reject chains where directoryName
name constraints are involved.

### Modifications:

- Removed the `directoryNameMatchesConstraint` method.
- Updated `NameConstraintsPolicy` to simply reject chains involving a
`directoryName` name constraint on both the `permittedSubtrees` and
`excludedSubtrees` path.
- Updated all existing directoryName name constraints tests to now
assert for failure.

### Result:

We now fail-safe on chains involving directoryName name constraints.
1.19.4
2026-07-17 11:30:03 +01:00
Raphael Hiesgen 89fbc37142 Add env flag to accept swift-crypto beta releases (#302)
### Motivation

Tagged releases can only have other tagged releases in their
dependencies. Tagging a package that depends on a swift-crypto beta and
swift-certificates requires a swift-certificates release that accepts a
swift-crypto beta release.

### Modifications

Introduce an environment flag that allows swift-certificates to depend
on swift-crypto beta releases.

### Results

Setting an environment flag can widen the upper limit of accepted
swift-cryto version to include 5.0.0 beta release.
1.19.3
2026-07-01 16:07:07 +01:00
Raphael Hiesgen daf628a263 Update benchmarks package name and thresholds (#303)
### Motivation

The benchmark package got renamed and changed the allocator. Benchmarks
thresholds passed with [version
1.34](https://github.com/apple/swift-certificates/actions/runs/28015378822/job/82918309837#step:6:198)
and then failed with [version
1.35](https://github.com/apple/swift-certificates/actions/runs/28055879634/job/83057967622#step:6:149).

### Modifications

* Follow benchmark package name change.
* Update failing thresholds.

### Results

6.3 benchmark CI pipeline passes.
2026-07-01 10:14:00 +01:00
eaa10d47d1 documentation updates (#296)
- **Fix stale DocC disambiguation hash for PrivateKey init**
- **Fix documentation errors, typos, and a bug in
CertificateStore.appending**
- **code example fixes within the existing articles:**
- **Lots of smaller fixes across the board - some copy/pasta errors,
consistency in usage, typos and grammar issues - added documentation
comments where missing to get all public types covered - applied
internal style guidelines for representing the types**

---------

Co-authored-by: David Nadoba <dnadoba@gmail.com>
Co-authored-by: Cory Benfield <lukasa@apple.com>
Co-authored-by: Raphael <josephnoir@users.noreply.github.com>
1.19.2
2026-06-15 13:04:58 -07:00
Rick Newton-Rogers a12bcbc0df Migrate macOS build argument overrides to Swift version inputs (#298)
Motivation

* The shared `macos_tests.yml` workflow no longer accepts
  `xcode_16_2_build_arguments_override` and the `xcode_16_3` input is a
  no-op. Passing the removed input causes CI to fail.
* Older Xcodes are being removed from the runners; Swift version inputs
  are the replacement.

Modifications

* Replace `xcode_16_2/16_3_build_arguments_override` with
  `swift_6_1/6_2/6_3_build_arguments_override` carrying the same
  `-Xswiftc -Xfrontend -Xswiftc -require-explicit-sendable` value.

Result

* macOS CI passes again using the Swift version inputs.
2026-05-15 11:30:48 +02:00
Benedek Kozma bde8ca32a0 Remove Foundation import (#297)
#227
1.19.1
2026-04-28 19:49:37 +01:00
LamTrinh.Dev e9312a35a3 Fix typo in SignatureAlgorithm error message. (#295)
## Summary
- Fixed typo in `SignatureAlgorithm.swift:180`: "unsupprted" →
"unsupported"

  ## Details
The error message thrown when an unsupported signature algorithm value
is encountered contained a spelling error. This has been corrected.

  ## Test plan
  - Existing tests continue to pass
- The error message is only shown when an invalid algorithm is used, so
no new tests are needed
2026-04-17 19:59:50 +00:00
Rick Newton-Rogers 5aa1c0d1bc Drop Swift 6.0 (#294)
Motivation:

Swift 6.0 is no longer supported, we should bump the tools version and
remove it from our CI.

Modifications:

* Bump the Swift tools version to Swift 6.1
* Remove Swift 6.0 jobs where appropriate in main.yml, pull_request.yml

Result:

Code reflects our support window.
1.19.0
2026-04-08 15:08:50 +01:00
Rick Newton-Rogers 1f8592e508 Enable Swift 6.3 jobs in CI (#293)
Motivation:

Swift 6.3 has been released, we should add it to our CI coverage.

Modifications:

Add additional Swift 6.3 jobs where appropriate in main.yml,
pull_request.yml

Result:

Improved test coverage.
2026-04-01 13:53:28 +01:00
Mike Drob 9e7a00de2b Use org security policy instead of our bespoke version (#292) 2026-03-11 18:27:15 +00:00
Rick Newton-Rogers 2ea3d05c75 update actions/checkout from v4 to v6 (#291)
Motivation

* Following [GitHub's
announcement](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/),
Node 20 is being deprecated and runners will begin using Node 24 by
default starting March 4th, 2026. Node 20 will reach end-of-life in
April 2026.

Modifications

* Upgrade GitHub Actions to their latest versions to ensure
compatibility with Node 24.
* Replace `actions/checkout@v4` with `actions/checkout@v6` in all
workflow files.

Result

* Workflow files reference `actions/checkout@v6`.
2026-03-02 13:32:40 +00:00
Rick Newton-Rogers 0ad242d196 switch from main to 0.0.7 for swiftlang workflows (#290)
Motivation

* `@main` references to `swiftlang/github-workflows` are deprecated.

Modifications

* Replace `@main` with `@0.0.7` in all workflow files.

Result

* Workflow files reference a pinned version of
`swiftlang/github-workflows`.
2026-02-20 14:50:51 +00:00
Justin OrozandCory Benfield 24ccdeeeed Custom private key (#282)
## Motivation:

In some cases a developer may want to sign a certificate using a method
other than a private key. For example: if a private key is protected by
hardware which signs asynchronously.

## Modifications:

- Create `CustomPrivateKey` protocol
- Create `async` initializers for `Certificate` and
`CertificateSigningRequest`.
- `CustomPrivateKey` can now back a`Certificate.PrivateKey`
- Make `Certificate.Signature` initializer public

## Result:

Developers can now sign a certificate with greater flexibility.

## Alternatives Considered:

### Implementations

#### Pass the `CustomPrivateKey` into `Certificate` and
`CertificateSigningRequest` initializers directly.
There is concern this could add too much duplication of api.

### Various names for the protocol:
- `Certificate.PrivateKeyProtocol` and
`Certificate.AsyncPrivateKeyProtocol`
- `Certificate.Signer`/`Certificate.AsyncSigner`
- `Certificate.SignatureProvider`/`Certificate.AsyncSignatureProvider`

---------

Co-authored-by: Cory Benfield <cbenfield@apple.com>
1.18.0
2026-02-10 14:29:41 +00:00
Sergey Cheperis 7d5f6124c9 Pass additionalIntermediateCertificates through to signWithSigningTime (#289)
When `signingTime` was provided to `CMS.sign`, the
`additionalIntermediateCertificates`
parameter was not being forwarded to `signWithSigningTime`, causing
signature verification
to fail for certificates that require an intermediate CA chain.

Fixes #287
1.17.1
2026-01-05 15:43:18 +00:00
RaphaelandCory Benfield 133a347911 Add validation function for raw signatures (#284)
### Motivation

Signatures can be performed on any kind of data, e.g., to prove
ownership of the private key for a given certificate. This data usually
comes as a blob of bytes.

### Modification

Add a signature verification function that operates on bytes represented
by the `DataProtocol`. The bytes are converted to the signature type
matching the key and share an implementation with the verification
function for `Certificate.Signature`.

### Result

Easy validation of signatures represented as bytes.

---------

Co-authored-by: Cory Benfield <lukasa@apple.com>
1.17.0
2025-11-27 18:05:16 +00:00
George Barnett 48d7c83a47 Don't hold a lock over a continuation in Promise (#286)
Motivation:

The various 'withMumbleContinuation' APIs are supposed to be invoked
synchronously with the caller. This assumption allows a lock to be
acquired before the call and released from the body of the
'withMumbleContinuation' after e.g. storing the continuation. However
this isn't the case and the job may be re-enqueued on the executor
meaning that this is pattern is vulnerable to deadlocks.

Modifications:

- Drop and reacquire the lock in Promise
- Avoid resuming continuations while holding the lock

Result:

Lower chance of deadlock
2025-11-25 08:52:23 +00:00
aryan-25 66a8512c4e Drop Swift 5.10 (#283)
Motivation:

Swift 5.10 is no longer supported. We should raise the minimum Swift
tools version to 6.0, fix consequent build warnings/errors, and remove
5.10 CI jobs.

Modifications:
- Raised the Swift tools version to 6.0 in both the main
`swift-certificates` package and the Benchmark package.
- Removed the now redundant `StrictConcurrency=complete` flag in
`swift-certificates`' `Package.swift`.
- Removed 5.10 CI job arguments.
- Removed 5.10 benchmark thresholds.
- Added an explicit type annotation to the `package-benchmark` setup
closure to address a build error.
- Updated `VerifierBenchmark` to use newer, non-deprecated
`RFC5280Policy` initializers (as a result of #276).
- Updated a test case in `Tests/X509Tests/PEMTests.swift` to no longer
use a deprecated `String` initializer.

Result:

Code reflects our support window.
1.16.0
2025-11-18 14:55:30 +00:00
Raphael 23b6a15b5d Expose supported signature algorithms for private keys (#281)
### Motivation:

When loading a private key from disk as a `Certificate.PrivateKey` there
is no straight forward way to query the supported signature algorithms.
For signature algorithm negotiation, the raw values defined in RFC are
useful as well.

### Modifications:

Add a new property to query the supported signature algorithms for a
given key. Add a new property that translates a signature algorithm to
the respective value defined in RFC 8446.

### Results:

Working with certificate private keys and signature algorithms gets
easier.
2025-11-18 14:16:22 +00:00
George Barnett c399f90e7b Avoid ambiguity in tests (#280)
Motivation:

swift-crypto just added `derRepresentation` to
`Curve25519.Signing.PrivateKey`, however swift-certificates already
provides the same API internally but returning an array of bytes (as
opposed to Data). This causes ambiguity in the swift-certificates tests.

Modifications:

- Specify the type to disambiguate. We do this rather than using the new
API as swift-crypto has stricter availability requirements which we
don't need to impose on our tests.

Result:

No ambiguity
1.15.1
2025-10-23 16:28:17 +00:00
aryan-25 a8b8f71614 Fix LockStorage warning (#279)
### Motivation:
`LockStorage` has a redundant `@available(*, unavailable)` annotation
for `Sendable` conformance. Since `LockStorage` inherits from
`ManagedBuffer`, which is [already
non-Sendable](https://github.com/swiftlang/swift/blob/d7bb1fe25f4f50a08d9f6ec54768e08c90c17c9d/stdlib/public/core/ManagedBuffer.swift#L72),
this annotation is unnecessary and results in a warning.

### Modifications:
Removed the redundant non-Sendable annotation in `LockStorage`

### Result:
swift-certificates compiles warning-free
2025-10-20 11:11:31 +01:00
Melissa Kilby ecf8cee493 chore: restrict GitHub workflow permissions - future-proof (#278)
See https://github.com/swiftlang/github-workflows/issues/167 for
additional context

This approach aligns with security best practices, as detailed in the
following documentation:

-
https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions
-
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#defining-access-for-the-github_token-scopes
-
https://openssf.org/blog/2024/08/12/mitigating-attack-vectors-in-github-workflows/


The default GITHUB_TOKEN permissions are defined at the repository
level. This PR modifies the workflow-level overrides to conform to
OpenSSF best practices -> defense in depth.

Allow me to quote OpenSSF:

https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions

> The highest score is awarded when the permissions definitions in each
workflow's yaml file are set as read-only at the top level and the
required write permissions are declared at the run-level.”

> Remediation steps
> - Set top-level permissions as read-all or contents: read as described
in GitHub's documentation.
> - Set any required write permissions at the job-level. Only set the
permissions required for that job; do not set permissions: write-all at
the job level.


Compare to the LLVM project:

Top-level: contents read, e.g.
https://github.com/swiftlang/llvm-project/blob/next/.github/workflows/build-ci-container-windows.yml#L3-L4
-> this makes it future-proof

Job-level: Allow write permissions as needed, e.g.
https://github.com/swiftlang/llvm-project/blob/next/.github/workflows/build-ci-container-windows.yml#L53-L58

Signed-off-by: Melissa Kilby <mkilby@apple.com>
2025-10-20 08:50:08 +01:00
aryan-25 f4cd9e78a1 Update RFC5280Policy and OCSPVerifierPolicy initializers (#276)
### Motivation:
New initializers for `ExpiryPolicy`, `RFC5280Policy`, and
`OCSPVerifierPolicy` were introduced in #266. These initializers were
added to prevent users from specifying `Date.now` as the time to
validate certificate expiry against. For context, the problem was that
`Date.now` would be evaluated at initialization, but validation could
occur at a later stage, at which point the validation time would become
stale.

These initializers had a `fixedValidationTime: Date? = nil` argument,
where a non-`nil` value denoted a *fixed* time to validate against, and
a `nil` value denoted that the current time, evaluated at the point of
validation, would be used for validation (the common case). Although the
dangers of specifying `fixedValidationTime = .now` were documented, in
practice, it is very easy for users to miss this and continue using the
API in an incorrect way.

Given that most users will validate certificate expiry against the
current time, we want to default to this and remove the validation time
argument from the public initializers entirely. Users who want to
specify a fixed predetermined time **must explicitly opt-in** by using
`@_spi(FixedExpiryValidationTime)` to access the initializers that have
a *non-optional* `fixedExpiryValidationTime` argument.

### Modifications:
- Deprecated the initializers of `RFC5280Policy` and
`OCSPVerifierPolicy` and introduced two new initializers for each: one
without a validation time argument (common case), and one with a
*non-optional* validation time argument guarded behind an SPI
- Updated the initializers of `ExpiryPolicy` (an internal type)
- Additional changes:
  - Updated test cases to use new initializers
  - Updated examples in documentation to use new initializers

### Result:
`RFC5280Policy` and `OCSPVerifierPolicy` can be used more safely
1.15.0
2025-10-13 11:17:12 +01:00
Cory Benfield 80052da803 Allow the 4.0 series of Crypto releases (#275) 2025-10-06 17:16:25 +01:00
Rick Newton-Rogers a556ec262c Enable Swift 6.2 jobs in CI (#274)
Motivation:

Swift 6.2 has been released, we should add it to our CI coverage.

Modifications:

Add additional Swift 6.2 jobs where appropriate in main.yml,
pull_request.yml

Result:

Improved test coverage.
2025-09-22 13:37:43 +00:00
Raphael 4b092f1516 Introduce a validated certificate chain type (#272)
### Motivation:

The certificate chain returned by validation has properties that are
currently not expressed in the API. Introducing a type that does so
allows other APIs to build on these properties.

### Modifications:

* Add a new `ValidatedCertificateChain` type and use it as a result type
for certificate validation. Since a validated chain always has at least
a leaf and a root, the type gives direct access to them.
* Deprecate the previous validate function and introduce a replacement.
Update use of the now-deprecated API and duplicate tests to include both
APIs.

### Result:

Certificate validation returns a type that conceptually holds meaning.
1.14.0
2025-09-12 12:49:58 +01:00
Cory Benfield 20c451f1ad Require VerifierPolicy not have isolated conformance (#269)
Motivation

While conceptually it is possible for verifier policies to have isolated
conformance, in practice the way PolicyBuilder is implemented makes that
nearly impossible. Given that the utility of an isolated VerifierPolicy
is very limited, let's just disallow it.

Modifications

Require VerifierPolicy to have a SendableMetatype

Result

Easier to build correct compositions over PolicyBuilder
1.13.0
2025-08-28 10:32:31 +01:00
Rafael Cepeda c059d9c9d0 Explicit sendable changes (#265)
Performed the necessary changes to enable compiler flag
`-require-explicit-sendable`. Also enabled this flag in macOS CI.
1.12.0
2025-07-31 15:35:39 +01:00
Raphael 6911702e11 Enable release mode builds (#270)
### Motivation:

Some errors do not show up in debug builds. Enabling release mode builds
improves the CI coverage.

### Modifications:

Enable release mode builds for pull requests and scheduled builds on
main.

### Result:

Improved CI coverage.
2025-07-30 15:29:56 +00:00
Cory Benfield 0b5a9f2e84 Re-core the benchmarks (#271)
With the release of swift-crypto 3.13.3, our benchmark numbers should
have improved. Let's lock those in.
2025-07-30 15:14:23 +00:00
Gus Cairo 70297c3d42 Improve the performance of Certificate's equal and hash implementations (#267)
Right now, `Certificate` uses the default implementations of `hash` and
`==`, which are member-wise.

We can make this more efficient by only comparing the raw bytes for the
TBS certificate, the signature, and the signature's algorithm.
2025-07-18 15:07:07 +01:00
aryan-25 a78498b1c7 Use current time by default during validation in RFC5280Policy and OCSPPolicy (#266)
## Motivation:

The initializers of `RFC5280Policy` and `OCSPPolicy` require a
validation time as an argument. If this argument is set to `Date.now`,
the timestamp would be captured at the point of initialization. As such,
if the validation method is invoked on the policy instance long after
initialization, the timestamp can become stale at that point. This means
that the validation function could incorrectly determine a certificate
(`RFC5280Policy`) or an OCSP response (`OCSPPolicy`) to be valid, when
it has actually expired by the time the validation is performed.

This is not an issue in common use-cases where the policy is initialized
(with `validationTime` set to `.now`) inside a `PolicyBuilder` closure,
because the closure is evaluated at the point of validation. However,
some use-cases may initialize the policy independently; the issue can
potentially arise here.

## Modifications:

This patch deprecates the current initializers of `RFC5280Policy` and
`OCSPPolicy` to guide users toward using a safer initializer which
requires a `fixedValidationTime: Date?` argument:
- Passing `nil` (default) will lead to the current time being obtained
*at the point of validation*. This will prevent the bug described above.
- Passing a specific `Date` instance preserves the ability to validate
against a fixed point in time, i.e. a time in the past or future, but
*not* the current time.

## Result:

Users now have the option to use a safer initializer to construct
`RFC5280Policy` and `OCSPPolicy`.
2025-07-15 16:28:47 +01:00
Cory Benfield 870f4d5fe5 Skip errors relating to interaction not being allowed (#259) 1.11.0 2025-07-02 08:16:42 -07:00
Andreas Bauer e3c198a6d8 Support singing via Certificate PrivateKey (#257)
This PR introduces two key changes to improve flexibility when working
with signatures in swift-certificates. Previously, it was only possible
to verify signatures using `Certificate.PrivateKey`, but not to generate
them.

- The internal `sign(bytes:signatureAlgorithm:)` method on
`Certificate.PrivateKey` is now public, allowing users to generate
signatures directly.
- `Certificate.Signature` gains a new `rawRepresentation` property that
exposes the raw byte representation of a signature.
2025-07-01 08:18:58 -07:00
Alex Azarov 8bcf6a7242 Fix API documentation links in README.md (#258)
This PR removes `main` branch name from API docs URLs, making them
always point to the latest stable release instead of the main branch.

For most of developers this README.md is the main entry point when
installing the library, so pointing them to API docs for the latest
stable release makes more sense then the main branch which may contain
un-released API or breaking changes.
2025-06-30 06:56:43 -07:00
Brian Maher ba4aeba31a Custom certificate store (#256)
This change adds support for implementing a `CustomCertificateStore` in
a backwards compatible way with minimal impact to performance. A custom
certificate store can be implemented, and then the new
`CertificateStore(custom:)` constructor can be used so that the custom
certificate store can be used interchangeably with a "normal"
certificate store.

Additionally, a test case verifies that this new protocol will work for
our use case. More specifically, the use case we have is for
normalization of distinguished names so that an exact match of
distinguished names is no longer required. For example, if
`printableString` should be used interchangeably with a `utf8String`.

This pull request has two commits:
- One that adds support for a `CustomCertificateStore`
- One that modifies the implementation to support `async` lookup of
certificiates.

The second change is not required for our use-case, however I would
expect that there may be a future use-case that requires looking up
certificates in a database, and supporting an `async` protocol would be
valuable. Also, the `verify()` method is already async, so supporting an
`async` lookup does not disrupt any existing public APIs.
2025-06-26 11:06:10 +01:00
Evan Wilde 9d7ff7720e Fix pthread use on FreeBSD (#253)
Much like OpenBSD, the FreeBSD pthread APIs are not imported with the
appropriate nullability annotations, so the base pthread mutex type
should be an optional value. Eventually we should provide API notes to
fix this issue, but that is not in place today.
See https://github.com/swiftlang/swift/issues/81407
2025-05-21 12:54:15 +01:00
Evan Wilde b77cbe9d98 CMake: Use full module triples (#252)
Teach the CMake build to install swiftmodules using the full module
triple. This uses the compiler to determine the appropriate module
triple instead of attempting to compute the architecture in CMake
script, making the build more robust for new platforms and
architectures.

Also removing redundant policies. CMP0077 and CMP0091 were added before
the minimum CMake version and therefore will always be active in this
project.
2025-05-14 08:20:48 +01:00
LamTrinh.Dev 20cf09cc9d Correct macCatalyst 14 in CertificateTests.swift (#251)
Base on `macOS 11 and iOS 14 (iPadOS 14)`, I think the correct is
`macCatalyst 14` . Maybe it is a copy issue above available condition in
this file `@available(macOS 13.3, iOS 16.4, watchOS 9.4, tvOS 16.4,
macCatalyst 16.4, visionOS 1.0, *)` .
2025-05-06 10:39:20 +00:00
Rick Newton-Rogers e7db922740 Drop Swift 5.9 (#250)
Motivation:

Swift 5.9 is no longer supported, we should bump the tools version and
remove it from our CI.

Modifications:

* Bump the Swift tools version to Swift 5.10
* Remove Swift 5.9 jobs where appropriate in main.yml, pull_request.yml

Result:

Code reflects our support window.
2025-05-05 12:21:20 +01:00
Gus Cairo 999fd70c78 Add new Certificate.PrivateKey init from PKCS8 DER bytes (#248)
This PR adds a new `init(derBytes:)` to initialise a private key in
PKCS8 format from an array of DER bytes.
1.10.0
2025-04-25 17:15:42 +01:00