ecc_is_pubkey_valid_partial(9)

💅 ecc_is_pubkey_valid_partial — like, the partial public key validation era

okay so bestie, welcome to the ecc_is_pubkey_valid_partial(9) page — that's the function name, and you found it in the Kernel API Manual, which is exactly where it lives ✨

---

✨ NAME ✨

ecc_is_pubkey_valid_partial — Partial public key validation. that's it, that's the whole vibe check 🎀

---

🦋 SYNOPSIS 🦋

int ecc_is_pubkey_valid_partial (const struct ecc_curve *curve , struct
ecc_point *pk );

literally just two args and it returns an int, no cap 💅

---

🌸 ARGUMENTS 🌸

• curve — elliptic curve domain parameters. yes, THE curve. the main character of the whole elliptic situation 🌈
• pk — public key as a point. it's giving "coordinates, but make it a struct" 💖

---

👑 DESCRIPTION 👑

so what does it actually do? it validates the public key according to SP800-56A section 5.6.2.3.4, the ECC Partial Public-Key Validation Routine 🧚

like, it's the routine from the spec, doing the routine things from the spec. periodt ⭐

---

💀 NOTE 💀

okay bestie, important: there is no check that the public key is in the correct elliptic curve subgroup. so don't come for this function when it doesn't catch that — it literally says right here that it doesn't 🙈

like, this is the partial validation. the name is not a decoration, iykyk 💅

---

🔥 RETURN 🔥

• 0 — if validation is successful. slay, we love a zero 🌸
• -EINVAL — if validation is failed. it's giving "nope, try again" 😭

---

💜 SEE ALSO 💜

kernel file ./include/crypto/internal/ecc.h, plus the whole friend group:

• ecc_swap_digits(9)
• ecc_digits_from_bytes(9)
• ecc_is_key_valid(9)
• ecc_gen_privkey(9)
• ecc_make_pub_key(9)
• crypto_ecdh_shared_secret(9)
• ecc_is_pubkey_valid_full(9)
• vli_is_zero(9)
• vli_cmp(9)
• vli_sub(9)
• vli_from_be64(9)
• vli_from_le64(9)
• vli_mod_inv(9)
• vli_mod_mult_slow(9)
• vli_num_bits(9)
• ecc_alloc_point(9)
• ecc_free_point(9)
• ecc_point_is_zero(9)
• ecc_point_mult_shamir(9)

---

and that's the page, bestie 🫶 this little icon dropped from ./include/crypto/internal — yes that's the source path — and it's dated October 2026, so it's freshhh. go validate those public keys (partially!) 💖✨