skip to main content
article
Free Access

Trust (and mistrust) in secure applications

Published:01 February 2001Publication History
First page image
Skip Supplemental Material Section

Supplemental Material

References

  1. 1 Adams C. and Zuccherato, R. A global PMI for electronic content distribution. In Seventh Annual Workshop on Selected Areas in Cryptography. Workshop Record, Aug. 2000. Springer-Verlag, to appear.]] Google ScholarGoogle ScholarDigital LibraryDigital Library
  2. 2 Collberg, C., Thomborson, C. and Low, D. A taxonomy of obfuscating transformations. Technical Report 148, Department of Computer Science, University of Auckland, New Zealand, Jul. 1997; ftp.cs.auckland. ac.nz/out/techreports/.]]Google ScholarGoogle Scholar
  3. 3 Internet Security Systems. Form tampering vulnerabilities in several Web-based shopping cart applications; xforce.iss.net/alerts/ advise42.php, Feb. 2000.]]Google ScholarGoogle Scholar
  4. 4 Wagner, D., Foster, J.S., Brewer, E.A. and Aiken, A. A first step towards automated detection of buffer overrun vulnerabilities. In Network and Distributed Systems Security Symposium, Feb. 2000.]]Google ScholarGoogle Scholar

Index Terms

  1. Trust (and mistrust) in secure applications

              Recommendations

              Reviews

              Andrew Robert Huber

              Misplaced trust leads to reliability and security problems in software. A trust relationship exists whenever a program expects an entity (such as user input) to have a certain property. The authors illustrate how failing to explicitly define these trust relationships during software development leads to incorrect software. The buffer overflow problem is used as an example of misplaced trust in input values. Another example uses hidden parameters in Web scripts. An application-level example of a Web-based client/server architecture demonstrates problems with trusting client applications and execution environments. Although helpful in making developers aware of trust and related issues, the paper neither fully describes the problem nor provides solutions. The authors neither define nor categorize trust relationships completely, nor do they describe how to determine what trust assumptions a program makes or should make. Only generalities are offered: "As little trust as possible should be placed in the hands of external components." Advice on how much trust this is, or how to determine if more than the minimum trust has been assumed would be helpful. Incomplete requirements and miscommunication between development groups are cited as the two most common causes of dangerous trust assumptions, yet no suggestions are offered for addressing these causes. The authors also fail to differentiate between trust relationships arising during development (e.g., trusting networks over which design documents are sent) and those in the developed software. Developers may find this paper enlightening, but will likely be left wondering what to do next.

              Access critical reviews of Computing literature here

              Become a reviewer for Computing Reviews.

              Comments

              Login options

              Check if you have access through your login credentials or your institution to get full access on this article.

              Sign in

              Full Access

              • Published in

                cover image Communications of the ACM
                Communications of the ACM  Volume 44, Issue 2
                Feb. 2001
                92 pages
                ISSN:0001-0782
                EISSN:1557-7317
                DOI:10.1145/359205
                Issue’s Table of Contents

                Copyright © 2001 ACM

                Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

                Publisher

                Association for Computing Machinery

                New York, NY, United States

                Publication History

                • Published: 1 February 2001

                Permissions

                Request permissions about this article.

                Request Permissions

                Check for updates

                Qualifiers

                • article

              PDF Format

              View or Download as a PDF file.

              PDF

              eReader

              View online with eReader.

              eReader

              HTML Format

              View this article in HTML Format .

              View HTML Format