Demo Data from EDBT 2026 / reviewers in the wild / expert
Thanasis Typaldos
dblp:351/6741
· DBLP profile ↗
1ranked-venue papers
0as first author
1since 2021 · last 2023
0009-0003-1054-4853ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 since 2021
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.
| Network and information security
1 paper |
Network security · 50% Cryptographic protocols and secure computation · 50% | |
| Computer networks
1 paper |
Internet of things and sensor networks · 100% |
Topics — the 4 heaviest of 5, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Cryptographic protocols and secure computation › key exchange
EDHOC |
0.7 | 1 | 2023 | EDHOC-Fuzzer: An EDHOC Protocol State Fuzzer · ISSTA 2023 |
Cryptographic protocols and secure computation
key exchange |
0.7 | 1 | 2023 | EDHOC-Fuzzer: An EDHOC Protocol State Fuzzer · ISSTA 2023 |
Network security
protocol security |
0.7 | 1 | 2023 | EDHOC-Fuzzer: An EDHOC Protocol State Fuzzer · ISSTA 2023 |
Network security
protocol state fuzzing |
0.7 | 1 | 2023 | EDHOC-Fuzzer: An EDHOC Protocol State Fuzzer · ISSTA 2023 |
Methods — techniques the papers use, named apart from their topics
model-based testing · 1.3model learning · 1.3
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2023 | EDHOC-Fuzzer: An EDHOC Protocol State FuzzerabstractEDHOC is a compact and lightweight authenticated key exchange protocol proposed by the IETF, whose design focuses on small message sizes, in order to be suitable for constrained IoT communication technologies. In this tool paper, we overview EDHOC-Fuzzer, a protocol state fuzzer for implementations of EDHOC clients and servers. It employs model learning to generate a state machine model of an EDHOC implementation, capturing its input/output behavior. This model can then be used for model-based testing, for fingerprinting, or can be analyzed for non-conformances, state machine bugs and security vulnerabilities. We overview the architecture and use of EDHOC-Fuzzer, and present some examples of models produced by the tool and our current findings. Konstantinos Sagonas, Thanasis Typaldos |
ISSTA | 2 |