andr3/scyther
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Scyther with my modifications
1,550 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%
f1f2f28f61
Go to file
Cas Cremers f1f2f28f61 Rewriting option parser wrapper to ensure memory is not lost. 
The option parser wrapper allocated memory in an incorrect way, which
could lead to problems especially with --xml-output, since it would
access the memory at a later point in the execution. This could then
propagate to GUI problems, since the GUI uses the --xml-output switch.
Rewrote the code to be more readable and less incorrect.
2014-06-10 14:37:40 +01:00
dist Removing obsolete manual copy commands from release scripts, since we copy the manual in now periodically by hand. 2013-12-12 09:02:30 +00:00
gui Updated version of the manual. 2014-02-18 12:32:24 +00:00
scripts Added loop script which I had always wanted before. 2008-08-21 21:55:55 +02:00
src Rewriting option parser wrapper to ensure memory is not lost. 2014-06-10 14:37:40 +01:00
testing Cleanup: Update notes for experimental directory to point to the correct protocols directory. 2014-03-19 09:35:26 +00:00
commit-template Added template for commits. 2011-04-06 10:50:43 +02:00
Makefile Minor synchronisation updates. 2012-12-17 10:14:31 +01:00
protocols Added softlink to protocols directory. 2012-11-15 13:41:02 +01:00
README.md Propagating compilation requirements to readme. 2014-02-18 12:21:04 +00: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://www.cs.ox.ac.uk/people/cas.cremers/scyther/index.html.

Installing from source

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
  • gcc-multilib

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

sudo apt-get install cmake build-essential flex bison gcc-multilib

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. The current (incomplete) snapshot of the manual can be found in the following location:

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.