Closed noahlevenson closed 1 year ago
The first half of this is addressed in https://github.com/getlantern/broflake/commit/56112a6308fed5f0033d36b125e3665eeec717cb and https://github.com/getlantern/broflake/commit/4667852f035c42d2dd5f4d233eefe03a10c9f7d6.
Not sure about derek.sh and werek.sh yet...
I think since the production egress server became incompatible with vanilla clients, this is a non-issue.
Post-launch, we shouldn't be poking the software by spinning up clients that connect to our public discovery and egress server. Test clients connecting to public services and behaving erratically would create a nuisance for regular users.
Broflake clients shouldn't hardcode the address for Freddie and the egress server by default. Test scripts (like derek.sh and werek.sh) should be refactored to explicitly require user-supplied addresses pointing to an instance of Freddie and the egress server.