-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[CF1] KEXalgo support list #20132
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
Merged
Merged
[CF1] KEXalgo support list #20132
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,7 +3,6 @@ pcx_content_type: concept | |
| title: Non-HTTP applications | ||
| sidebar: | ||
| order: 1 | ||
|
|
||
| --- | ||
|
|
||
| Cloudflare offers both client-based and clientless ways to grant secure access to non-HTTP applications. | ||
|
|
@@ -17,6 +16,7 @@ Non-HTTP applications require [connecting your private network](/cloudflare-one/ | |
| Users can connect by installing the Cloudflare WARP client on their device and enrolling in your Zero Trust organization. Remote devices connect to your applications as if they were on your private network. By default, all devices enrolled in your organization can access any private route unless they are protected by an Access policy or Gateway firewall rule. To secure the application, you can [create a self-hosted application](/cloudflare-one/applications/non-http/self-hosted-private-app/) for a private IP range, port range, and/or hostname and build [Access policies](/cloudflare-one/policies/access/) that allow or block specific users. | ||
|
|
||
| If you would like to define how users access specific infrastructure servers within your network, [create an infrastructure application](/cloudflare-one/applications/non-http/infrastructure-apps/) in Access for Infrastructure. Access for Infrastructure provides an additional layer of control and visibility over how users access non-HTTP applications, including: | ||
|
|
||
| - Define fine-grained policies to govern who has access to specific servers and exactly how a user may access that server. | ||
| - Eliminate SSH keys by using short-lived certificates to authenticate users. | ||
| - Export SSH command logs to a storage service or SIEM solution using [Logpush](/cloudflare-one/insights/logs/logpush/). | ||
|
|
@@ -29,6 +29,14 @@ Clientless access methods are suited for organizations that cannot deploy the WA | |
|
|
||
| Cloudflare's [browser-based terminal](/cloudflare-one/applications/non-http/browser-rendering/) allows users to connect over SSH and VNC without any configuration. When users visit the public hostname URL (for example, `https://ssh.example.com`) and log in with their Access credentials, Cloudflare will render a terminal in their browser. | ||
|
|
||
| When connecting over SSH, Cloudflare supports following key exchange algorithms: | ||
|
|
||
| - [email protected] | ||
| - curve25519-sha256 | ||
| - ecdh-sha2-nistp256 | ||
| - ecdh-sha2-nistp384 | ||
| - ecdh-sha2-nistp521 | ||
|
|
||
| ### Client-side cloudflared (legacy) | ||
|
|
||
| :::note | ||
|
|
@@ -41,6 +49,6 @@ Users can log in to the application by installing `cloudflared` on their device | |
|
|
||
| To connect to an application over a specific protocol, refer to these tutorials: | ||
|
|
||
| * [SSH](/cloudflare-one/connections/connect-networks/use-cases/ssh/) | ||
| * [SMB](/cloudflare-one/connections/connect-networks/use-cases/smb/) | ||
| * [RDP](/cloudflare-one/connections/connect-networks/use-cases/rdp/) | ||
| - [SSH](/cloudflare-one/connections/connect-networks/use-cases/ssh/) | ||
| - [SMB](/cloudflare-one/connections/connect-networks/use-cases/smb/) | ||
| - [RDP](/cloudflare-one/connections/connect-networks/use-cases/rdp/) | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @deadlypants1973, if this is specific to browser-rendered SSH, I'd recommend moving this info to https://developers.cloudflare.com/cloudflare-one/applications/non-http/browser-rendering/. We changed up the IA recently to make the non-HTTP page a general overview page.