View Attach (4) Info

Add new attachment

Only authorized users are allowed to upload new attachments.

List of attachments

Kind Attachment Name Size Version Date Modified Author Change note
png
 dmz_port.png 54.9 kB 2 29-Dec-2020 05:25 Ben Spink
png
 dmz_publickey.png 13.9 kB 1 29-Dec-2020 05:25 Ben Spink
png
 dmz_selector.png 30.3 kB 1 29-Dec-2020 05:25 Ben Spink
png
 dmz_user.png 57.6 kB 3 29-Dec-2020 05:25 Ben Spink

This page (revision-35) was last changed on 20-May-2022 03:33 by Ben Spink

This page was created on 29-Dec-2020 05:25 by Ben Spink

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 3 added 5 lines
When a connection comes into the DMZ server over SFTP/FTP(es)/HTTP(s)/WebDAV(s), the DMZ server talks to the internal server on an existing connection it already has from the internal server. This communication is over a SSL socket always initiated from the internal to the DMZ. The protocol the DMZ then uses inside this secure connection is HTTP. The internal server then attaches the connection to the first HTTP (not HTTPS) port internally that it finds in its list of ports.
So all interaction between DMZ and Internal is the HTTP protocol (inside a SSL connection). The user may be using SFTP to connect to the DMZ, and ask for a directory listing. This then results in the DMZ asking the internal server for a dir listing using HTTP, and then its translated and delivered to the SFTP client as a SFTP dir listing. This way all protocols are handled by the DMZ, and the internal server does everything using one protocol that can handle everything.
----
At line 38 removed 4 lines
When a connection comes into the DMZ server over SFTP/FTP(es)/HTTP(s)/WebDAV(s), the DMZ server talks to the internal server on an existing connection it already has from the internal server. This communication is over a SSL socket always initiated from the internal to the DMZ. The protocol the DMZ then uses inside this secure connection is HTTP. The internal server then attaches the connection to the first HTTP (not HTTPS) port internally that it finds in its list of ports.
So all interaction between DMZ and Internal is the HTTP protocol (inside a SSL connection). The user may be using SFTP to connect to the DMZ, and ask for a directory listing. This then results in the DMZ asking the internal server for a dir listing using HTTP, and then its translated and delivered to the SFTP client as a SFTP dir listing. This way all protocols are handled by the DMZ, and the internal server does everything using one protocol that can handle everything.
----
Version Date Modified Size Author Changes ... Change note
35 20-May-2022 03:33 8.975 kB Ben Spink to previous
34 05-Mar-2021 02:04 8.881 kB Ben Spink to previous | to last
33 05-Mar-2021 02:03 8.89 kB Ben Spink to previous | to last
32 05-Mar-2021 02:02 8.969 kB Ben Spink to previous | to last
31 29-Dec-2020 05:25 7.887 kB Ben Spink to previous | to last
30 29-Dec-2020 05:25 5.528 kB Halmágyi Árpád to previous | to last
29 29-Dec-2020 05:25 5.527 kB Halmágyi Árpád to previous | to last
28 29-Dec-2020 05:25 5.416 kB Ada Csaba to previous | to last
27 29-Dec-2020 05:25 5.414 kB Ada Csaba to previous | to last
26 29-Dec-2020 05:25 4.72 kB Ben Spink to previous | to last
25 29-Dec-2020 05:25 4.639 kB Ben Spink to previous | to last
24 29-Dec-2020 05:25 4.654 kB Ben Spink to previous | to last
23 29-Dec-2020 05:25 4.644 kB Ben Spink to previous | to last
22 29-Dec-2020 05:25 4.648 kB Halmágyi Árpád to previous | to last
21 29-Dec-2020 05:25 4.64 kB Ben Spink to previous | to last
« This page (revision-35) was last changed on 20-May-2022 03:33 by Ben Spink
G’day (anonymous guest)
CrushFTP10 | What's New

Referenced by
CrushOAuth
Enterprise License Enhancements
Google Authenticator
High Availability
LeftMenu
User Manager

JSPWiki