Table of contents
Combined revision comparison
This section contains a description of the method of authenticating VPN client computers that connect to the SoftEther VPN Server in the previous item #2.2User Authentication#. . Server authentication is oppositely the function whereby the VPN Server verifies that the VPN client computer (VPN client or VPN Server / VPN Bridge that conducts cascade connection) that attempts to connect to the SoftEther VPN Server is authentic. Because server authentication is not needed for conventional operation, it is off by default, but can be enabled for each client connection setting or cascade connection setting.
...
Server authentication by certificate verifies that the connection destination VPN Server is authentic by verifying the certificate, the opposite role of client certificate authentication such as described in 2.2 User Authentication#2.2.5#. . The connection destination VPN Server possesses an X.509 certificate and corresponding private key data, and the VPN client computer (VPN client or VPN Server / VPN Bridge that conducts cascade connection) that attempts to connect to VPN Server determines if the connection destination VPN Server can be trusted by the contents of the certificate. Because an RSA algorithm is used for verifying the certificate, the VPN Server must have a private key that corresponds to the certificate.
...
Version from 03:36, 2 Mar 2013
This section contains a description of the method of authenticating VPN client computers that connect to the SoftEther VPN Server in the previous item #2.2#. Server authentication is oppositely the function whereby the VPN Server verifies that the VPN client computer (VPN client or VPN Server / VPN Bridge that conducts cascade connection) that attempts to connect to the SoftEther VPN Server is authentic. Because server authentication is not needed for conventional operation, it is off by default, but can be enabled for each client connection setting or cascade connection setting.
...
Server authentication by certificate verifies that the connection destination VPN Server is authentic by verifying the certificate, the opposite role of client certificate authentication such as described in #2.2.5#. The connection destination VPN Server possesses an X.509 certificate and corresponding private key data, and the VPN client computer (VPN client or VPN Server / VPN Bridge that conducts cascade connection) that attempts to connect to VPN Server determines if the connection destination VPN Server can be trusted by the contents of the certificate. Because an RSA algorithm is used for verifying the certificate, the VPN Server must have a private key that corresponds to the certificate.
...
Version as of 16:19, 4 Mar 2013
This section contains a description of the method of authenticating VPN client computers that connect to the SoftEther VPN Server in the previous item 2.2User Authentication. Server authentication is oppositely the function whereby the VPN Server verifies that the VPN client computer (VPN client or VPN Server / VPN Bridge that conducts cascade connection) that attempts to connect to the SoftEther VPN Server is authentic. Because server authentication is not needed for conventional operation, it is off by default, but can be enabled for each client connection setting or cascade connection setting.
...
Server authentication by certificate verifies that the connection destination VPN Server is authentic by verifying the certificate, the opposite role of client certificate authentication such as described in 2.2 User Authentication. The connection destination VPN Server possesses an X.509 certificate and corresponding private key data, and the VPN client computer (VPN client or VPN Server / VPN Bridge that conducts cascade connection) that attempts to connect to VPN Server determines if the connection destination VPN Server can be trusted by the contents of the certificate. Because an RSA algorithm is used for verifying the certificate, the VPN Server must have a private key that corresponds to the certificate.
...
