mirror of
https://github.com/digital-asset/daml.git
synced 2024-09-20 09:17:43 +03:00
75c7d48d5b
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 |
||
|---|---|---|
| .. | ||
| release | ||
| src | ||
| BUILD.bazel | ||
| README.md | ||
HTTP JSON Service
See "HTTP JSON API Service" on docs.daml.com for usage information.
Documentation can also be found in the RST format: