Built-in Htsget and Crypt4gh for the HTSGET storage #12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is the next step for supporting the HTSGET storage:
support for the Htsget protocol and Crypt4gh key-pair generation and content decryption is baked into the Funnel source code.
After this change, the Funnel environment does not depend on other programs for invoking content download over Htsget protocol. Therefore, this solution is more reliable.
Summary of changes:
./.c4gh/key[.pub]
, and~/.c4gh/key[.pub]
) as described hereC4GH_PASSPHRASE
,C4GH_SECRET_KEY
, andC4GH_PUBLIC_KEY
(the latter is a new variable name, yet optional)HTSGETConfig
: removedSendPublicKey
(as public key is always sent), and addedTimeout
parameter.