You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of SecureDrop 1.0.0, we support v3 onion services, but the workstation/proxy currently only works with v2 addresses for connecting to the Journalist Interface. Because pilot organizations may have switched to v3-only by the time of the pilot, we need to ensure that the workstation can be configured to use a v3 Journalist Interface onion service.
The text was updated successfully, but these errors were encountered:
config.json file now must contain the hostnames without .onion
It also has "hidservv3" entries with default values of "ADD_YOUR_VALUE",
changing those will cause the system to setup with V3 onion addresses.
There is no other changes visiable to the user of the securedrop-client.
config.json file now must contain the hostnames without .onion
It also has "hidservv3" entries with default values of "ADD_YOUR_VALUE",
changing those will cause the system to setup with V3 onion addresses.
There is no other changes visiable to the user of the securedrop-client.
config.json file now must contain the hostnames without .onion
It also has "hidservv3" entries with default values of "ADD_YOUR_VALUE",
changing those will cause the system to setup with V3 onion addresses.
There is no other changes visiable to the user of the securedrop-client.
As of SecureDrop 1.0.0, we support v3 onion services, but the workstation/proxy currently only works with v2 addresses for connecting to the Journalist Interface. Because pilot organizations may have switched to v3-only by the time of the pilot, we need to ensure that the workstation can be configured to use a v3 Journalist Interface onion service.
The text was updated successfully, but these errors were encountered: