introduce CAP, a Context-Aware Privacy-preserving LBS system with integrated protection for data privacy and communication anonymity. We have implemented CAP and integrated it with Google Maps, a popular LBS system. Theoretical analysis and experimental results validate CAP’s effectiveness on privacy

Abstract not found

Abstract not found

Abstract not found

presence of mobile code. The focus of that paper was on making the case for the importance of the local OS, and outlining an appropriate OS for that environment: the Fluke [10] operating system, an OS based on a recursive virtual machine model, analogous to the Cambridge CAP Computer [30], but implemented

. Our system will be deployed at every instance of VM as well as at the client node end to detect and prevent intrusions due to malicious programs by an IDPS agents. This MA-IDPS model not only protects the cloud environment but also secures its agents and encrypts data tables that are part of IDPS

devices by using resource isolation to protect hosted operating systems. VMMs could also be used to place constraints on the resource utilization of hosted operating systems and their applications. Xen is closely tied to the x86 computer architecture and is optimized to work well on desktop personal

; is expressed by possession of directory capabilities. Preservation of capabilities An executing program (protected procedure) in the CAP computer has access to a set of capabilities specified by its capability segments. These capabilities fall into various classes: store capabilities for segments of code

Paper prepared for the NBER project on “Risks of Financial Institutions”. We benefited from suggestions and criticism by many participants in the NBER project on “Risks of financial institutions”, in particular by the organizers Mark Carey (also involving Dean Amel and Allen Berger) and Rene Stulz, by our discussant Tony Saunders and by Patrick de Fontnouvelle, Gary Gorton, Andy Lo, Jim O’Brien and Eric Rosengren. Furthermore, we are grateful for comments we received at the 2004 European Finance Association Meetings in Maastricht, in particular by our discussant Marco da Rin and by Christian Upper, at the 2004 Ottobeuren seminar in economics, notably the thoughts of our discussant Ernst Baltensberger, of Friedrich Heinemann and of Gerhard Illing, as well as at seminars of the Max Planck Institute for Research on Collective Goods, the Federal Reserve Bank of St. Louis, the ECB and the University of Frankfurt. Gabe de Bondt and David Marques Ibanez supported us enormously in finding yield spread data, Lieven Baele and Richard Stehle kindly made us aware of pitfalls in Datastream equity data. Very helpful research assistance by Sandrine Corvoisier, Peter Galos and Marco Lo Duca as well as editorial support by Sabine Wiedemann are gratefully acknowledged. Any views expressed only reflect those of the authors and should not be interpreted as the ones of the ECB or the Eurosystem. The views expressed herein are those of the author(s) and do not necessarily reflect the views of the National Bureau of Economic Research.

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,