Changed client to allow http
This merge requests adds a --notls
flag to all subcommands of bitmaskcfg which send requests to the menshen api. The flag ensures omitting TLS for development reasons is allowed - in case the host url contains http instead of https. This allows us to test a locally running jnk, jnk-compose or a manually setup menshen API on localhost against bitmaskcfg.
closes #2 (closed)
Merge request reports
Activity
requested review from @cyberta
added 1 commit
- e07feeba - add no-tls flag to bitmaskcfg tool, revert changes in uTLS client
added 1 commit
- 1f900cba - parse no tls flag for locations best command
mentioned in merge request !4 (merged)
If I recall correctly one issue was: If I disable TLS, it still uses DNS over HTTPs per default:
https://0xacab.org/leap/bitmask-core/-/blob/main/pkg/bootstrap/api.go?ref_type=heads#L36
And this won't work without TLS (in the way it is implemented becauses it uses http2/uTLS). So if we dont use TLS, we also have to disable DNS over HTTP.Edited by Pea Nutclosing in favor of !4 (merged)