raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

DOC: Describe how to use SSL for remoting, see #2407

Browse source
This commit is contained in:
Patrik Nordwall 2012-08-20 17:04:20 +02:00
parent 7b45360b5f
commit 85c212f491
2 changed files with 42 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

37
akka-docs/scala/remoting.rst
View file

@ -45,6 +45,11 @@ As you can see in the example above there are four things you need to add to get
systems have different names. This is because each actor system has its own network subsystem
listening for connections and handling messages as not to interfere with other actor systems.
.. _remoting-scala-configuration:
Remote Configuration
^^^^^^^^^^^^^^^^^^^^
The example above only illustrates the bare minimum of properties you have to add to enable remoting.
There are lots of more properties that are related to remoting in Akka. We refer to the following
reference file for more information:
@ -349,13 +354,7 @@ This will prevent the client to send these messages to the server:
Here is how to turn it on in the config::
akka {
actor {
remote {
untrusted-mode = on
}
}
}
akka.remote.untrusted-mode = on
Secure Cookie Handshake
-----------------------
@ -373,13 +372,19 @@ as the ``require-cookie`` option turned on.
Here is an example config::
akka {
actor {
remote {
netty {
secure-cookie = "090A030E0F0A05010900000A0C0E0C0B03050D05"
require-cookie = on
}
}
}
akka.remote.netty {
secure-cookie = "090A030E0F0A05010900000A0C0E0C0B03050D05"
require-cookie = on
}
SSL
---
SSL can be used for the remote transport by activating the ``akka.remote.netty.ssl``
configuration section. See description of the settings in the :ref:`remoting-scala-configuration`.
.. note::
When using SHA1PRNG on Linux it's recommended specify ``-Djava.security.egd=file:/dev/./urandom`` as argument
to the JVM to prevent blocking. It is NOT as secure because it reuses the seed.