Home About Meetings

February 13 2018 GDPR, codewars, Meltdown and Spectre Meet

Posted on 2018-02-18 21:55:36 +0000 by John

John shared a presentation he was developing on GDPR for small voluntary organisations. David S commented that the test for organisations would be ‘have you made a bona fide attempt to meet the regulations?’ He also commented on the three different uses of ‘loss’:

For organisations managing their own servers, they might need to consider encrypting the server logs; however, small voluntary organisations which use a server are more likely to use a hosted server.

Suggested software:

Never transfer anything on USB sticks.

Darren spoke about the last Leeds Code Dojo when they had taken part in codewars, each writing a program in a chosen language to solve a problem. When you submit your program, it is evaluated to provide you with a review and a ranking as a coder.

David S drew attention to spectre-meltdown-checker.sh which checks how many vulnerabilities have been addressed in your kernel.

Intel had originally sent out a patch which had allegedly caused some machines to freeze; so it had withdrawn it and then discovered that it did not necessarily freeze machines and reissued it.

The latest updates from Intel are available as Microcode Revision Guidance.

Brendan Gregg has done a paper on Initial Performance Regressions as a result of KPTI/KAISER Meltdown.