1998
DOI: 10.1007/3-540-68671-1_12
|View full text |Cite
|
Sign up to set email alerts
|

The Safe-Tcl Security Model

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
40
0

Year Published

1998
1998
2003
2003

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 68 publications
(40 citation statements)
references
References 7 publications
0
40
0
Order By: Relevance
“…This framework will then be used to define some general attack classes, which can then be instantiated on particular systems. The definitions presented in this section were obtained by the analysis of a number of existing systems and their security models [8,9,12,14], as well as by the OMG's MASIF specification [10].…”
Section: General Framework For the Analysismentioning
confidence: 99%
“…This framework will then be used to define some general attack classes, which can then be instantiated on particular systems. The definitions presented in this section were obtained by the analysis of a number of existing systems and their security models [8,9,12,14], as well as by the OMG's MASIF specification [10].…”
Section: General Framework For the Analysismentioning
confidence: 99%
“…The Tcl enforcement module is implemented with Safe Tcl. Safe Tcl is a Tcl extension that is designed to allow the safe execution of untrusted Tcl scripts [18,21]. Safe Tcl provides two interpreters.…”
Section: Authorization and Enforcementmentioning
confidence: 99%
“…After that, the Java agent corresponds exactly to the Tcl agent. It turns on digital signatures (lines 4-5), registers with the agent system (lines 7-8), migrates to the location of the search engine (lines 10-11), performs the multi-step query (lines [13][14][15][16][17][18], and returns home (lines [20][21][22]. As with the Tcl examples, error-checking and some initialization code have been omitted.…”
Section: Figmentioning
confidence: 99%
See 1 more Smart Citation
“…Mobile agents can gain unauthorized access to confidential data on the platform if they can bypass the platform's security policy. Several techniques have been proposed for protecting the agent platform, namely Signed Code [22], Proof Carrying Code [42], Path Histories [46], Authorization Certificates [59], Safe Code Interpretation [47], State Appraisal [29], and Software-based Fault Isolation [60]. Some of these techniques aim at authenticating the mobile agent or the source of the agent, while others are focused on safe code execution.…”
Section: Securitymentioning
confidence: 99%