Scollar
From Erights
(Difference between revisions)
(3 intermediate revisions not shown) | |||
Line 1: | Line 1: | ||
- | + | == What is Scoll (and Scollar) ? == | |
+ | ''Scoll'' is a tool-based approach to help design and develop secure programs. It involves: | ||
+ | * a declarative language to express safety problems that are relevant to software developers: "Safe collaboration language". | ||
+ | * a tool to solve these problems: ''Scollar'' | ||
+ | * a datalog based formalism "KBM" (Knowledge Behavior Models) gives Scoll its formal semantics | ||
- | + | == Scoll is an Open Source Project== | |
+ | [http://www.scoll.evoluware.eu The home page of the Scoll Project] | ||
+ | * [http://www.scoll.evoluware.eu/scolldoc.html the online documentation about Scoll and Scollar] | ||
+ | * [http://developer.berlios.de/projects/scollar/ the Oz code for the Scollar backend component] | ||
+ | * [http://developer.berlios.de/projects/swingscollar/ the Java code for the GUI component of Scollar (SwingScollar)] | ||
+ | |||
+ | == Publications on Scoll == | ||
+ | * [http://www.evoluware.eu/scoll/fastscoll.pdf "Know What You Trust: Analyzing and Designing Trust Policies with Scoll"], Fred Spiessens, Jerry den Hartog, and Sandro Etallein "Formal Aspects in Security and Trust", LNCS 5491, April 2009, pg.129-142. | ||
+ | * [http://www.evoluware.eu/fsp_thesis.pdf "Patterns of Safe Collaboration"], Fred Spiessens' PhD Thesis, February 2009, UcL Louvain-la-Neuve. | ||
+ | * [http://www.info.ucl.ac.be/~pvr/tgc05fs.pdf "A Practical Formal Model for Safety Analysis in Capability-Based Systems"], Fred Spiessens and Peter Van Roy, in "Trustworthy Global Computing", LNCS 3705, december 2005, pg. 248-278. | ||
+ | * [http://www.info.ucl.ac.be/~pvr/rr2005-12.pdf "Scoll and Scollar: Safe collaboration based on partial trust"], Fred Spiessens, Yves Jaradin, and Peter Van Roy, Technical Report, 2005 , UcL Louvain-la-Neuve. | ||
+ | * [http://www.info.ucl.ac.be/~pvr/rr2005-11.pdf "Using Constraints To Analyze And Generate Safe Capability Patterns"], Fred Spiessens, Yves Jaradin, and Peter Van Roy, Technical Report, 2005 , UcL Louvain-la-Neuve. | ||
+ | * [http://www.info.ucl.ac.be/~pvr/rr2005-10.pdf "SCOLL: A language for safe capability based collaboration"], Yves Jaradin, Fred Spiessens, Peter Van Roy, Technical Report, 2005, UcL Louvain-la-Neuve. | ||
[[Category:Applications]] | [[Category:Applications]] | ||
[[Category:Formal Reasoning]] | [[Category:Formal Reasoning]] |
Latest revision as of 10:50, 31 May 2009
What is Scoll (and Scollar) ?
Scoll is a tool-based approach to help design and develop secure programs. It involves:
- a declarative language to express safety problems that are relevant to software developers: "Safe collaboration language".
- a tool to solve these problems: Scollar
- a datalog based formalism "KBM" (Knowledge Behavior Models) gives Scoll its formal semantics
Scoll is an Open Source Project
The home page of the Scoll Project
- the online documentation about Scoll and Scollar
- the Oz code for the Scollar backend component
- the Java code for the GUI component of Scollar (SwingScollar)
Publications on Scoll
- "Know What You Trust: Analyzing and Designing Trust Policies with Scoll", Fred Spiessens, Jerry den Hartog, and Sandro Etallein "Formal Aspects in Security and Trust", LNCS 5491, April 2009, pg.129-142.
- "Patterns of Safe Collaboration", Fred Spiessens' PhD Thesis, February 2009, UcL Louvain-la-Neuve.
- "A Practical Formal Model for Safety Analysis in Capability-Based Systems", Fred Spiessens and Peter Van Roy, in "Trustworthy Global Computing", LNCS 3705, december 2005, pg. 248-278.
- "Scoll and Scollar: Safe collaboration based on partial trust", Fred Spiessens, Yves Jaradin, and Peter Van Roy, Technical Report, 2005 , UcL Louvain-la-Neuve.
- "Using Constraints To Analyze And Generate Safe Capability Patterns", Fred Spiessens, Yves Jaradin, and Peter Van Roy, Technical Report, 2005 , UcL Louvain-la-Neuve.
- "SCOLL: A language for safe capability based collaboration", Yves Jaradin, Fred Spiessens, Peter Van Roy, Technical Report, 2005, UcL Louvain-la-Neuve.