diff options
| author | Charles Lee <ckl@google.com> | 2024-04-08 23:05:14 +0000 |
|---|---|---|
| committer | Charles Lee <ckl@google.com> | 2024-04-08 23:05:14 +0000 |
| commit | cd27d6419bedd83cbd24611ec54b6d4bfdb0cdca (patch) | |
| tree | cb041a010eb80e3ff2f14089efb031dc13221f29 | |
| parent | 507bb993e90a87d0a62591a5284bc34a3f1c5c22 (diff) | |
| download | wycheproof-cd27d6419bedd83cbd24611ec54b6d4bfdb0cdca.tar.gz | |
Update documentation to reflect new repository location.upstream-master
| -rw-r--r-- | CONTRIBUTING.md | 26 | ||||
| -rw-r--r-- | README.md | 9 |
2 files changed, 3 insertions, 32 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fa97ad3..fca3996 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,16 +2,6 @@ Want to contribute? Great! First, read this page (including the small print at the end). ### Before you contribute -Before we can use your code, you must sign the -[Google Individual Contributor License Agreement] -(https://cla.developers.google.com/about/google-individual) -(CLA), which you can do online. The CLA is necessary mainly because you own the -copyright to your changes, even after your contribution becomes part of our -codebase, so we need your permission to use and distribute your code. We also -need to be sure of various other things—for instance that you'll tell us if you -know that your code infringes on other people's patents. You don't have to sign -the CLA until after you've submitted your code for review and a member has -approved it, but you must do it before we can put your code into our codebase. Before you start working on a larger contribution, you should get in touch with us first through the issue tracker with your idea so that we can help out and possibly guide you. Coordinating up front makes it much easier to avoid @@ -22,22 +12,6 @@ If your tests uncover security vulnerabilities, please first report directly to the maintainers of the libraries. You should only submit tests to us once the bugs have been acknowledged or fixed. -Google has several -[security reward programs](https://www.google.com/about/appsecurity/programs-home/) -that provide cash rewards for quality security research that identifies or fixes -security vulnerabilities in products that we provide or proactive security -improvements to select open-source products. If your tests found or helped fix -vulnerabilities that are in scope you should submit them to these programs. - -If you have any question with regard to disclosure, please email us at -security@google.com. - ### Code reviews All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. - -### The small print -Contributions made by corporations are covered by a different agreement than -the one above, the -[Software Grant and Corporate Contributor License Agreement] -(https://cla.developers.google.com/about/google-corporate).
\ No newline at end of file @@ -1,6 +1,6 @@ # Project Wycheproof -https://github.com/google/wycheproof +https://github.com/c2sp/wycheproof *Project Wycheproof is named after [Mount Wycheproof](https://en.wikipedia.org/wiki/Mount_Wycheproof), the smallest @@ -16,11 +16,8 @@ climb it.* ## Introduction -Project Wycheproof tests crypto libraries against known attacks. It is developed -and maintained by members of Google Security Team, but it is not an official -Google product. +Project Wycheproof tests crypto libraries against known attacks. -At Google, we rely on many third party cryptographic software libraries. Unfortunately, in cryptography, subtle mistakes can have catastrophic consequences, and we found that libraries fall into such implementation pitfalls much too often and for much too long. Good implementation guidelines, @@ -226,7 +223,7 @@ Project Wycheproof: ### Maintainers -Project Wycheproof is maintained by: +Project Wycheproof has been maintained by: * Daniel Bleichenbacher * Thai Duong |