Titlebook: Software Security -- Theories and Systems; Mext-NSF-JSPS Intern Mitsuhiro Okada,Benjamin C. Pierce,Akinori Yonezaw Conference proceedings 2

消極詞匯

對(duì)手

Types and Effects for Non-interfering Program Monitors the sequence of program actions deviates from a specified security policy, the monitor transforms the sequence or terminates the program. We present the design and formal specification of a language for defining the policies enforced by program monitors..Our language provides a number of facilities

有危險(xiǎn)

焦慮

Enforcing Java Run-Time Properties Using Bytecode Rewritingodify the semantics of Java while making no changes to the Java virtual machine itself. While this gives us portability and power, there are numerous pitfalls, mostly stemming from the limitations imposed upon Java bytecode by the Java virtual machine. We reflect on our experience building three sec

郊外

insert

Formalization and Verification of a Mail Server in Coqgs of the mail server may be abused for eavesdropping mail contents, spreading virus, sending spam messages, etc. We have verified a part of a mail server written in Java, by manually translating the Java program into a Coq function as faithfully as possible, and verifying properties of the Coq func

exigent

Design and Implementation of Security System Based on Immune System cooperation among immune cells of the system. This system implements each immune cell as an agent based on our multiagent language, which is an extension of concurrent logic programming languages. These agents can detect and reject intrusion by cooperating with each other.

他姓手中拿著

Alveolar-Bone

Typing One-to-One and One-to-Many Correspondences in Security Protocolsed to specify correctness properties of cryptographic protocols. In earlier work, we showed how to typecheck one-to-one correspondences for protocols expressed in the spi-calculus. We present a new type and e.ect system able to verify both one-to-one and one-to-many correspondences.

Infelicity

Proof-Carrying Code with Untrusted Proof RulesPCC the producer negotiates beforehand, and in an unspecified way, with the consumer the permission to prove safety in whatever high-level way it chooses. In practice this has meant that highlevel rules for type safety have been hard-wired into the system as part of the trusted code base. This limit