skip to main content
research-article
Free Access

Finding more than one worm in the apple

Published:01 July 2014Publication History
Skip Abstract Section

Abstract

If you see something, say something.

References

  1. Apple Inc. Xcode overview, 2014; http://bit.ly/1kXUAzDGoogle ScholarGoogle Scholar
  2. Arthur, C. Apple's SSL iPhone vulnerability: How did it happen, and what next? The Guardian, (Feb. 25, 2014); http://www.theguardian.com/technology/2014/feb/25/apples-ssl-iphone-vulnerability-how-did-it-happen-and-what-next.Google ScholarGoogle Scholar
  3. Auerbach, D. An extraordinary kind of stupid. Slate (Feb. 25, 2014); http://slate.me/1o75yGsGoogle ScholarGoogle Scholar
  4. Bellovin, S.M. Goto Fail. SMBlog (Feb. 23, 2014); https://www.cs.columbia.edu/~smb/blog/2014-02/2014-02-23.html.Google ScholarGoogle Scholar
  5. Bland, M. Test Certified, 2011; http://mike-bland.com/2011/10/18/test-certified.html.Google ScholarGoogle Scholar
  6. Bland, M. Testing on the Toilet, 2011; http://mike-bland.com/2011/10/25/testing-on-the-toilet.html.Google ScholarGoogle Scholar
  7. Bland, M. Test Mercenaries, 2012; http://mike-bland.com/2012/07/10/test-mercenaries.html.Google ScholarGoogle Scholar
  8. Bland, M. AutoTest Central, 2014; http://autotestcentral.com/small-medium-and-large-test-sizesGoogle ScholarGoogle Scholar
  9. Dijkstra, E. A case against the GO TO statement. Commun. ACM 11, 3 (Nov. 1968), 147--148; http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF. Google ScholarGoogle ScholarDigital LibraryDigital Library
  10. Fuller, L. TestableSecurity: demonstrating that <code>SSLVerifySignedServerKeyExchange()</code> is trivially testable, 2014; https://github.com/landonf/Testability-CVE-2014-1266.Google ScholarGoogle Scholar
  11. Google, Inc. Too many tests. Google Testing Blog (Feb. 21, 2008); http://googletesting.blogspot.com/2008/02/in-movie-amadeus-austrian-emperor.html.Google ScholarGoogle Scholar
  12. Greenfield, R. Why Apple's power cords keep breaking. The Wire (July 30, 2012); http://www.thewire.com/technology/2012/07/why-apples-power-cords-keep-breaking/55202/.Google ScholarGoogle Scholar
  13. Langley, A. Apple's SSL/TLS bug. Imperial Violet (Feb. 22, 2014); https://www.imperialviolet.org/2014/02/22/applebug.html.Google ScholarGoogle Scholar
  14. Ray, C.K. TDD and signed SSLVerifySignedServerKeyExchange. Exploring Agile Solutions: Software Development with Agile Practices (Feb. 23, 2014); http://agilesolutionspace.blogspot.com/2014/02/tdd-and-signed-sslverifysignedserverkey.html.Google ScholarGoogle Scholar
  15. Schneier, B. Was the iOS SSL flaw deliberate? Schneier on Security: A Blog Covering Security and Security Technology (Feb. 2014); https://www.schneier.com/blog/archives/2014/02/was_the_ios_ssl.html.Google ScholarGoogle Scholar
  16. van Deursen, A. Learning from Apple's #gotofail security bug. Arie van Deursen: Software Engineering in Theory and Practice (Feb. 22, 2014); http://avandeursen.com/2014/02/22/gotofail-security/.Google ScholarGoogle Scholar

Index Terms

  1. Finding more than one worm in the apple

              Recommendations

              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 57, Issue 7
                July 2014
                98 pages
                ISSN:0001-0782
                EISSN:1557-7317
                DOI:10.1145/2622628
                • Editor:
                • Moshe Y. Vardi
                Issue’s Table of Contents

                Copyright © 2014 ACM

                Publication rights licensed to ACM. ACM acknowledges that this contribution was authored or co-authored by an employee, contractor or affiliate of a national government. As such, the Government retains a nonexclusive, royalty-free right to publish or reproduce this article, or to allow others to do so, for Government purposes only.

                Publisher

                Association for Computing Machinery

                New York, NY, United States

                Publication History

                • Published: 1 July 2014

                Permissions

                Request permissions about this article.

                Request Permissions

                Check for updates

                Qualifiers

                • research-article
                • Popular
                • Refereed

              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