andr3/scyther
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Scyther with my modifications
1,492 Commits 1 Branch 0 Tags 21 MiB
C 42.9%
Python 28.8%
TeX 14.1%
C++ 9.8%
Shell 1.2%
Other 3.1%
6c7493838c
Go to file
Cas Cremers 6c7493838c Implemented well-formedness check as in the 2012 book. 
We check that variables occur first in receive events.
2012-12-06 09:52:13 +01:00
design Removed huge file; unclear why this was in here anyway. 2010-05-11 10:58:38 +02:00
dist Fixed release scripts to work with new git conventions. 2008-09-10 11:20:50 +02:00
gui Added Wimax models from compositionality paper. 2012-11-27 21:56:05 +01:00
scripts Added loop script which I had always wanted before. 2008-08-21 21:55:55 +02:00
src Implemented well-formedness check as in the 2012 book. 2012-12-06 09:52:13 +01:00
testing Cleanup and restructuring of testing directory setup. 2012-11-15 16:47:08 +01:00
commit-template Added template for commits. 2011-04-06 10:50:43 +02:00
protocols Added softlink to protocols directory. 2012-11-15 13:41:02 +01:00
README.md Cleanup and restructuring of testing directory setup. 2012-11-15 16:47:08 +01:00

README.md

The Scyther tool repository

This README describes the organization of the repository of the Scyther tool for security protocol analysis. Its intended audience are interested users and future developers of the Scyther tool, as well as protocol modelers. For installation and usage instructions of the Scyther tool see: http://people.inf.ethz.ch/cremersc/scyther/index.html.

Developing

We use Linux during the development of Scyther, but development on Windows and MAC OS X should be equally feasible. Note that the below instructions are written from a Linux/Ubuntu perspective, and probably need modifications for other platforms.

Scyther is written partly in Python (for the GUI, using wxPython) and partly in C (for the backend).

In order to run the tool from a repository checkout, it is required to compile the C sources into a working binary for the backend. The simplest way to achieve this is to run the build.sh script in the ./src directory. This script compiles a binary version of the tool on the native platform. Thus, in the Linux case, it should produce ./src/scyther-linux. This file is automatically copied to the related directory under ./gui, and if successful you can attempt to run ./gui/scyther-gui.py to use the graphical user interface.

The build process depends on the following (Debian/Ubuntu) packages:

  • cmake
  • build-essential
  • flex
  • bison

If you are using Ubuntu, installing these may be as simple as running

sudo apt-get install cmake build-essential flex bison

In case you also want to be able to compile Windows binaries from Linux, you also need:

  • mingw32

Note that welcome all contributions, e.g., further protocol models. Just send us a pull request.

Manual

We are currently rewriting the manual. Bear with us for a second and have a look at the example protocol models.

Protocol Models

The protocol models have the extension .spdl and can be found in the following directories:

  • ./gui/Protocols, containing the officially released models, and
  • ./testing, containing models currently under development.

License

Currently these Scyther sources are licensed under the GPL 2, as indicated in the source code. Contact Cas Cremers if you have any questions.