I agree to license my contributions to each file under the terms given at the top of each file I changed.
The most important contributions are uses of ring. That is, we're very interested in seeing useful things built on top of ring, like implementations of TLS, SSH, the Noise Protocol, etc.
Of course, contributions to ring‘s code base are highly appreciated too. If you want to work directly on ring and you don’t have an idea for something to contribute already, see these curated lists of open issues:
In addition, we're always interested in these kinds of contributions:
Before submitting pull requests, make sure that the tests succeed both when running cargo test
and cargo test --features=rsa_signing
. See BUILDING.md for more info about the features flags that are useful for people hacking on ring.
Travis CI is used for Android, Linux, and macOS. Appveyor is used for Windows. The tests are run in debug and release configurations, for the current release of each Rust channel (Stable, Beta, Nightly), for each configuration listed in the table below. The C compilers listed are used for compiling the C portions.
Please report bugs either as pull requests or as issues in the issue tracker. ring has a full disclosure vulnerability policy. Please do NOT attempt to report any security vulnerability in this code privately to anybody.
See LICENSE.