Demo Data from SIGIR 2026 / reviewers in the wild / expert
Mukesh Tiwari
dblp:02/8036
· DBLP profile ↗
4ranked-venue papers
0as first author
2since 2021 · last 2023
0000-0001-5373-9659ORCID · verified
Domains — the database's venue-derived domains; a paper can count in several
Security and privacy · 3 · 2 since 2021Theory of computation · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
2 papers |
Program verification · 86% Software maintenance and evolution · 14% | |
| Network and information security
3 papers |
Cryptographic protocols and secure computation · 100% | |
| Theoretical computer science
1 paper |
Automated reasoning and model checking · 100% |
Topics — the 10 heaviest of 10, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Cryptographic protocols and secure computation
machine-checked proofs |
0.7 | 1 | 2023 | Machine-checking Multi-Round Proofs of Shuffle: Terelius-Wikstrom and Bayer-Groth · USENIX Security Symposium 2023 |
Cryptographic protocols and secure computation
verifiable shuffle |
0.7 | 1 | 2023 | Machine-checking Multi-Round Proofs of Shuffle: Terelius-Wikstrom and Bayer-Groth · USENIX Security Symposium 2023 |
Program verification
concurrent program verification |
0.7 | 1 | 2023 | Assume but Verify: Deductive Verification of Leaked Information in Concurrent Applications · CCS 2023 |
Program verification
deductive verification |
0.7 | 1 | 2023 | Assume but Verify: Deductive Verification of Leaked Information in Concurrent Applications · CCS 2023 |
Program verification › security property verification
information flow verification |
0.7 | 1 | 2023 | Assume but Verify: Deductive Verification of Leaked Information in Concurrent Applications · CCS 2023 |
Cryptographic protocols and secure computation › electronic voting
verifiable voting |
0.4 | 1 | 2019 | Verified Verifiers for Verifying Elections · CCS 2019 |
Software maintenance and evolution › reverse engineering
code extraction |
0.4 | 1 | 2019 | Verified Verifiers for Verifying Elections · CCS 2019 |
Program verification › formal proof
mechanized proof |
0.4 | 1 | 2019 | Verified Verifiers for Verifying Elections · CCS 2019 |
Automated reasoning and model checking › theorem proving
proof checking |
0.2 | 1 | 2023 | Machine-checking Multi-Round Proofs of Shuffle: Terelius-Wikstrom and Bayer-Groth · USENIX Security Symposium 2023 |
Cryptographic protocols and secure computation
electronic voting |
0.1 | 1 | 2019 | Verified Verifiers for Verifying Elections · CCS 2019 |
Methods — techniques the papers use, named apart from their topics
proof assistant · 1.3formal verification · 1.3auto-active program verifier · 1.3assume annotations · 1.3SecCSL · 1.3machine-checked proof · 0.8code extraction · 0.8
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2023 | Assume but Verify: Deductive Verification of Leaked Information in Concurrent ApplicationsabstractWe consider the problem of specifying and proving the security of non-trivial, concurrent programs that intentionally leak information. We present a method that decomposes the problem into (a) proving that the program only leaks information it has declassified via assume annotations already widely used in deductive program verification; and (b) auditing the declassifications against a declarative security policy. We show how condition (a) can be enforced by an extension of the existing program logic SecCSL, and how (b) can be checked by proving a set of simple entailments. Part of the challenge is to define respective semantic soundness criteria and to formally connect these to the logic rules and policy audit. We support our methodology in an auto-active program verifier, which we apply to verify the implementations of various case study programs against a range of declassification policies. Toby C. Murray, Mukesh Tiwari, Gidon Ernst, David A. Naumann |
CCS | 2 |
| 2023 | Machine-checking Multi-Round Proofs of Shuffle: Terelius-Wikstrom and Bayer-Groth
Thomas Haines, Rajeev Goré, Mukesh Tiwari |
USENIX Security Symposium | 3 |
| 2019 | Verified Verifiers for Verifying ElectionsabstractThe security and trustworthiness of elections is critical to democracy; alas, securing elections is notoriously hard. Powerful cryptographic techniques for verifying the integrity of electronic voting have been developed and are in increasingly common use. The claimed security guarantees of most of these techniques have been formally proved. However, implementing the cryptographic verifiers which utilize these techniques is a technical and error prone process, and often leads to critical errors appearing in the gap between the implementation and the formally verified design. We significantly reduce the gap between theory and practice by using machine checked proofs coupled with code extraction to produce cryptographic verifiers that are themselves formally verified. We demonstrate the feasibility of our technique by producing a formally verified verifier which we use to check the 2018 International Association for Cryptologic Research (IACR) directors election. Thomas Haines, Rajeev Goré, Mukesh Tiwari |
CCS | 3 |
| 2017 | Schulze Voting as Evidence Carrying Computation
Dirk Pattinson, Mukesh Tiwari |
ITP | 2 |