You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mina.apache.org by gn...@apache.org on 2024/09/27 20:26:36 UTC
(mina-sshd) branch master updated: Add changelog for 2.14.0
This is an automated email from the ASF dual-hosted git repository.
gnodet pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mina-sshd.git
The following commit(s) were added to refs/heads/master by this push:
new 4748eae48 Add changelog for 2.14.0
4748eae48 is described below
commit 4748eae48f95237c16f97162d291ec9eb61717a9
Author: Guillaume Nodet <gn...@gmail.com>
AuthorDate: Tue Sep 24 10:57:41 2024 +0200
Add changelog for 2.14.0
---
CHANGES.md | 76 +-----------------------------------
CHANGES.md => docs/changes/2.14.0.md | 44 ++-------------------
2 files changed, 6 insertions(+), 114 deletions(-)
diff --git a/CHANGES.md b/CHANGES.md
index 124a70664..c2133d509 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -34,87 +34,15 @@
# [Version 2.13.1 to 2.13.2](./docs/changes/2.13.2.md)
+# [Version 2.13.1 to 2.14.0](./docs/changes/2.14.0.md)
+
# Planned for next version
## Bug Fixes
-* [GH-524](https://github.com/apache/mina-sshd/issues/524) Performance improvements
-* [GH-533](https://github.com/apache/mina-sshd/issues/533) Fix multi-step authentication
-* [GH-582](https://github.com/apache/mina-sshd/issues/582) Fix filtering in `NamedFactory`
-* [GH-587](https://github.com/apache/mina-sshd/issues/587) Prevent `NullPointerException`on closed channel in `NettyIoSession`
-* [GH-590](https://github.com/apache/mina-sshd/issues/590) Better support for FIPS
-* [GH-597](https://github.com/apache/mina-sshd/issues/597) Pass on `Charset` in `ClientSession.executeRemoteCommand()`
-
## New Features
-* New utility methods `SftpClient.put(Path localFile, String remoteFileName)` and
-`SftpClient.put(InputStream in, String remoteFileName)` facilitate SFTP file uploading.
-
-### [GH-590](https://github.com/apache/mina-sshd/issues/590) Better support for FIPS
-
-Besides fixing a bug with bc-fips (the `RandomGenerator` class exists in normal Bouncy Castle,
-but not in the FIPS version, but Apache MINA sshd referenced it even if only bc-fips was present),
-support was improved for running in an environment restricted by FIPS.
-
-There is a new system property `org.apache.sshd.security.fipsEnabled`. If set to `true`, a number
-of crypto-algorithms not approved by FIPS 140 are disabled:
-
-* key exchange methods sntrup761x25519-sha512, sntrup761x25519-sha512<!-- -->@openssh.com, curve25519-sha256, curve25519-sha256<!-- -->@libssh.org, curve448-sha512.
-* the chacha20-poly1305 cipher.
-* the bcrypt KDF used in encrypted private key files in [OpenSSH format](https://github.com/openssh/openssh-portable/blob/master/PROTOCOL.key).
-* all ed25519 keys and signatures.
-
-Additionally, the new "SunJCEWrapper" `SecurityProviderRegistrar` (see below) and the
-`EdDSASecurityProviderRegistrar` are disabled, and the `BouncyCastleScurityProviderRegistrar`
-looks only for the "BCFIPS" security provider, not for the normal "BC" provider.
-
-If the system property is _not_ set to `true`, FIPS mode can be enabled programmatically
-by calling `SecurityUtils.setFipsMode()` before any other call to Apache MINA sshd.
-
## Potential compatibility issues
-### New security provider registrar
-There is a new `SecurityProviderRegistrar` that is registered by default
-if there is a `SunJCE` security provider. It uses the AES and
-HmacSHA* implementations from `SunJCE` even if Bouncy Castle is also
-registered. `SunJCE` has native implementations, whereas Bouncy Castle
-may not.
-
-The new registrar has the name "SunJCEWrapper" and can be configured
-like any other registrar. It can be disabled via the system property
-`org.apache.sshd.security.provider.SunJCEWrapper.enabled=false`. It is also
-disabled in FIPS mode (see above).
-
-### [GH-582](https://github.com/apache/mina-sshd/issues/582) Fix filtering in `NamedFactory`
-
-The methods `NamedFactory.setupBuiltinFactories(boolean ignoreUnsupported, ...)` and
-`NamedFactory.setupTransformedFactories(boolean ignoreUnsupported, ...)` had a bug that
-gave the "ignoreUnsupported" parameter actually the meaning of "include unsupported".
-
-This was fixed in this release, but existing code calling these or one of the following methods:
-
-* `BaseBuilder.setUpDefaultMacs(boolean ignoreUnsupported)`
-* `BaseBuilder.setUpDefaultCiphers(boolean ignoreUnsupported)`
-* `ClientBuilder.setUpDefaultCompressionFactories(boolean ignoreUnsupported)`
-* `ClientBuilder.setUpDefaultKeyExchanges(boolean ignoreUnsupported)`
-* `ClientBuilder.setUpDefaultSignatureFactories(boolean ignoreUnsupported)`
-* `ServerBuilder.setUpDefaultCompressionFactories(boolean ignoreUnsupported)`
-* `ServerBuilder.setUpDefaultKeyExchanges(boolean ignoreUnsupported)`
-* `ServerBuilder.setUpDefaultSignatureFactories(boolean ignoreUnsupported)`
-* any of the methods starting with `SshConfigFileReader.configure`
-* `SshClientConfigFileReader.configure(...)`
-* `SshServerConfigFileReader.configure(...)`
-
-should be reviewed:
-
-* if the method is called with parameter value `true`, the result will no longer include unsupported algorithms. Formerly it wrongly did.
-* if the method is called with parameter value `false`, the result may include unsupported algorithms. Formerly it did not.
-
-So if existing code used parameter value `false` to ensure it never got unsupported algorithms, change it to `true`.
-
## Major Code Re-factoring
-### JDK requirements
-
-* [GH-536](https://github.com/apache/mina-sshd/issues/536) The project now requires
-JDK 17 at build time, while the target runtime still remains unchanged to support JDK 8.
diff --git a/CHANGES.md b/docs/changes/2.14.0.md
similarity index 78%
copy from CHANGES.md
copy to docs/changes/2.14.0.md
index 124a70664..79f807061 100644
--- a/CHANGES.md
+++ b/docs/changes/2.14.0.md
@@ -1,40 +1,4 @@
-# [Version 2.1.0 to 2.2.0](./docs/changes/2.2.0.md)
-
-# [Version 2.2.0 to 2.3.0](./docs/changes/2.3.0.md)
-
-# [Version 2.3.0 to 2.4.0](./docs/changes/2.4.0.md)
-
-# [Version 2.4.0 to 2.5.0](./docs/changes/2.5.0.md)
-
-# [Version 2.5.0 to 2.5.1](./docs/changes/2.5.1.md)
-
-# [Version 2.5.1 to 2.6.0](./docs/changes/2.6.0.md)
-
-# [Version 2.6.0 to 2.7.0](./docs/changes/2.7.0.md)
-
-# [Version 2.7.0 to 2.8.0](./docs/changes/2.8.0.md)
-
-# [Version 2.8.0 to 2.9.0](./docs/changes/2.9.0.md)
-
-# [Version 2.9.0 to 2.9.1](./docs/changes/2.9.1.md)
-
-# [Version 2.9.1 to 2.9.2](./docs/changes/2.9.2.md)
-
-# [Version 2.9.2 to 2.10.0](./docs/changes/2.10.0.md)
-
-# [Version 2.10.0 to 2.11.0](./docs/changes/2.11.0.md)
-
-# [Version 2.11.0 to 2.12.0](./docs/changes/2.12.0.md)
-
-# [Version 2.12.0 to 2.12.1](./docs/changes/2.12.1.md)
-
-# [Version 2.12.1 to 2.13.0](./docs/changes/2.13.0.md)
-
-# [Version 2.13.0 to 2.13.1](./docs/changes/2.13.1.md)
-
-# [Version 2.13.1 to 2.13.2](./docs/changes/2.13.2.md)
-
-# Planned for next version
+# Introduced in 2.14.0
## Bug Fixes
@@ -48,12 +12,12 @@
## New Features
* New utility methods `SftpClient.put(Path localFile, String remoteFileName)` and
-`SftpClient.put(InputStream in, String remoteFileName)` facilitate SFTP file uploading.
+ `SftpClient.put(InputStream in, String remoteFileName)` facilitate SFTP file uploading.
### [GH-590](https://github.com/apache/mina-sshd/issues/590) Better support for FIPS
Besides fixing a bug with bc-fips (the `RandomGenerator` class exists in normal Bouncy Castle,
-but not in the FIPS version, but Apache MINA sshd referenced it even if only bc-fips was present),
+but not in the FIPS version, but Apache MINA sshd referenced it even if only bc-fips was present),
support was improved for running in an environment restricted by FIPS.
There is a new system property `org.apache.sshd.security.fipsEnabled`. If set to `true`, a number
@@ -117,4 +81,4 @@ So if existing code used parameter value `false` to ensure it never got unsuppor
### JDK requirements
* [GH-536](https://github.com/apache/mina-sshd/issues/536) The project now requires
-JDK 17 at build time, while the target runtime still remains unchanged to support JDK 8.
+ JDK 17 at build time, while the target runtime still remains unchanged to support JDK 8.