Add Sensible APIs to support removing BoringSSL from the rest of the ecosystem
Open
- Dominant language
- Assembly
- Stars
- 1.7k
- Forks
- 223
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Related issue https://github.com/apple/swift-nio-ssl/issues/382
APIs:
- [ ] Encrypted keys (#264)
- [ ] PKCS#12 support
- [ ] PBKDF2 support (#98)
- [ ] RSA initialisers from ASN.1 (https://github.com/apple/swift-crypto/issues/269)
- [ ] Related https://github.com/apple/swift-nio-ssl/issues/484
Contributor guide
Research direction
Start by reading the related swift-nio-ssl issue and the linked swift-crypto issues for the intended scope. Review the API checklist for encrypted keys, PKCS#12, PBKDF2, and RSA initialisers from ASN.1; done means the required APIs support removing BoringSSL from the wider ecosystem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- cryptography
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100