Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Main repository of the Tamarin prover for security protocol verification.
Haskell Python JavaScript CSS Makefile VimL Other


Fix link that changed inside the stack repository
latest commit 73d9bede0f
@rsasse rsasse authored
Failed to load latest commit information.
case-studies-regression Regression output changed due to modified heuristics
data Merge fix: GUI shows different options now
doc added explanation for L_ and F_ usage in manual
etc Make executable relocatable.
examples Added ARPKI example
images Added third screenshot and thumbnail. Also added production notes.
lib Added new command line option quit-on-warning that does as advertised…
misc Additional documentation on cleandot
src Added new command line option quit-on-warning that does as advertised…
.gitignore ignore .stack-work, removed cabal-related commands from Makefile and …
.hgignore rename tool directory to 'tamarin-prover'
.travis.yml cleanup of .travis.yml
AUTHORS added authors
CHANGES more documentation more documentation Update
LICENSE preparing for release
Makefile Cleaning up the Makefile added link to readme for improved graph output into initial readme
Setup.hs notes on better --version flag rename tool directory to 'tamarin-prover'
stack.yaml Set stack to use lts-2.22, thus GHC 7.8, as with 7.10 command line pr…
tamarin-prover.cabal fixed version number

The Tamarin prover repository

master branch build-status

This README describes the organization of the repository of the Tamarin prover for security protocol verification. Its intended audience are interested users and future developers of the Tamarin prover. For installation and usage instructions of the Tamarin prover see: installation instructions.

Developing and contributing

See contributing instructions.

Version Numbering Policy

We use version numbers with four components.

  • The first component is the major version number. It indicates complete rewrites of the codebase.
  • The second component is the minor version number. We use odd minor version numbers to denote development releases intended for early adopters. We use even minor version numbers to denote public releases, which are also published.
  • The third component indicates bugfix releases.
  • The fourth component indicates documentation and meta-data changes.

We ensure that the external interface of a version of the Tamarin prover is backwards compatible with the external interface of all versions that agree on the major and minor version number.

We announce all releases of the Tamarin prover on:


The manual is /doc/ It is part of every installation of the Tamarin prover.

Experimental improved graph output

You can use our experimental improved graph output which may be helpful for very large graphs that can be created for complicated protocols. To enable this feature read the instructions about improved graphs.

Example Protocol Models

All example protocol models are found in the directory


All models that we consider stable are part of every installation of the Tamarin prover. See tamarin-prover.cabal for the list of installed protocols. We use the following sub-directories to organize the models.

csf12/         the AKE case studies from our CSF'12 paper.
classic/       classic security protocols like the ones from
loops/         experiments for testing loop-invariants and protocols with
               non-monotonic state
related_work/  examples from related work on protocols with loops or
               non-monotonic state
experiments/   all other experiments
ake/           more AKE examples including ID-based and tripartite group KE
               protocols based on bilinear pairing
features/      (small) models that demonstrate a given feature
ccs15/         the observational equivalence case studies from our CCS'15 paper

Feel free to add more sub-directories and describe them here.

In general, we try use descriptive names for files containing the models. We also document all our findings as comments in the protocol model. Moreover, we use the following header in all files to make their context more explicit.

   Protocol:    Example
   Modeler:     Simon Meier, Benedikt Schmidt
   Date:        January 2012

   Status:      working

   Description of protocol.

Something went wrong with that request. Please try again.