I initially reported this for pureos-8.0-live-amd64.hybrid.iso with a SHA1 of
I can reproduce this on the latest version of pureos-8.0-live-amd64.hybrid.iso with SHA1 94a60b15505085c588ad67d13de40af957383fbe.
(The latter is apparently dated 2017-12-17)
I actually warned about this issue, so people would not link to the December image from our download page, as I haven't had the time to fix the problem during that month...
This issue will be resolved with the next image rebuild, which will be done once the Meltdown attack is mitigated in our kernel.
I actually warned about this issue, so people would not link to the December image from our download page
Not sure I understand this given that both versions (November and December?) do not work.
So my other ISO which I thought that was November might be from earlier - it has a non-November timestamp on my filesystem, but I have idea whether I can trust that hence giving you the SHAs in a few messages back.
(+1 for versioned file downloads!)