Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: gorilla/securecookie
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.1.1
Choose a base ref
...
head repository: gorilla/securecookie
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.1.2
Choose a head ref
  • 19 commits
  • 152 files changed
  • 10 contributors

Commits on May 18, 2018

  1. [bugfix] check for an empty hashKey (#52) 

    this scenario might occur when converting from an empty string to
byte slice, such as when reading from a configuration file.
    @Wessie @elithrar
    Wessie authored and elithrar committed May 18, 2018
    Configuration menu
    Copy the full SHA
    b009e17 View commit details
    Browse the repository at this point in the history

Commits on Jun 8, 2018

  1. Update LICENSE & AUTHORS files (#54)

    @elithrar
    elithrar authored Jun 8, 2018
    Configuration menu
    Copy the full SHA
    78f3d31 View commit details
    Browse the repository at this point in the history

Commits on Aug 27, 2018

  1. Create go.mod to be aware of go modules (#55)

    @flibustenet @elithrar
    flibustenet authored and elithrar committed Aug 27, 2018
    Configuration menu
    Copy the full SHA
    51f4719 View commit details
    Browse the repository at this point in the history

Commits on Aug 30, 2018

  1. Create release_drafter.yml (#57)

    @elithrar
    elithrar authored Aug 30, 2018
    Configuration menu
    Copy the full SHA
    3a8eb0d View commit details
    Browse the repository at this point in the history

Commits on Sep 13, 2018

  1. [docs] Clarify usage of GenerateRandomKey

    Matt Silverlock committed Sep 13, 2018
    Configuration menu
    Copy the full SHA
    1aeabd1 View commit details
    Browse the repository at this point in the history

  2. [docs] Add note RE: persistence to GenerateRandomKey

    Matt Silverlock committed Sep 13, 2018
    Configuration menu
    Copy the full SHA
    1112382 View commit details
    Browse the repository at this point in the history

  3. Merge pull request #58 from gorilla/elithrar/generaterandomkey-docs 

    [docs] Clarify usage of GenerateRandomKey
    @kisielk
    kisielk authored Sep 13, 2018
    Configuration menu
    Copy the full SHA
    bb1ab76 View commit details
    Browse the repository at this point in the history

Commits on Oct 10, 2018

  1. github: remove false-match for language detection

    Steve Manuel committed Oct 10, 2018
    Configuration menu
    Copy the full SHA
    2a3375f View commit details
    Browse the repository at this point in the history

  2. Merge pull request #59 from nilslice/sm/gitattrs 

    github: remove false-match for language detection
    @kisielk
    kisielk authored Oct 10, 2018
    Configuration menu
    Copy the full SHA
    e65cf8c View commit details
    Browse the repository at this point in the history

Commits on Jun 27, 2019

  1. Create config.yml (#63) 

    * Create config.yml

* Delete .travis.yml
    @elithrar
    elithrar authored Jun 27, 2019
    Configuration menu
    Copy the full SHA
    629b6af View commit details
    Browse the repository at this point in the history

Commits on Jul 7, 2019

  1. doc: correct a reference to block size that was meant to be key size (#… 

    …64)

The AES block size is always the same, it's the key size that selects AES-128, AES-192, or AES-256.
    @FiloSottile @elithrar
    FiloSottile authored and elithrar committed Jul 7, 2019
    Configuration menu
    Copy the full SHA
    8645062 View commit details
    Browse the repository at this point in the history

Commits on Oct 28, 2019

  1. docs: Include an example for using DecodeMulti in the Readme (#69) 

    * Include an example for using DecodeMulti in the Readme

* Put warning in as code comment
    @tflyons @elithrar
    tflyons authored and elithrar committed Oct 28, 2019
    Configuration menu
    Copy the full SHA
    61b4ad1 View commit details
    Browse the repository at this point in the history

Commits on Sep 12, 2020

  1. build: use build matrix; drop Go <= 1.10 (#74)

    @elithrar
    elithrar authored Sep 12, 2020
    Configuration menu
    Copy the full SHA
    f37875e View commit details
    Browse the repository at this point in the history

Commits on Dec 9, 2022

  1. archive mode

    @elithrar
    elithrar authored Dec 9, 2022
    Configuration menu
    Copy the full SHA
    9865a2b View commit details
    Browse the repository at this point in the history

Commits on Jul 15, 2023

  1. Update README.md 

    Signed-off-by: Corey Daley <cdaley@redhat.com>
    Corey Daley authored Jul 15, 2023
    Configuration menu
    Copy the full SHA
    80d3cb3 View commit details
    Browse the repository at this point in the history

  2. Merge pull request #78 from gorilla/coreydaley-patch-1 

    Update README.md
    Corey Daley authored Jul 15, 2023
    Configuration menu
    Copy the full SHA
    ab6b808 View commit details
    Browse the repository at this point in the history

Commits on Jul 29, 2023

  1. docs: changed deprecated goo.gl links to their unshortened variant (#77) 

    Unshortened the links in the docs because 
1. goo.gl is a deprecated service 
2. being able to see the actual link is more verbose thus more useful
inside of docs

Co-authored-by: Corey Daley <cdaley@redhat.com>
    @vvvvv
    vvvvv and Corey Daley authored Jul 29, 2023
    Configuration menu
    Copy the full SHA
    4ce5252 View commit details
    Browse the repository at this point in the history

Commits on Jul 31, 2023

  1. Update go version & add verification/testing tools (#81) 

    <!--
For Work In Progress Pull Requests, please use the Draft PR feature,
see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for
further details.

     For a timely review/response, please avoid force-pushing additional
     commits if your PR already received reviews or comments.

     Before submitting a Pull Request, please ensure that you have:
- 📖 Read the Contributing guide:
https://github.com/gorilla/.github/blob/main/CONTRIBUTING.md
- 📖 Read the Code of Conduct:
https://github.com/gorilla/.github/blob/main/CODE_OF_CONDUCT.md

     - Provide tests for your changes.
     - Use descriptive commit messages.
	 - Comment your code where appropriate.
	 - Squash your commits
     - Update any related documentation.

     - Add gorilla/pull-request-reviewers as a Reviewer
-->

## What type of PR is this? (check all applicable)

- [ ] Refactor
- [ ] Feature
- [ ] Bug Fix
- [x] Optimization
- [ ] Documentation Update

## Description

## Related Tickets & Documents

<!--
For pull requests that relate or close an issue, please include them
below. We like to follow [Github's guidance on linking issues to pull
requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).

For example having the text: "closes #1234" would connect the current
pull
request to issue 1234.  And when we merge the pull request, Github will
automatically close the issue.
-->

- Related Issue #
- Closes #

## Added/updated tests?

- [ ] Yes
- [ ] No, and this is why: _please replace this line with details on why
tests
      have not been included_
- [ ] I need help with writing tests

## Run verifications and test

- [ ] `make verify` is passing
- [ ] `make test` is passing
    Corey Daley authored Jul 31, 2023
    Configuration menu
    Copy the full SHA
    22eae5c View commit details
    Browse the repository at this point in the history

Commits on Oct 18, 2023

  1. update GitHub workflows (#82) 

    <!--
For Work In Progress Pull Requests, please use the Draft PR feature,
see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for
further details.

     For a timely review/response, please avoid force-pushing additional
     commits if your PR already received reviews or comments.

     Before submitting a Pull Request, please ensure that you have:
- 📖 Read the Contributing guide:
https://github.com/gorilla/.github/blob/main/CONTRIBUTING.md
- 📖 Read the Code of Conduct:
https://github.com/gorilla/.github/blob/main/CODE_OF_CONDUCT.md

     - Provide tests for your changes.
     - Use descriptive commit messages.
	 - Comment your code where appropriate.
	 - Squash your commits
     - Update any related documentation.

     - Add gorilla/pull-request-reviewers as a Reviewer
-->

## What type of PR is this? (check all applicable)

- [x] Refactor
- [ ] Feature
- [ ] Bug Fix
- [ ] Optimization
- [ ] Documentation Update
- [ ] Go Version Update
- [ ] Dependency Update

## Description

## Related Tickets & Documents

<!--
For pull requests that relate or close an issue, please include them
below. We like to follow [Github's guidance on linking issues to pull
requests](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue).

For example having the text: "closes #1234" would connect the current
pull
request to issue 1234.  And when we merge the pull request, Github will
automatically close the issue.
-->

- Related Issue #
- Closes #

## Added/updated tests?

- [ ] Yes
- [ ] No, and this is why: _please replace this line with details on why
tests
      have not been included_
- [ ] I need help with writing tests

## Run verifications and test

- [x] `make verify` is passing
- [x] `make test` is passing
    Corey Daley authored Oct 18, 2023
    Configuration menu
    Copy the full SHA
    eae3c18 View commit details
    Browse the repository at this point in the history
Loading