mlsanityData to 14 Oct 2026

The Efficient Server Audit Problem, Deduplicated Re-execution, and the Web

arXiv 1709.08501 ↗First posted 25 Sep 2017cs.CR cs.DCcited by 2

Not on the map. Why?

Abstract (arXiv)

You put a program on a concurrent server, but you don't trust the server; later, you get a trace of the actual requests that the server received from its clients and the responses that it delivered. You separately get logs from the server; these are untrusted. How can you use the logs to efficiently _verify_ that the responses were derived from running the program on the requests? This is the _Efficient Server Audit Problem_, and it abstracts real-world scenarios, including running a web application on an untrusted provider. We give a solution based on several new techniques, including simultaneous replay and efficient verification of concurrent executions. We implement the solution for PHP web applications. For several applications, our verifier achieves 5.6--10.9x speedup versus simply re-executing, with less than 10 percent overhead for the server.

Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). First posted on arXiv 25 Sep 2017.

Builds on

No reference list yet.

Built on by

Cited by year

Citing papers per year: 2021: 1; 2022: 0; 2023: 1.

2 papers.