Cannot Find KDF in SASLAuthentication+SCRAM-SHA256

[felswa]

Describe the issue

Hi. Following to change on 14 Oct the private func Hi doesn't compile because it cannot find KDF.

Vapor version

4.117.0

Operating system and version

MacOS 26.0.01

Swift version

SPM - 6.0

Steps to reproduce

private func Hi(string: [UInt8], salt: [UInt8], iterations: UInt32) throws -> SymmetricKey {
try KDF.Insecure.PBKDF2.deriveKey(
from: string,
salt: salt,
using: .sha256,
outputByteCount: 32,
unsafeUncheckedRounds: Int(iterations)
)
}

Outcome

Unable to build project

Additional notes

[gwynne]

I cannot reproduce this failure. Most likely SwiftPM is getting a little confused by swift-crypto's versioning. I suggest removing .build and Package.resolved, running swift package purge-cache, and trying again.

[felswa]

Thank you. I am working in XCode and have tried removing Package.resolved and Reset Package Cache but that does not seem to fix the issue. I have also tried this

rm -rf ~/Library/org.swift.swiftpm
rm -rf ~/Library/Caches/org.swift.swiftpm

to reset the Package cache.

[gwynne]

KDF has been available in swift-crypto since version 3.9.0, which was released around this time last year. Can you verify what version of it SwiftPM is using for your package? You can find it from the commandline with:

# Extract from Package.resolved
jq -r '.pins[]|select(.identity=="swift-crypto").state.version' Package.resolved

or

# Extract from swift package show-dependencies
swift package show-dependencies --format=json | jq -r 'first(recurse(.dependencies[])|select(.name=="swift-crypto")).version'

or, a bit more simply,

# Just grep the human-readable output
swift package show-dependencies | grep swift-crypto

[fabianfett]

@gwynne we should likely just ship a tiny release with #592.

[fabianfett]

Released as 1.29.0

[gwynne]

@fabianfett I don't think that would cause this issue without also causing package resolution failures. Xcode was being recalcitrant about showing me those errors at one point, but swift package resolve popped up the issue immediately.