🆕⚛️🔐 Starting with iOS 26, CryptoKit gets support for quantum-secure cryptography with algorithms such as ML-KEM, ML-DSA and HPKE with X-Wing:
developer.apple.com/documentatio...
developer.apple.com/documentatio...
Apple CryptoKit | Apple Developer Documentation
Perform cryptographic operations securely and efficiently.
developer.apple.com
June 9, 2025 at 7:29 PM
🆕⚛️🔐 Starting with iOS 26, CryptoKit gets support for quantum-secure cryptography with algorithms such as ML-KEM, ML-DSA and HPKE with X-Wing:
developer.apple.com/documentatio...
developer.apple.com/documentatio...
Updates to swift-crypto that offer an expanded cross-platform feature set for apps relying on cryptography: github.com/apple/swift-...
Release 5.0.0 · apple/swift-crypto
Swift Crypto 5.0 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 ...
github.com
September 17, 2026 at 4:32 PM
Updates to swift-crypto that offer an expanded cross-platform feature set for apps relying on cryptography: github.com/apple/swift-...
Apple didn't ship X-Wing in CryptoKit willy-nilly
July 3, 2026 at 1:42 PM
Apple didn't ship X-Wing in CryptoKit willy-nilly
#apps #mac #macOS #remotecontrol #vnc
RemoteSupervisor 1.2 is now available for Mac and iPad, the new way to monitor your computers and servers. Built in Swift and powered by the modern NRSP protocol, it ensures end-to-end encryption through Apple’s CryptoKit framework.
www.elonovo.com
RemoteSupervisor 1.2 is now available for Mac and iPad, the new way to monitor your computers and servers. Built in Swift and powered by the modern NRSP protocol, it ensures end-to-end encryption through Apple’s CryptoKit framework.
www.elonovo.com
October 28, 2025 at 3:27 PM
#apps #mac #macOS #remotecontrol #vnc
RemoteSupervisor 1.2 is now available for Mac and iPad, the new way to monitor your computers and servers. Built in Swift and powered by the modern NRSP protocol, it ensures end-to-end encryption through Apple’s CryptoKit framework.
www.elonovo.com
RemoteSupervisor 1.2 is now available for Mac and iPad, the new way to monitor your computers and servers. Built in Swift and powered by the modern NRSP protocol, it ensures end-to-end encryption through Apple’s CryptoKit framework.
www.elonovo.com
I'm starting to see a lot of specs using ML-DSA-44 (which is fine!) but I would really like it if Apple's CryptoKit implemented ML-DSA-44 instead of just -65 and -87.
June 30, 2026 at 7:17 PM
I'm starting to see a lot of specs using ML-DSA-44 (which is fine!) but I would really like it if Apple's CryptoKit implemented ML-DSA-44 instead of just -65 and -87.
- CryptoKit: fancy swift _read vs get property access
anyone know what this does?
anyone know what this does?
September 16, 2026 at 8:30 PM
- CryptoKit: fancy swift _read vs get property access
anyone know what this does?
anyone know what this does?
let's see if there are any framework changes in the latest 27 beta from yesterday, I have to imagine it's mostly fixes at this point #wwdc
- CryptoKit: removed the recently-added insecure UnauthenticatedAES and UnauthenticatedChaCha20
- CryptoKit: removed the recently-added insecure UnauthenticatedAES and UnauthenticatedChaCha20
August 25, 2026 at 12:44 PM
let's see if there are any framework changes in the latest 27 beta from yesterday, I have to imagine it's mostly fixes at this point #wwdc
- CryptoKit: removed the recently-added insecure UnauthenticatedAES and UnauthenticatedChaCha20
- CryptoKit: removed the recently-added insecure UnauthenticatedAES and UnauthenticatedChaCha20
This is a hugely important update for CryptoKit - make sure you check out the session to learn more about what you do (and don’t) need to do as an App Developer to protect against quantum computers.
🆕⚛️🔐 Starting with iOS 26, CryptoKit gets support for quantum-secure cryptography with algorithms such as ML-KEM, ML-DSA and HPKE with X-Wing:
developer.apple.com/documentatio...
developer.apple.com/documentatio...
Apple CryptoKit | Apple Developer Documentation
Perform cryptographic operations securely and efficiently.
developer.apple.com
June 9, 2025 at 8:25 PM
This is a hugely important update for CryptoKit - make sure you check out the session to learn more about what you do (and don’t) need to do as an App Developer to protect against quantum computers.
Only one new thing in Apple's CryptoKit for Apple OS 27 so far: `KEMOneTimePrivateKey`.
> A one-time private key for a key encapsulation mechanism, which can only decapsulate once but it does so faster.
Interesting..
developer.apple.com/documentatio...
> A one-time private key for a key encapsulation mechanism, which can only decapsulate once but it does so faster.
Interesting..
developer.apple.com/documentatio...
KEMOneTimePrivateKey | Apple Developer Documentation
A one-time private key for a key encapsulation mechanism, which can only decapsulate once but it does so faster.
developer.apple.com
June 9, 2026 at 1:32 AM
Only one new thing in Apple's CryptoKit for Apple OS 27 so far: `KEMOneTimePrivateKey`.
> A one-time private key for a key encapsulation mechanism, which can only decapsulate once but it does so faster.
Interesting..
developer.apple.com/documentatio...
> A one-time private key for a key encapsulation mechanism, which can only decapsulate once but it does so faster.
Interesting..
developer.apple.com/documentatio...
Swift Crypto is still closely tied to CryptoKit as #Swift expands across servers, Windows, Android and embedded.
A new discussion asks if the ecosystem needs a crypto package that can evolve independently.
https://forums.swift.org/t/state-of-cryptography-in-swift/89649
#SwiftLang #ServerSideSwift
A new discussion asks if the ecosystem needs a crypto package that can evolve independently.
https://forums.swift.org/t/state-of-cryptography-in-swift/89649
#SwiftLang #ServerSideSwift
State of cryptography in Swift
Hi all, Nearly two years have passed since this post about Swift Crypto on all platforms. That post aimed to discuss the state of the main cryptography library used today in Swift, its interaction with its closed source counterpart, CryptoKit, and the future of using said library for the server world and all other platforms and ecosystems Swift supports, both present at the time and that have arisen in the meantime. The main pain points that post was trying to express, and to gather feedback ...
forums.swift.org
September 20, 2026 at 5:00 PM
Swift Crypto is still closely tied to CryptoKit as #Swift expands across servers, Windows, Android and embedded.
A new discussion asks if the ecosystem needs a crypto package that can evolve independently.
https://forums.swift.org/t/state-of-cryptography-in-swift/89649
#SwiftLang #ServerSideSwift
A new discussion asks if the ecosystem needs a crypto package that can evolve independently.
https://forums.swift.org/t/state-of-cryptography-in-swift/89649
#SwiftLang #ServerSideSwift
Public-key cryptography with CryptoKit for iOS
This article explains how to use CryptoKit for public-key cryptography in iOS apps to enhance security.
tanaschita.com/cryptokit-pu...
by Natascha Fadeeva
#ios #iosdevelopment #swift #cryptography #swiftlang
This article explains how to use CryptoKit for public-key cryptography in iOS apps to enhance security.
tanaschita.com/cryptokit-pu...
by Natascha Fadeeva
#ios #iosdevelopment #swift #cryptography #swiftlang
Public-key cryptography with CryptoKit for iOS
Learn how to implement public-key cryptography in iOS using CryptoKit. This guide covers encryption, digital signatures, and secure key exchange to protect sensitive data in our Swift apps.
tanaschita.com
March 31, 2025 at 4:27 AM
Public-key cryptography with CryptoKit for iOS
This article explains how to use CryptoKit for public-key cryptography in iOS apps to enhance security.
tanaschita.com/cryptokit-pu...
by Natascha Fadeeva
#ios #iosdevelopment #swift #cryptography #swiftlang
This article explains how to use CryptoKit for public-key cryptography in iOS apps to enhance security.
tanaschita.com/cryptokit-pu...
by Natascha Fadeeva
#ios #iosdevelopment #swift #cryptography #swiftlang
😔
"@preconcurrency" it is, then...
"@preconcurrency" it is, then...
March 7, 2025 at 4:00 AM
😔
"@preconcurrency" it is, then...
"@preconcurrency" it is, then...
What Claude got right:
Architecture — Supabase-direct, no custom API layer. iOS talks to the same backend as the web app.
Hard integrations — Apple Sign-In with CryptoKit nonce. StoreKit 2 with server-side verification. AVAudioSession for background playback.
These would've taken me weeks alone.
Architecture — Supabase-direct, no custom API layer. iOS talks to the same backend as the web app.
Hard integrations — Apple Sign-In with CryptoKit nonce. StoreKit 2 with server-side verification. AVAudioSession for background playback.
These would've taken me weeks alone.
February 21, 2026 at 1:36 AM
What Claude got right:
Architecture — Supabase-direct, no custom API layer. iOS talks to the same backend as the web app.
Hard integrations — Apple Sign-In with CryptoKit nonce. StoreKit 2 with server-side verification. AVAudioSession for background playback.
These would've taken me weeks alone.
Architecture — Supabase-direct, no custom API layer. iOS talks to the same backend as the web app.
Hard integrations — Apple Sign-In with CryptoKit nonce. StoreKit 2 with server-side verification. AVAudioSession for background playback.
These would've taken me weeks alone.
During all of the ML-KEM / ML-DSA excitement in CryptoKit I failed to realize that SHA-3 is in CryptoKit as well. No SHAKE as far as I can see, which leaves me a tad deflated, but progress!
June 11, 2025 at 2:35 AM
During all of the ML-KEM / ML-DSA excitement in CryptoKit I failed to realize that SHA-3 is in CryptoKit as well. No SHAKE as far as I can see, which leaves me a tad deflated, but progress!
Does anyone know how to generate a 16-byte challenge using CryptoKit? The default is 12.
Is generating two and then partially concatenating considered secure?
https://developer.apple.com/documentation/cryptokit/aes/gcm/nonce/init()
Is generating two and then partially concatenating considered secure?
https://developer.apple.com/documentation/cryptokit/aes/gcm/nonce/init()
November 16, 2024 at 2:40 PM
Does anyone know how to generate a 16-byte challenge using CryptoKit? The default is 12.
Is generating two and then partially concatenating considered secure?
https://developer.apple.com/documentation/cryptokit/aes/gcm/nonce/init()
Is generating two and then partially concatenating considered secure?
https://developer.apple.com/documentation/cryptokit/aes/gcm/nonce/init()
TIL CryptoKit (it's for cryptography, not cryptocurrencies) doesn’t natively add the prefix (compressed and uncompressed) to public keys.
March 13, 2025 at 5:38 AM
TIL CryptoKit (it's for cryptography, not cryptocurrencies) doesn’t natively add the prefix (compressed and uncompressed) to public keys.
Have you tried it with .NET 11? We introduced some interesting new CryptoKit things that maybe might make things a little more difficult. More symbols, at least.
July 11, 2026 at 6:00 PM
Have you tried it with .NET 11? We introduced some interesting new CryptoKit things that maybe might make things a little more difficult. More symbols, at least.
The day has finally come… I’ve added Swift to the Micro.blog for Mac project. Yes, I know it’s 2023, almost 2024. After tinkering with Apple’s Security framework and Common Crypto, decided CryptoKit was the way to go and it’s Swift-only.
December 13, 2023 at 2:45 PM
The day has finally come… I’ve added Swift to the Micro.blog for Mac project. Yes, I know it’s 2023, almost 2024. After tinkering with Apple’s Security framework and Common Crypto, decided CryptoKit was the way to go and it’s Swift-only.
No array copy. The benchmark is run on the Apple M4. Apple's CryptoKit SHA-256 on M-series Macs is special and outperforms other software implementations of SHA-256.
December 11, 2025 at 2:37 PM
No array copy. The benchmark is run on the Apple M4. Apple's CryptoKit SHA-256 on M-series Macs is special and outperforms other software implementations of SHA-256.
Many of you probably know about this trick, but for everyone else – You can set a default answer to the App Store Connect build encryption question when uploading your iOS, macOS and visionOS builds. Manually selecting "no" every time is not required. 👨🏻💻 #appledev
July 7, 2026 at 4:39 PM
Many of you probably know about this trick, but for everyone else – You can set a default answer to the App Store Connect build encryption question when uploading your iOS, macOS and visionOS builds. Manually selecting "no" every time is not required. 👨🏻💻 #appledev
Addition to the list: Apple CryptoKit developer.apple.com/documentatio...
isValidAuthenticationCode(_:authenticating:using:) | Apple Developer Documentation
Returns a Boolean value indicating whether the given message authentication code is valid for a block of data.
developer.apple.com
May 27, 2025 at 5:05 PM
Addition to the list: Apple CryptoKit developer.apple.com/documentatio...
CryptoKit works in-memory only and CommonCrypto doesn't support AES-GCM so to support large files I had to embed OpenSSL and the S3 Files binary grew by 5mb. 😿
January 31, 2025 at 4:31 PM
CryptoKit works in-memory only and CommonCrypto doesn't support AES-GCM so to support large files I had to embed OpenSSL and the S3 Files binary grew by 5mb. 😿
smart to keep CryptoKit for the hashing — no reason to roll your own there. the optional TSA approach is interesting, letting users bring their own timestamp authority keeps the trust model clean. offline verification is a big deal for evidence chains
March 6, 2026 at 11:35 PM
smart to keep CryptoKit for the hashing — no reason to roll your own there. the optional TSA approach is interesting, letting users bring their own timestamp authority keeps the trust model clean. offline verification is a big deal for evidence chains
Which is fine, but a surprising "CryptoKit API lets you do something the docs don't want you do".
What would be most useful is if `finalize` was documented as not "finalizing" but more like a `current`.
What would be most useful is if `finalize` was documented as not "finalizing" but more like a `current`.
October 23, 2025 at 1:46 AM
Which is fine, but a surprising "CryptoKit API lets you do something the docs don't want you do".
What would be most useful is if `finalize` was documented as not "finalizing" but more like a `current`.
What would be most useful is if `finalize` was documented as not "finalizing" but more like a `current`.
I suppose they were right when they said the package wasn’t completely stable, which is fair, but it’s the most updated package right now.
I hope CryptoKit won’t give me as much trouble…
I hope CryptoKit won’t give me as much trouble…
March 11, 2025 at 2:47 PM
I suppose they were right when they said the package wasn’t completely stable, which is fair, but it’s the most updated package right now.
I hope CryptoKit won’t give me as much trouble…
I hope CryptoKit won’t give me as much trouble…