Bump bcprov-jdk15on from 1.60 to 1.61

[dependabot-preview]

Bumps bcprov-jdk15on from 1.60 to 1.61.

Changelog

Sourced from bcprov-jdk15on's changelog.

<title>Bouncy Castle Crypto Package - Release Notes</title>

Bouncy Castle Crypto Package - Release Notes

1.0 Introduction

The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. The package is organised so that it contains a light-weight API suitable for use in any environment (including the J2ME) with the additional infrastructure to conform the algorithms to the JCE framework.

2.0 Release History

2.1.1 Version

Release: 1.61
Date:      2019, February 4th.

2.1.2 Defects Fixed

• Use of EC named curves could be lost if keys were constructed via a key factory and algorithm parameters. This has been fixed.
• RFC3211WrapEngine would not properly handle messages longer than 127 bytes. This has been fixed.
• The JCE implementations for RFC3211 would not return null AlgorithmParameters. This has been fixed.
• TLS: Don't check CCS status for hello_request.
• TLS: Tolerate unrecognized hash algorithms.
• TLS: Tolerate unrecognized SNI types.
• An incompatibility issue in ECIES-KEM encryption in cofactor mode has been fixed.
• An issue with XMSS/XMSSMT private key loading which could result in invalid signatures has been fixed.
• StateAwareSignature.isSigningCapable() now returns false when the key has reached it's maximum number of signatures.
• The McEliece KeyPairGenerator was failing to initialize the underlying class if a SecureRandom was explicitly passed.
• The McEliece cipher would sometimes report the wrong value on a call to Cipher.getOutputSize(int). This has been fixed.
• CSHAKEDigest.leftEncode() was using the wrong endianness for multi byte values. This has been fixed.
• Some ciphers, such as CAST6, were missing AlgorithmParameters implementations. This has been fixed.
• An issue with the default "m" parameter for 1024 bit Diffie-Hellman keys which could result in an exception on key pair generation has been fixed.
• The SPHINCS256 implementation is now more tolerant of parameters wrapped with a SecureRandom and will not throw an exception if it receives one.
• A regression in PGPUtil.writeFileToLiteralData() which could cause corrupted literal data has been fixed.
• Several parsing issues related to the processing of CMP PKIPublicationInfo have been fixed.
• The ECGOST curves for id-tc26-gost-3410-12-256-paramSetA and id-tc26-gost-3410-12-512-paramSetC had incorrect co-factors. These have been fixed.

2.1.3 Additional Features and Functionality

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.