2e9df1c0b9
Previous test refactor wrapped both keys in their respective DER envelopes. CI surfaced the asymmetry: jsonwebtoken's two from_ed_der constructors expect different inputs. - EncodingKey::from_ed_der → PKCS#8 v1 wrapped (ring's Ed25519KeyPair::from_pkcs8 path). The 16-byte prefix + 32-byte seed blob is correct. - DecodingKey::from_ed_der → raw 32-byte public key. Internally it becomes ring's UnparsedPublicKey::new(&ED25519, key_bytes), which takes the bare bytes, NOT a SubjectPublicKeyInfo wrapper. The test was building an SPKI DER for the public key, so verification saw a malformed key and failed every signature with InvalidSignature (`accepts_well_formed_base_license` and `activation_token_matches_machine`). Drop the SPKI helper, pass `signing_key.verifying_key().to_bytes()` straight into DecodingKey::from_ed_der. Inline doc-comment captures the asymmetry so the next person doesn't fall in the same hole. |
||
|---|---|---|
| .. | ||
| capabilities | ||
| icons | ||
| src | ||
| .gitignore | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| tauri.conf.json | ||