World Library  
Flag as Inappropriate
Email this Article

Bouncy Castle (cryptography)

Article Id: WHEBN0003636963
Reproduction Date:

Title: Bouncy Castle (cryptography)  
Author: World Heritage Encyclopedia
Language: English
Subject: Cryptographic software, AES implementations, RSA BSAFE, Stunnel, OpenSSL
Collection: Cryptographic Software, Java (Programming Language) Libraries, Software Using the Mit License, Transport Layer Security Implementation
Publisher: World Heritage Encyclopedia
Publication
Date:
 

Bouncy Castle (cryptography)

Bouncy Castle
Stable release

1.53 (Java) (October 10, 2015 (2015-10-10) [1])

1.7 (C#) (April 7, 2011 (2011-04-07) [2])
Written in C# and Java
Operating system Cross-platform
Type Cryptography API
License MIT License[3]
Website .orgbouncycastle

Bouncy Castle is a collection of charitable organization: Legion of the Bouncy Castle Inc.

Bouncy Castle is Australian in origin and therefore American restrictions on the export of cryptographic software do not apply to it.

Contents

  • History 1
  • Architecture 2
  • Spongy Castle 3
  • See also 4
  • Notes 5
  • External links 6

History

Bouncy Castle started when two colleagues were tired of having to re-invent a set of cryptography libraries each time they changed jobs working in server-side JavaSE. One of the developers was active in JavaME (J2ME at that time) development as a hobby and a design consideration was to include the greatest range of Java VMs for the library, including those on J2ME.

This design consideration led to the architecture that exists in Bouncy Castle.

Some key properties of the project are:

  • Founded in May 2000. Now has around 20,000 downloads a month, including 5000 of the full Java distribution.
  • Originally just Java, C# API added in 2006.
  • Original Java API around 27,000 lines including test code. Provided support for J2ME, a JCE/JCA provider, and basic X.509 certificate generation.
  • Latest Java release, 1.53, 390,640 lines including test code. Supports same functionality as original release (with a larger number of algorithms) plus PKCS#10, PKCS#12, CMS, S/MIME, OpenPGP, DTLS, TLS, OCSP, TSP, CMP, CRMF, DVCS, DANE, and Attribute Certificates.
  • C# API around 145,000 lines. Supports most of what the Java API does.
  • Strong emphasis on standards compliance and adaptability.
  • Public support facilities include an issue tracker, dev mailing list and a wiki all available at the website.
  • Commercial support provided under resources for the relevant API listed on the Bouncy Castle website

On 18 October 2013, a not-for-profit association, the Legion of the Bouncy Castle Inc. was established in the state of Victoria, Australia, by the core developers and others to take ownership of the project and support the ongoing development of the APIs. The association was recognised as an Australian charity with a purpose of advancement in education and a purpose that is beneficial to the community by the Australian Charities and Not-For-Profits Commission on 7 November 2013. The association was authorised to fundraise to support its purposes on 29 November 2013 by Consumer Affairs Victoria.

Architecture

The Bouncy Castle architecture consists of two main components that support the base cryptographic capabilities. These are known as the 'light-weight' API, and the Java Cryptography Extension (JCE) provider. There are further components that are built upon the JCE provider which support additional functionality such as PGP support, S/MIME and similar.

The low-level, or 'light-weight', API is a set of APIs that implement all the underlying cryptographic algorithms. The APIs were designed to be simple enough to use if needed, but provided the basic building blocks for the JCE provider. The intent is to use the low-level API in memory constrained devices (JavaME) or when easy access to the JCE libraries is not possible (such as distribution in an applet). As the light-weight API is just Java code, the Java virtual machine (JVM) does not impose any restrictions on the operation of the code, and at early times of the Bouncy Castle history it was the only way to develop strong cryptography that was not crippled by the Jurisdiction Policy files which prevented any JCE providers from performing "strong" encryption.

The JCE-compatible provider is built upon the low-level APIs. As such, the source code for the JCE provider is an example of how to implement many of the "common" crypto problems using the low-level API. Many projects have been built using the JCE provider, including an Open Source Certificate Authority EJBCA.

Spongy Castle

The Android operating system, as of early 2014, includes a customized version of Bouncy Castle.[4] Due to class name conflicts, this prevents Android applications from including and using the official release of Bouncy Castle as-is. A third-party project called Spongy Castle distributes a renamed version of the library to work around this issue.[5]

See also

Notes

  1. ^ "Latest Java Releases - bouncycastle.org". 2015-10-10. Retrieved 2015-10-15. 
  2. ^ "The Legion of the Bouncy Castle C# Cryptography APIs". 2011-04-07. Retrieved 2014-06-16. 
  3. ^ "Bouncy Castle - LICENSE". 
  4. ^ Reimer Pohlmann Schneider (October 17, 2014). ISSE 2014 Securing Electronic Business Processes: Highlights of the Information Security Solutions Europe 2014 Conference. Springer. p. 205. 
  5. ^ "Spongy Castle". Github. Retrieved April 29, 2013. 

External links

  • "Legion of the Bouncy Castle". 
  • Roedy Green. "Bouncy Castle". Mindprod Java glossary. 
  • kpbe An open source Password Based Encryption tool for files that uses Bouncy Castle C# implementation
  • JCrypTool (JCT) is a widespread open source e-learning tool illustrating more than 100 cryptographic and cryptanalytic concepts. It uses the Bouncy Castle Java implementation. JCT is built with Java/Eclipse/RCP/SWT and runs on Windows, MacOS, and Linux. See CrypTool.
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.