← Latest papers
💻 computer science

Plausible Deniability in Fully Homomorphic Computation

This paper introduces PD-FHC, a framework for plausible deniability in fully homomorphic computation that utilizes a single Fredkin-gate wiring on RGB images to simultaneously execute a real Boolean circuit and multiple decoys, thereby allowing users to outsource computations to untrusted clouds while maintaining information-theoretic position privacy and the ability to reveal a verifiable decoy under coercion.

Original authors: Shahzad Ahmad, Stefan Rass, Zahra Seyedi

Published 2026-07-13
📖 7 min read🧠 Deep dive

Original authors: Shahzad Ahmad, Stefan Rass, Zahra Seyedi

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a photo lab technician who needs to perform a secret, private calculation on a batch of images. Maybe you need to check if a specific measurement in a photo is higher than a certain limit. But there's a catch: you have to send these photos to a cloud computer you don't fully trust.

Usually, if you want to keep your data secret, you use Fully Homomorphic Encryption (FHE). Think of this as putting your photos in an unbreakable, glowing glass box. The cloud can still do math on the box, but it can't see inside. The problem? The glowing box is a dead giveaway. If a bossy, coercive adversary (like a government agent or a strict boss) demands to know what you're doing, they can point at the glowing box and say, "You're definitely doing secret math! Hand over the key!" You can't deny it because the box itself screams "Secret!"

This paper introduces a clever new trick called PD-FHC (Plausible Deniability in Fully Homomorphic Computation). Instead of a glowing box, imagine you are hiding your secret math inside a massive, ordinary-looking image filter.

The Magic Trick: One Wiring, Many Stories

Here is how the magic works, using a playful analogy:

Imagine you have a giant grid of 12,000 tiny light switches (these are the pixels in an image). You want to perform a secret calculation using a specific pattern of switches (your "real" circuit). But you also want to be able to tell a different story if someone forces you to explain what you did.

The authors use a special type of switch called a Fredkin gate. Think of a Fredkin gate as a magical traffic cop for three lanes of data. It has a control bit (a little flag) that decides what it does:

  • If the flag is down, it lets the cars pass straight through.
  • If the flag is up, it swaps the cars in the two side lanes.

Now, here is the genius part: The cloud provider only sees the traffic cop's instructions (the wiring), not the flags.

  1. The Setup: You take your secret calculation and turn it into a specific pattern of flags. You also invent several "decoy" calculations (like checking image brightness or color balance) and turn those into different patterns of flags.
  2. The Embedding: You hide the flags for your secret calculation in a few specific light switches. You hide the flags for your decoy calculations in other switches. For every single remaining switch in the image, you fill it with random noise.
  3. The Cloud's Job: You send the image to the cloud. You tell them, "Please run this specific traffic cop pattern on every single switch in the image." The cloud doesn't know which switches hold your secret, which hold a decoy, and which are just random noise. They just apply the same rule to everyone, all at once.
  4. The Result: Because the flags (control bits) are different for each group of switches, the traffic cop ends up doing your secret math on the secret switches, a decoy math on the decoy switches, and random noise math on the rest.

The "Plausible Deniability" Moment

Now, imagine the coercive adversary shows up. "What were you calculating?" they demand.

You can't say, "I did secret math," because that's the truth. But you can say, "Oh, I was just running a brightness check on these specific pixels!" You point to one of your decoy circuits.

The adversary checks the math. They see the flags you hid, they see the result, and they verify that the math works perfectly. They have no way of knowing that this was just a decoy. The "real" secret calculation is still hidden among the random noise and the other decoys, looking exactly like the rest of the image.

What This Paper Proves (and What It Doesn't)

The authors are very careful about what they claim to have solved and what is still a mystery.

What is Proven:

  • The "Position" Secret: If you fill your image with random noise that matches the statistical pattern of your secret data, the cloud provider cannot tell where your secret switches are. It's like trying to find a specific grain of sand on a beach when every grain looks exactly the same. The paper proves that under these specific conditions, the cloud's chance of guessing the right spot is no better than random guessing.
  • The "Existence" Secret: If you are forced to reveal some of your circuits, you can reveal the decoys. The paper proves that the adversary cannot prove that more circuits exist beyond the ones you revealed. It's like a magician showing you a few empty pockets; you can't prove there isn't a hidden pocket you didn't show them.

What is Ruled Out or Not Solved:

  • No "Invisible" Math: The paper explicitly states that this does not hide the fact that a computation is happening. The cloud knows a calculation is running because they are doing it. The magic is only in hiding which calculation it is and where the secret data is.
  • No "Magic" Obfuscation: The authors reject the idea of using complex cryptographic tricks to hide the structure of the circuit (the wiring). They admit that the wiring is visible to the cloud. The only thing hidden is the meaning of the gates, which comes from the hidden flags.
  • No "Perfect" Cover for Any Image: You cannot just take a random holiday photo and hide your secret in it. The paper argues that if the photo's natural "noise" doesn't match the random noise you add, a smart detector might spot the difference. You need to use a cover story that expects high randomness (like a dithering service or a noise-injection tool). If you try to hide your secret in a normal photo, you might get caught.

How Sure Are They?

The authors are very confident in their math but honest about the limits.

  • The Math: They have proven that if you follow their rules (matching the random noise perfectly), the cloud's advantage in finding your secret is exactly zero. This isn't a guess; it's a mathematical certainty based on the properties of the Fredkin gate.
  • The Real World: They ran simulations (computer tests) with images ranging from 128x128 pixels up to 512x512 pixels and circuits with 5 to 302 gates. These tests showed that the system works fast enough to be practical, competing with existing encryption tools.
  • The Weak Spot: The only thing they don't have a hard proof for is the "semantic" part. Can you always invent a decoy story that sounds believable? For example, if you claim you were checking "image brightness," does the math actually look like a brightness check? The paper admits this requires human creativity and domain knowledge. It's a "plausible" story, but the paper doesn't prove you can automate it perfectly.

The Bottom Line

This paper offers a way to outsource secret math to the cloud without leaving a glowing "I'm doing secrets!" sign. It turns your secret calculation into a needle in a haystack, where the haystack is filled with other needles that look exactly the same. If someone forces you to show a needle, you can show them a fake one that passes every test.

It's not a magic shield that makes the math invisible, and it doesn't work if you try to hide it in the wrong kind of picture. But for the right setup, it gives you a powerful new superpower: the ability to say, "I was just doing this boring thing," and have the math prove you right.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →