gorazdko/bc-crypto-base

Audited Cryptographic Functions

Blockchain Commons Crypto Base

Well-Reviewed and Audited Cryptographic Functions for Use in Blockchain Commons Software Projects

These are selected cryptographic functions used by various Blockchain Commons software projects that have have been vetted by the developers as having been sufficiently well-reviewed and/or cryptographically audited by other parties, but also meet our specific needs (for instance to be able to run on embedded hardware).

Installation

$ ./configure
$ make check
$ sudo make install

This sequence runs the module's unit tests.

Use

1. Link against libbc-crypto-base.a.
2. Include the umbrella header in your code:

#include <bc-crypto-base/bc-crypto-base.h>

Notes for Maintainers

Before accepting a PR that can affect build or unit tests, make sure the following sequence of commands succeeds:

$ ./configure
$ make distcheck
$ make distclean

make distcheck builds a distribution tarball, unpacks it, then configures, builds, and runs unit tests from it, then performs an install and uninstall from a non-system directory and makes sure the uninstall leaves it clean. make distclean removes all known byproduct files, and unless you've added files of your own, should leave the directory in a state that could be tarballed for distribution. After a make distclean you'll have to run ./configure again.

Origin, Authors, Copyright & Licenses

Unless otherwise noted (either in this /README.md or in the file's header comments) the contents of this repository are Copyright © 2020 by Blockchain Commons, LLC, and are licensed under the spdx:BSD-2-Clause Plus Patent License.

The table below establishes provenance (repository of origin, permalink, and commit id) for each source file in this repository. Contributors to these files are listed in the commit history for each file, first in this repo, then in the repo of their origin.

In most cases, the authors, copyright, and license for each file reside in comments in the source. When it does not we have attempted to attribute it accurately below.

File	From	Commit	Authors & Copyright (c)	License
bc-crypto-hash.h	blockchaincommons/bc-crypto-base	?	2020 Blockchain Commons, LLC	BSD-2-Clause-Patent
hmac.c	trezor/trezor-firmware	fdad317	2013-2014 Tomas Dzetkulic 2013-2014 Pavol Rusnak	MIT
hmac.h	trezor/trezor-firmware	4e0d813	2013-2014 Tomas Dzetkulic 2013-2014 Pavol Rusnak	MIT
memzero.c	trezor/trezor-firmware derived from jedisct1/libsodium	4e0d813 32385c6	2013-2019 Frank Denis	ISC
memzero.h	trezor/trezor-firmware derived from jedisct1/libsodium	4e0d813 32385c6	2013-2019 Frank Denis	ISC
options.h	trezor/trezor-firmware	4e0d813	2013-2014 Pavol Rusnak	MIT
pbkdf2.c	trezor/trezor-firmware	fdad317	2013-2014 Tomas Dzetkulic 2013-2014 Pavol Rusnak	BSD-3-Clause
pbkdf2.c	trezor/trezor-firmware	4e0d813	2013-2014 Tomas Dzetkulic 2013-2014 Pavol Rusnak	BSD-3-Clause
sha2.c	trezor/trezor-firmware	fdad317	2000-2001 Aaron D. Gifford 2013-2014 Pavol Rusnak	BSD-3-Clause
sha2.h	trezor/trezor-firmware	4e0d813	2000-2001 Aaron D. Gifford 2013-2014 Pavol Rusnak	BSD-3-Clause
crc32.c crc32.h	NA	NA	2020 Wolf McNally for Blockchain Commons	BSD-3-Clause

Used by …

• bc-shamir — Blockchain Common's Shamir Secret Sharing Library

Derived from…

• trezor/trezor-firmware/crypto — Heavily optimized cryptography algorithms for embedded devices, used by both Trezor Core and the Trezor One firmware, from Satoshi Labs (docs).

Dependencies

• autotools - Gnu Build System from Free Software Foundation (intro).

Financial Support

Blockchain Commons Crypto Base is a project of Blockchain Commons. We are proudly a "not-for-profit" social benefit corporation committed to open source & open development. Our work is funded entirely by donations and collaborative partnerships with people like you. Every contribution will be spent on building open tools, technologies, and techniques that sustain and advance blockchain and internet security infrastructure and promote an open web.

To financially support further development of Blockchain Commons Crypto Base and other projects, please consider becoming a Patron of Blockchain Commons through ongoing monthly patronage as a GitHub Sponsor. You can also support Blockchain Commons with bitcoins at our BTCPay Server.

Contributing

We encourage public contributions through issues and pull-requests! Please review CONTRIBUTING.md for details on our development process. All contributions to this repository require a GPG signed Contributor License Agreement.

Questions & Support

As an open-source, open-development community, Blockchain Commons does not have the resources to provide direct support of our projects. If you have questions or problems, please use this repository's issues feature. Unfortunately, we can not make any promises on response time.

If your company requires support to use our projects, please feel free to contact us directly about options. We may be able to offer you a contract for support from one of our contributors, or we might be able to point you to another entity who can offer the contractual support that you need.

Credits

The following people directly contributed to this repository. You can add your name here by getting involved — the first step is to learn how to contribute from our CONTRIBUTING.md documentation.

Name	Role	Github	Email	GPG Fingerprint
Christopher Allen	Principal Architect	@ChristopherA	<[email protected]>	FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED
Wolf McNally	Project Lead	@WolfMcNally	<[email protected]>	9436 52EE 3844 1760 C3DC  3536 4B6C 2FCF 8947 80AE

Responsible Disclosure

We want to keep all our software safe for everyone. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner. We are unfortunately not able to offer bug bounties at this time.

We do ask that you offer us good faith and use best efforts not to leak information or harm any user, their data, or our developer community. Please give us a reasonable amount of time to fix the issue before you publish it. Do not defraud our users or us in the process of discovery. We promise not to bring legal action against researchers who point out a problem provided they do their best to follow the these guidelines.

Reporting a Vulnerability

Please report suspected security vulnerabilities in private via email to [email protected] (do not use this email for support). Please do NOT create publicly viewable issues for suspected security vulnerabilities.

The following keys may be used to communicate sensitive information to developers:

Name	Fingerprint
Christopher Allen	FDFE 14A5 4ECB 30FC 5D22 74EF F8D3 6C91 3574 05ED

You can import a key by running the following command with that individual’s fingerprint: gpg --recv-keys "<fingerprint>" Ensure that you put quotes around fingerprints that contain spaces.

Version History

0.2.0, 7/1/2020

• Added functions for computing CRC-32 checksums.

0.1.0, 5/19/2020

• Initial release.