diff options
| author | Patrick Steinhardt <ps@pks.im> | 2016-02-10 11:06:23 +0100 |
|---|---|---|
| committer | Patrick Steinhardt <ps@pks.im> | 2016-02-10 11:06:23 +0100 |
| commit | 50174ab459e7a6c007f6ffa15d381f2f18bd89b8 (patch) | |
| tree | 9652b5edd7f15f12f7ae37438327d99ebdc8d5e5 /script | |
| parent | 8dddea42aaf876663fc3cc1afa31f2165cb9f993 (diff) | |
| download | libgit2-50174ab459e7a6c007f6ffa15d381f2f18bd89b8.tar.gz | |
coverity: use https URL for posting build
When posting our instrumented build results to Coverity we have
to include sensitive information, in particular our authorization
token. Currently we use an unencrypted channel to post this
information, leading to the token being transferred in plain.
Fix this by using a secured connection instead.
Diffstat (limited to 'script')
| -rwxr-xr-x | script/coverity.sh | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/script/coverity.sh b/script/coverity.sh index 785044c8a..8c826892f 100755 --- a/script/coverity.sh +++ b/script/coverity.sh @@ -50,10 +50,9 @@ COVERITY_UNSUPPORTED=1 \ tar czf libgit2.tgz cov-int SHA=$(git rev-parse --short HEAD) curl \ - --form project=libgit2 \ --form token="$COVERITY_TOKEN" \ --form email=bs@github.com \ --form file=@libgit2.tgz \ --form version="$SHA" \ --form description="Travis build" \ - http://scan5.coverity.com/cgi-bin/upload.py + https://scan.coverity.com/builds?project=libgit2 |