|Formulating Security in Programming Languages email@example.com (Seima Rao) (2015-01-15)|
|From:||Seima Rao <firstname.lastname@example.org>|
|Date:||Thu, 15 Jan 2015 17:49:53 +0530|
|Posted-Date:||16 Jan 2015 10:19:18 EST|
I came up with this notation in stating the goal of security in
Programming Language Construct = Syntax + Semantics + Side Effect.
N# semantics N# syntax = Syntax + Semantics + Side Effects
Security = N# semantics N# syntax - Side Effects
I will explain via a C example:
N# (malloc-semantics) N# (malloc-syntax, free-opt-syntax) = Memory
Allocation + Memory Deallocation + Memory Leak
In the above, the LHS says, apply the combined syntaxes of malloc
and optional-free to the semantics of malloc. The result is that
Memory Leak is a side effect. So, the goal of security is to remove
Does the approach specified in the above paragraphs occur to you as
brute force esp when generalizing over the entire grammar(small &
manageable) if not the semantics(the whole large LRM)?
Is anyone interested in this topic ?
Are there any other formal approaches to investigating security in
Return to the
Search the comp.compilers archives again.