Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Malicious executable content in Gerrit contributions

Hi Denis,

Maybe having a white-list of usual contributors (Allowed to have an auto-trigger) would help. For others, only manual-trigger (From a Committer) would be allowed.


-----Message d'origine-----
De : [] De la part de Denis Roy
Envoyé : mercredi 10 décembre 2014 14:54
À :
Objet : [] Malicious executable content in Gerrit contributions

Well, the moment I've been dreading has finally come... malicious virus/malware is now in our Gerrit database.


This shows the intention of the contributor:

In this case, the bad contribution was picked up and built by Hudson... 
Many projects also run tests on these unknown contributions, which means Hudson not only builds the malicious code, but executes it too.

I am convinced that this practice, albeit convenient for projects, can ultimately lead to really bad things.

Discuss in this bug:

The Hudson Gerrit plugin allows several trigger events... "Patchset Created" is probably not the best event to use.  Right now I cannot see any other events, but having a first human verification that the contribution is not a Linux executable or shell script is definitely what I would recommend.

_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top