Identity Based Cryptography for Certificate Free Security

You are reading version 1 of this direction, frozen 2026-10-04. The latest version is version 2.

Version 1 of 281 papers113 conceptsfrozen 2026-10-04

In traditional public key infrastructure (PKI), trust is a heavy commodity. To send an encrypted message, you don't just need the recipient's public key; you need a digital certificate—a signed document from a Certificate Authority (CA) proving that the key actually belongs to them. This "certificate tax" creates significant administrative overhead, requiring complex storage, transmission of certificate chains, and the constant maintenance of Revocation Lists.

Identity-Based Cryptography (IBC) fundamentally reimagines this process by turning a user's unique identifier—such as an email address, IP address, or SIP URI—directly into their public key. As Hongwei Li and colleagues demonstrate in Identity-Based Cryptography for Cloud Security, this shift can slash communication overhead by 70% and client-side computation by over 80% by eliminating the need to transmit and verify certificate chains.

The Intuition: Identity as a Mathematical Coordinate

The core mechanism of IBC relies on a trusted third party called a Private Key Generator (PKG). Instead of generating a random pair of keys and asking a CA to certify them, the system works in reverse:

  1. Public Key Derivation: Anyone can compute a recipient's public key using only the recipient's identity string (e.g., [email protected]) and the PKG’s public system parameters. Mathematically, the identity string is mapped to a point on an elliptic curve.
  2. Private Key Extraction: The recipient authenticates themselves to the PKG, which uses a master secret key to generate the corresponding private key for that specific identity string.

This allows for "spontaneous" secure communication. As Giuseppe Ateniese and Breno de Medeiros explain in Identity-based Chameleon Hash and Applications, a sender can encrypt a message for a recipient who hasn't even registered with the system yet. The recipient only needs to fetch their private key when they are ready to decrypt.

Streamlining the Handshake

The primary advantage of IBC is the removal of the "lookup" phase in secure protocols. In a standard SSL/TLS handshake, the server must send its certificate to the client, and the client must verify it against a root CA. Xian-Zhu Li proposes in An Improved TLS handshake protocol that if a server's identity (like its IP) is known, the client can independently calculate the server's public key. This bypasses the transmission of proof, accelerating the authentication handshake by over 40%.

This efficiency is critical for resource-constrained environments:

Solving the Key Escrow Problem

A major philosophical hurdle for IBC is "key escrow": because the PKG generates the private keys, it technically has the power to decrypt any message or forge any signature. To counter this, researchers like Dawei Zhao and Shudong Li advocate for Self-Certified Public Keys.

In An efficient dynamic ID based remote user authentication scheme using self-certified public keys for multi-server environment, they describe a system where a user's public key is computed from their identity and a signature from a trusted authority. This hybrid approach, also explored by Giuseppe Ateniese in Certified Bitcoins, ensures that the public key is implicitly verifiable (no certificate needed) while preventing the central authority from knowing the user's actual private key.

Scaling to Modern Architectures

As we move toward decentralized and quantum-resistant systems, IBC is evolving. In the realm of blockchain, Zijian Bao and colleagues introduced An Identity-Based Adaptor Signature Scheme, which allows users to execute off-chain conditional logic (like atomic swaps) using human-readable identifiers instead of raw cryptographic hashes.

Furthermore, to prepare for the "cryptographic apocalypse" of quantum computing, researchers are shifting from bilinear pairings to lattice-based math. Guanglu Wei and others proposed LA-AKA, a lattice-based protocol that allows IoT devices to agree on encryption keys in just two rounds of communication using only their device identifiers, providing a post-quantum future that remains certificate-free.

Papers in this version

Showing 60 of 81 papers.

History & citationVersion 2 · 2026-10-04

Current · Permanent link

  1. Version 2 (latest) · 2026-10-04 · 86 papers
  2. Version 1 · 2026-10-04 · 81 papers
Cite this direction

Latest version (a living page):

@misc{lacuna_identity_based_cryptography_623d7675,
  title = {identity-based cryptography},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/identity-based-cryptography/rdr_623d7675e44e44bcbe29805fe2f37c9e},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-19},
}

This exact version (version 1, frozen text):

@misc{lacuna_identity_based_cryptography_for_certific_623d7675_v1,
  title = {Identity Based Cryptography for Certificate Free Security},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/identity-based-cryptography-for-certificate-free-security/rdr_623d7675e44e44bcbe29805fe2f37c9e/v/1},
  note = {Version 1, frozen 2026-10-04. Accessed 2026-11-19},
}