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

Merge 3.0.6 back into master #20

Merged
merged 14 commits into from
Feb 15, 2016
Merged

Merge 3.0.6 back into master #20

merged 14 commits into from
Feb 15, 2016

Conversation

andreaceccanti
Copy link
Contributor

No description provided.

Default to TLSv1.2 for VOMS legacy requests.

Issue: https://issues.infn.it/jira/browse/VOMS-653
VOMS Java APIs select SSLv3 for legacy VOMS requests
The CANL Openssl certificate validator can be configured,
at creation time, to use the MD5 or SHA1 function to resolve
trust anchors. MD5 was used in openssl pre 1.x, SHA1 is used
since 1.x. Typically CA trust anchors are packaged in a way
that both hash functions would work, but we should not hide the
possibility of configuring which is the desired behaviour in the
CertificateValidatorBuilder.

Now CertificateValidatorBuilder allows to choose which has function
should be used, via the opensslHashFunction method.

The default hash function is MD5.

Issue: https://issues.infn.it/jira/browse/VOMS-703
andreaceccanti added a commit that referenced this pull request Feb 15, 2016
Merge 3.0.6 back into master
@andreaceccanti andreaceccanti merged commit b33d6cf into master Feb 15, 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
Development

Successfully merging this pull request may close these issues.

None yet

1 participant