From 457409e8a460fa115565a5450e7f4eb4a558f32c Mon Sep 17 00:00:00 2001
From: Raimo Niskanen For SSL to work, at least
- a public key and a certificate must be specified for the server
- side. In the following example, the PEM-files consist of two
- entries, the server certificate and its private key.
+ The SSL distribution options can be written into a file
+ that is consulted when the node is started. This file name
+ is then specified with the command line argument
+
+ Any available SSL option can be specified in an options file,
+ but note that options that take a
+ Do not tamper with the socket options
+
+ For SSL to work, at least a public key and a certificate
+ must be specified for the server side.
+ In the following example, the PEM file
+
+ Create a file named for example
+
+ And then start the node like this
+ (line breaks in the command are for readability,
+ and shall not be there when typed):
+
+ The options in the
+ For the client, the option
+
+ For the server it is also possible to use the option
+
+ A node started in this way is fully functional, using SSL
+ as the distribution protocol.
+
+ As in the previous section the PEM file
+ On the
+
+
+
+
An example command line can now look as follows +
+ An example command line doing the same as the example + in the previous section can now look as follows (line breaks in the command are for readability, - and are not be there when typed):
-
+ and shall not be there when typed):
+
+
- A node started in this way is fully functional, using SSL
- as the distribution protocol.
+(ssl_test@myhost)1>]]>
+
A convenient way to specify arguments to Erlang is to use environment
variable
An example command line with this option would look like this:
-
+
+ -ssl_dist_optfile "/home/me/ssl/ssl_test@myhost.conf"
+ -sname ssl_test]]>
+
A node started in this way will only be able to communicate with other nodes using SSL distribution over IPv6.
-- cgit v1.2.3