Abstract
Definition 1. should read as follows:
A program is type-safe for a KPU (‘crypto-safe’) if those KPU machine instructions that work on encrypted data always get encrypted data on which to work during execution of the program, while those instructions that work on unencrypted data always get unencrypted data on which they can work, and (‘alias-safe’) every read from an encrypted address is from the exact same encryption of that address that was last written to.
The article uses just ‘type-safe’ or ‘crypto-safe’ throughout, understanding that the program code under consideration is always already ‘alias-safe’ in its own right.
The original online version for this chapter can be found at http://dx.doi.org/10.1007/978-3-642-36563-8_9
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Breuer, P.T., Bowen, J.P. (2013). Erratum: A Fully Homomorphic Crypto-Processor Design. In: Jürjens, J., Livshits, B., Scandariato, R. (eds) Engineering Secure Software and Systems. ESSoS 2013. Lecture Notes in Computer Science, vol 7781. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-36563-8_16
Download citation
DOI: https://doi.org/10.1007/978-3-642-36563-8_16
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-36562-1
Online ISBN: 978-3-642-36563-8
eBook Packages: Computer ScienceComputer Science (R0)