On 31.12.18 12:34, Ivan Ivanov wrote:
Had a lot of access problems recently, both to
coreboot website and
yes, they were very unresponsive yesterday.
Was it a DDoS attack?
I wouldn't know. Though, there's also still the migration to a new
mailing list solution (index generation for the archive), that takes
many resources on the server.
How to make sure that the
sources at review coreboot repository haven't been modified during
Due to the distributed nature of Git, we always know that the history
of the code (and implicitly the state of the code up to a given point)
wasn't tampered with. But... there were (authorized) modifications
during "this event". So what would remain (if we'd expect tampering) is
to distinguish wanted modifications from unwanted ones. Again, Git makes
this easy. If you have a trusted commit hash (or local pointer to an
earlier revision on master) you can ask Git what changed since then.