diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 02edf9b..334a9da 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -2,7 +2,7 @@ name: Rust CI on: push: branches: - - master + - main pull_request: types: [opened, repoened, synchronize] diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0548d4d..f4043ae 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -5,7 +5,7 @@ possible. ## Pull Requests We actively welcome your pull requests. -1. Fork the repo and create your branch from `master`. +1. Fork the repo and create your branch from `main`. 2. If you've added code that should be tested, add tests. 3. If you've changed APIs, update the documentation. 4. Ensure the test suite passes. diff --git a/src/lib.rs b/src/lib.rs index ece3473..45620a2 100644 --- a/src/lib.rs +++ b/src/lib.rs @@ -35,7 +35,7 @@ //! type SlowHash = opaque_ke::slow_hash::NoOpHash; //! } //! ``` -//! See [examples/simple_login.rs](https://github.com/novifinancial/opaque-ke/blob/master/examples/simple_login.rs) +//! See [examples/simple_login.rs](https://github.com/novifinancial/opaque-ke/blob/main/examples/simple_login.rs) //! for a working example of a simple password-based login using OPAQUE. //! //! Note that our choice of slow hashing function in this example, `NoOpHash`, is selected only to ensure @@ -508,7 +508,7 @@ //! know the password the client uses during registration and login can recover this secret, as it is never exposed to the server. As a result, the export key //! can be used (separately from the OPAQUE protocol) to provide confidentiality and integrity to other data which only the client should be able to process. //! For instance, if the server is expected to maintain any client-side secrets which require a password to access, then this export key can be used to encrypt -//! these secrets so that they remain hidden from the server (see [examples/digital_locker.rs](https://github.com/novifinancial/opaque-ke/blob/master/examples/digital_locker.rs) +//! these secrets so that they remain hidden from the server (see [examples/digital_locker.rs](https://github.com/novifinancial/opaque-ke/blob/main/examples/digital_locker.rs) //! for a working example). //! //! You can access the export key from the `export_key` field of [ClientRegistrationFinishResult] and [ClientLoginFinishResult].