List view
once [M1](https://github.com/a-sit-plus/signum/milestone/1) is done, we also need to * [ ] make sure that everything we can do in hardware, is actually done in hardware (#287) * [ ] re-evaluate the whole API for consistency * [ ] remove all deprecations * [ ] support arbitrary signature and encryption algorithms (bye, bye enums!). This may be affect other types of algorithms as well! * [ ] re-evaluate what functionality should be provided as core functionality and what should rather be extensions functions (similar to kotlinx.io, for example)
No due date•0/11 issues closedSupport every kind of operation expected from a full-blown crypto provider in decreasing order of priority: 1. [x] ASN.1 (low-level abstractions, parsing, encoding, construction, high-level encoding) in the crypto context (i.e. no ANS.1 REAL, etc.) 1. [x] Signing+Verifying * EC (NIST curves) * RSA (PKCS#1, PSS) 1. [x] HW-backed crypto on iOS + Android * Biometric Auth * Passphrase-based Auth * Attestation support 2. [x] Symmetric Encryption/Decryption * AES * ChaCha/Poly 3. [x] Key Agreement * ECDH 4. [ ] Asymmetric Encryption/Decryption * RSA 5. [x] Key Wrapping * AES key wrapping 6. [ ] KDF/KSF * [ ] HKDF * [ ] PBKDF2 * [ ] Scrypt 7. [x] MAC * HMAC-SHA1 * HMAC-SHA{256-512} This is not about supporting specific algorithms, paddings, etc, but to have all interfaces ready, with at least a single algorithm being usable across all targets
No due date•9/11 issues closed