A proof-carrying-code infrastructure for resources

Hans Wolfgang Loidl, Kenneth MacKenzie, Steffen Jost, Lennart Beringer

Research output: Chapter in Book/Report/Conference proceedingConference contribution

4 Scopus citations

Abstract

This paper tackles the issue of increasing dependability of distributed systems in the presence of mobile code. To this end we present a complete Proof-carrying-code (PCC) infrastructure for independent and automatic certification of resource bounds of mobile JVM programs. This includes a certifying compiler for a high-level language, which produces a certificate of bounded heap consumption, and independent certificate validation, realised via proof-checking, on the code-consumer side. Thus, we are now in a position to automatically infer linear upper bounds on the heap consumption of a strict, first-order functional language, generate a certificate encoding a formal proof of such bounded heap consumption and independently validate this certificate at the consumer side by checking the certificate. This prevents mobile code from exhausting resources on the local machine.

Original languageEnglish (US)
Title of host publicationProceedings - 2009 4th Latin-American Symposium on Dependable Computing, LADC 2009
Pages127-134
Number of pages8
DOIs
StatePublished - 2009
Externally publishedYes
Event2009 4th Latin-American Symposium on Dependable Computing, LADC 2009 - Joao Pessoa, Brazil
Duration: Sep 1 2009Sep 4 2009

Publication series

NameProceedings - 2009 4th Latin-American Symposium on Dependable Computing, LADC 2009

Conference

Conference2009 4th Latin-American Symposium on Dependable Computing, LADC 2009
Country/TerritoryBrazil
CityJoao Pessoa
Period9/1/099/4/09

All Science Journal Classification (ASJC) codes

  • Computer Science Applications
  • Software

Keywords

  • Program verification
  • Proof-carrying-code
  • Resource analysis

Fingerprint

Dive into the research topics of 'A proof-carrying-code infrastructure for resources'. Together they form a unique fingerprint.

Cite this