Repository: mina-sshd Updated Branches: refs/heads/master 4aef497ee -> b737b07d2
[SSHD-766] Fixed README.md documentation to reflect new forwarding filter strcuture Project: http://git-wip-us.apache.org/repos/asf/mina-sshd/repo Commit: http://git-wip-us.apache.org/repos/asf/mina-sshd/commit/b737b07d Tree: http://git-wip-us.apache.org/repos/asf/mina-sshd/tree/b737b07d Diff: http://git-wip-us.apache.org/repos/asf/mina-sshd/diff/b737b07d Branch: refs/heads/master Commit: b737b07d251479dd186ce877cad5b0d13b9bb054 Parents: 756a9c6 Author: Lyor Goldstein <lyor.goldst...@gmail.com> Authored: Thu Sep 21 08:46:25 2017 +0300 Committer: Lyor Goldstein <lyor.goldst...@gmail.com> Committed: Thu Sep 21 08:47:13 2017 +0300 ---------------------------------------------------------------------- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/mina-sshd/blob/b737b07d/README.md ---------------------------------------------------------------------- diff --git a/README.md b/README.md index 0f53709..260c024 100644 --- a/README.md +++ b/README.md @@ -750,7 +750,7 @@ One can skip all the conditional code if a specific known extension is required: ### Standard port forwarding -Port forwarding as specified in [RFC 4254 - section 7](https://tools.ietf.org/html/rfc4254#section-7) is fully supported by the client and server. From the client side, this capability is exposed via the `start/stopLocal/RemotePortForwarding` method. The key player in this capability is the configured `ForwardingFilter` that controls this feature - on **both** sides - client and server. By default, this capability is **disabled** - i.e., the user must provide an implementation and call the appropriate `setTcpipForwardingFilter` method on the client/server. +Port forwarding as specified in [RFC 4254 - section 7](https://tools.ietf.org/html/rfc4254#section-7) is fully supported by the client and server. From the client side, this capability is exposed via the `start/stopLocal/RemotePortForwarding` method. The key player in this capability is the configured `ForwardingFilter` that controls this feature - on **both** sides - client and server. By default, this capability is **disabled** - i.e., the user must provide an implementation and call the appropriate `setForwardingFilter` method on the client/server. The code contains 2 simple implementations - an accept-all and a reject-all one that can be used for these trivial policies. **Note:** setting a _null_ filter is equivalent to rejecting all such attempts.
