feat: support embedding encrypted psiphon config (#285)
We use an optional build tag to hide this configuration. When you choose this configuration, you need to provide the encrypted config as well as the corresponding decryption key. This is not the final design. This is an interim design to start working and experimenting with this functionality. The general idea here is to support psiphon in the binaries we build without committing the psiphon config to the repository itself. Part of https://github.com/ooni/probe/issues/985
This commit is contained in:
parent
79e8424677
commit
c89ecce3e0
7 changed files with 74 additions and 9 deletions
|
|
@ -275,15 +275,6 @@ func (s *Session) DefaultHTTPClient() *http.Client {
|
|||
return &http.Client{Transport: s.httpDefaultTransport}
|
||||
}
|
||||
|
||||
// FetchPsiphonConfig fetches psiphon config from the API.
|
||||
func (s *Session) FetchPsiphonConfig(ctx context.Context) ([]byte, error) {
|
||||
clnt, err := s.NewOrchestraClient(ctx)
|
||||
if err != nil {
|
||||
return nil, err
|
||||
}
|
||||
return clnt.FetchPsiphonConfig(ctx)
|
||||
}
|
||||
|
||||
// FetchTorTargets fetches tor targets from the API.
|
||||
func (s *Session) FetchTorTargets(
|
||||
ctx context.Context, cc string) (map[string]model.TorTarget, error) {
|
||||
|
|
|
|||
Loading…
Reference in a new issue