diff options
| author | Michael Scherer <misc@redhat.com> | 2019-04-11 16:31:22 +0200 |
|---|---|---|
| committer | Michael Scherer <misc@redhat.com> | 2019-04-11 16:31:22 +0200 |
| commit | 56c913adcb59cb3d92d250b97d09d55eea99aba7 (patch) | |
| tree | c67cc726a7b1ea8f0905f01b519031c88d0dfdc3 | |
| parent | 29a5b64cf94b2ddc247e459a3154f4688d49d157 (diff) | |
Automatically accept the review.gluster.org ssh key
See https://bugzilla.redhat.com/show_bug.cgi?id=1698694
While this would open us to MITM in very specific case (like, just
after a server was reinstalled), a attacker would like just get
access to vote on a patch as the regression tests, which do not seems
that a big attack. This wouldn't also be stealth, since the MITM would
be discovered as soon as the traffic is no longer intercepted.
Plus, the others scripts already do the same.
Change-Id: I8e294d92c2602c86fe6f04227512ce70ec081f03
| -rw-r--r-- | build-gluster-org/scripts/centos-regression.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/build-gluster-org/scripts/centos-regression.sh b/build-gluster-org/scripts/centos-regression.sh index abac535..cb2134e 100644 --- a/build-gluster-org/scripts/centos-regression.sh +++ b/build-gluster-org/scripts/centos-regression.sh @@ -117,5 +117,5 @@ fi # Update Gerrit with the success/failure status sudo mv /tmp/gluster_regression.txt $WORKSPACE || true sudo chown jenkins:jenkins gluster_regression.txt || true -ssh build@review.gluster.org gerrit review --message "'$BURL : $VERDICT'" --project=glusterfs --label CentOS-regression="$V" $GIT_COMMIT +ssh -o "StrictHostKeyChecking=no" build@review.gluster.org gerrit review --message "'$BURL : $VERDICT'" --project=glusterfs --label CentOS-regression="$V" $GIT_COMMIT exit $RET |