@@ -14,11 +14,11 @@ as UTM services, for deep SSL inspection. But it can handle unencrypted
1414network traffic as well.
1515
1616[ The UTMFW project] ( https://github.com/sonertari/UTMFW ) uses SSLproxy to
17- decyrpt and feed network traffic into its UTM services: Web Filter, POP3
18- Proxy, SMTP Proxy, and Inline IPS; and also indirectly into Virus Scanner and
19- Spam Filter through those UTM software. Given that most of the Internet
20- traffic is encrypted now, without SSLproxy it wouldn't be possible to deeply
21- inspect most of the network traffic passing through UTMFW.
17+ decrypt and feed network traffic into its UTM services: Web Filter, POP3 Proxy,
18+ SMTP Proxy, and Inline IPS; and also indirectly into Virus Scanner and Spam
19+ Filter through those UTM software. Given that most of the Internet traffic is
20+ encrypted now, without SSLproxy it wouldn't be possible to deeply inspect most
21+ of the network traffic passing through UTMFW.
2222
2323See [ this presentation] ( https://drive.google.com/open?id=12YaGIGs0-xfpqMNAY3rzUbIyed-Tso8W )
2424for a summary of SSL interception and potential issues with middleboxes that
@@ -50,7 +50,7 @@ communication occurs over networking sockets.
5050SSLproxy supports split mode of operation similar to SSLsplit as well. In
5151split mode, packets are not diverted to listening programs, effectively making
5252SSLproxy behave similar to SSLsplit, but not exactly like it, because SSLproxy
53- has certain features non-existent in SSLsplit, such as user authentication,
53+ has certain features nonexistent in SSLsplit, such as user authentication,
5454protocol validation, and filtering rules. Also, note that the implementation
5555of the proxy core in SSLproxy is different from the one in SSLsplit; for
5656example, the proxy core in SSLproxy runs lockless, whereas SSLsplit
@@ -253,7 +253,7 @@ normally prevent MitM attacks or make them more difficult. SSLproxy can deny
253253OCSP requests in a generic way. For HTTP and HTTPS connections, SSLproxy
254254mangles headers to prevent server-instructed public key pinning (HPKP), avoid
255255strict transport security restrictions (HSTS), avoid Certificate Transparency
256- enforcement (Expect-CT) and prevent switching to QUIC/SPDY, HTTP/2 or
256+ enforcement (Expect-CT), and prevent switching to QUIC/SPDY, HTTP/2 or
257257WebSockets (Upgrade, Alternate Protocols). HTTP compression, encodings and
258258keep-alive are disabled to make the logs more readable.
259259
@@ -349,7 +349,7 @@ user record with the current system time. If the difference is greater than
349349the value configured by the UserTimeout option, the connection is redirected
350350to the login page.
351351
352- If the connection passes all these checks, SSLproxy proceeds with establishing
352+ If the connection passes all those checks, SSLproxy proceeds with establishing
353353the connection.
354354
355355The atime of the IP address in the users table is updated with the system time
@@ -358,7 +358,7 @@ using a privsep command, it is expensive. So, to reduce the frequency of such
358358updates, it is deferred until after the user idle time is more than half of
359359the timeout period.
360360
361- If a description text is provided in the DESC field, it can be used with
361+ If a description text is provided in the DESC field, it can be used in
362362filtering rules to treat the user logged in from different locations, i.e.
363363from different client IP addresses, differently.
364364
0 commit comments