thms.properties
Wrote more about this in
https://tersesystems.com/2014/01/13/fixing-the-most-dangerous-code-in-the-world/
Adding this to the Akka issue so Konrad doesn't have to...
--
Will Sargent
*Engineer, Lightbend, Inc.*
will.sarg...@lightbend.com
On Sun, Jul 31, 2016 at 4:30 AM, Konrad 'k
e security
property jdk.tls.disabledAlgorithms to add TLSv1 specifically.
Will Sargent
Engineer, Lightbend, Inc.
On Tue, Jul 26, 2016 at 1:12 AM, <yinzhongh...@gmail.com> wrote:
> Configure file as follow:
> # Protocol to use for SSL encryption, choose from:
> # Java 6 & 7:
&g
You can mitigate this by using akka-slf4j with Logback and using
AsyncAppender in your logback configuration. It is lossy for debug events,
so once the queue fills up to 80% it will start throwing away events.
http://logback.qos.ch/manual/appenders.html#AsyncAppender
On Sun, Dec 13, 2015 at
The SSLContext is responsible for handling the trust store -- you set it up
and pass that into akka-http using HttpsContext.create(sslContext,...).
How to set up the SSLContext is a bit confusing. There are examples in the
guides for Android:
-with-7-logback-tweaks/
A logging framework has to implement SLF4J and not be a bottleneck -- Play
and Akka use logback and it works fine.
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com, the company behind Play Framework
http://www.playframework.com, Akka http://akka.io
check. More here:
http://tersesystems.com/2014/03/23/fixing-hostname-verification/
Addendum: forgot to mention that server identity checks only really matter
if you have SSLEngine operating as a client, rather than as a server, so
it's not a requirement.
Will Sargent
Consultant, Professional
Hi Thomas,
There's some things you should watch out for in your code:
* If you want to use TLS 1.2, you should specify getInstance(TLSv1.2)
specifically (JDK 1.7 defaults to TLS 1.0)
* You should disable SSLv3 (at the very least) using setEnabledProtocols().
* You are better off initializing
You can also simulate network failure more directly with iptables and tc:
https://github.com/tylertreat/Comcast
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com, the company behind Play Framework
http://www.playframework.com, Akka http://akka.io and Scala
http
You can turn on JSSE debugging with -Djavax.net.debug=all to see the
underlying cipher key exchange and setup as well, which may help.
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com, the company behind Play Framework
http://www.playframework.com, Akka http://akka.io
One way to do it would be to have a supervisor actor be responsible for
opening and closing the actor, and instantiating MyActor. Then, the
supervisor actor can deathwatch for the actor and close the writer, or
close the writer through the supervisorStrategy on exception.
Will Sargent
Consultant
Hi Dominik,
Good talking to you yesterday -- here's the documentation I was referring
to about futures and pipeTo.
http://doc.akka.io/docs/akka/current/scala/futures.html
http://doc.akka.io/docs/akka/current/scala/actors.html#Ask__Send-And-Receive-Future
Will Sargent
Consultant, Professional
Yes, you can use SLF4JLogger, then cast to Logback and change the log level
there.
http://stackoverflow.com/a/3838108/5266
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com, the company behind Play Framework
http://www.playframework.com, Akka http://akka.io and Scala
Or, if you just want a reloadable runtime, you can tell Logback to watch
for changes to the logging file using autoScan:
http://logback.qos.ch/manual/configuration.html#autoScan
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com, the company behind Play Framework
http
You could look at the snowflake based systems:
https://github.com/BazuSports/flurry
http://boundary.com/blog/2012/01/12/flake-a-decentralized-k-ordered-unique-id-generator-in-erlang/
https://github.com/gideondk/flakepack
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com
You should look at
http://typesafe.com/activator/template/akka-distributed-workers
which uses akka persistence with a work-pulling master.
Will Sargent
Consultant, Professional Services
Typesafe http://typesafe.com, the company behind Play Framework
http://www.playframework.com, Akka http
I'm doing some work on the Play side for client side TLS, but it'll be a
while before it gets in.
http://tersesystems.com/2014/01/13/fixing-the-most-dangerous-code-in-the-world/
In the mean time, you should use sun.security.util.HostnameChecker for
hostname verification.
Will.
On Tue, Feb 11,
16 matches
Mail list logo
