Gary Verhaegen 75c7d48d5b bind localhost for json-api and scenarios (#4576) ... Both were previously binding 0.0.0.0, which is inherently insecure. More importantly to me, that meant running `bazel test //...` essentially rendered my computer unusable for however long it took (which is _long_), as it kept popping up focus-stealing dialogs about whether or not I wanted to trust "java" to open an incoming network connection. The ScenarioService does not seem to have an existing setup for CLI args and my Scala-fu is not good enough to add one, so I just changed the hard-coded path. The JSON API already had an option, just with the wrong default. This is technically a breaking change, but I'm hoping to pass it under the "experimental" flag we still have on the JSON API. CHANGELOG_BEGIN - [JSON API - Experimental] As a security improvement, the JSON API server will now bind on ``127.0.0.1`` by default. Previous behaviour was to bind on ``0.0.0.0``; you can get that behaviour back by passing in the (existing) flag ``--address 0.0.0.0``. - [DAML SDK] The Scenario Service will now bind on ``127.0.0.1``. Previous behaviour was to bind on ``0.0.0.0``. CHANGELOG_END		2020-03-05 17:10:49 +01:00
..
db-backend	Aligning DB contract table with domain.ActiveContract class (#3989)	2020-01-08 20:39:57 +00:00
http-json	bind localhost for json-api and scenarios (#4576)	2020-03-05 17:10:49 +01:00
jwt	EC256 rather than EC512 algo (#4019)	2020-01-16 08:55:55 -05:00
lf-value-json	Remove pragma 'daml 1.2' (#4702)	2020-02-26 13:17:45 -05:00
utils	Remove unused dependencies to da_scala_library (#3938)	2020-01-06 18:14:21 +01:00