Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certificate issues #514

Closed
wants to merge 9 commits into from

Conversation

aberenguel
Copy link
Contributor

In this work I did some things related to certificates:

  • creation of certificates with SHA-2 signatures
  • use of the new Bouncy Castle API for create certificates
  • reactivating the signing request feature
  • some bug fixes

@guusdk
Copy link
Member

guusdk commented Jan 19, 2016

@guusdk
Copy link
Member

guusdk commented Jan 19, 2016

Thanks for your contribution. This should improve things a lot. I've added some comments inline.

@guusdk
Copy link
Member

guusdk commented Jan 25, 2016

I'm merging this to master, cherry-picking all but the SHA-1 to SHA-2 commit to 4.0 branch. Will follow up to restore the 5-year validity for self-signed certificates.

@guusdk
Copy link
Member

guusdk commented Jan 25, 2016

I have created new pull requests that, combined, contain all of the commits from this pull request.

#526 contains most commits, with an additional commit that restores the 5-year-validity for self-signed certificates.

#527 contains the commit that replaces SHA-1 with SHA-2. Although desirable, we shouldn't have such a change in a patch release.

@guusdk guusdk closed this Jan 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants