A backdoor in a popular Ruby gem

Posted Apr 11, 2019 6:23 UTC (Thu) by eru (subscriber, #2753)
In reply to: A backdoor in a popular Ruby gem by NYKevin
Parent article: A backdoor in a popular Ruby gem

You are describing a "CI" setup for reproducible builds. That can actually also be a carrot for developers involved in large code bases like browsers or LibreOffice, where building on the developers desktop might take hours.

A backdoor in a popular Ruby gem

Posted Apr 11, 2019 6:36 UTC (Thu) by nilsmeyer (guest, #122604) [Link] (1 responses)

Though it can be said the compute capacity already exists and is paid for on the developers workstation while the funds to pay for it again on the other end have to be organized.

A backdoor in a popular Ruby gem

Posted Apr 11, 2019 7:18 UTC (Thu) by roc (subscriber, #30627) [Link]

Developer workstations are incredibly inefficient. For a big project like Firefox you need lots of cores to make the build latency tolerable, but then they're mostly idle.