# Attacks on verification keys

As discussed in the [verification key generation](/inferix-whitepaper/implementation/verification-key-generation.md), colluding attackers may know a set of used keys, then use these keys to predict the next keys (this is called *random number generator attack* [\[20\]](/inferix-whitepaper/references.md#20)). Furthermore, a large enough set of *workers* may also temporarily saturate the rendering task assignment mechanism of the *manager* to control which nodes will be assigned\cite{Lian2007}. These nodes already know the verification keys used for the assigned tasks, then they generate straightforwardly forged images which validate the noise verification. In short, once the verification key generation is predictable, the noise verification will be compromised.

This attack is mitigated due the [cryptographic hash property](/inferix-whitepaper/implementation/verification-key-generation.md) of $$K\_{\mathtt{verif}}$$: knowledge about generated keys does not leak any information about the next keys.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.inferix.io/inferix-whitepaper/implementation/threat-analysis/attacks-on-verification-keys.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.