Re: [Ksummit-discuss] [TECH TOPIC] QR encoded oops for the kernel

["Teodora Băluţă" <teobaluta@gmail.com>]

On Mon, May 12, 2014 at 8:09 PM, H. Peter Anvin <hpa@zytor.com> wrote:
> On 05/12/2014 09:49 AM, Levente Kurusa wrote:
>>
>> What I wonder is how could we get the server back-end to not allow
>> the same oopses from bad users.
>>
>> Having a link like:
>>
>> oops.kernel.org/submit_oops.php?qr=$ENTROPY$BASE64DATA
>>
>> would mean that malicious users could edit the $ENTROPY part and
>> hence effectively report the same oops twice. Maybe some checksum?
>>  Or will it be too much for an already damaged kernel?
>>
>
> What did the old kerneloops system do for these kinds of things?
>
> Again, I'm concerned that a KS session for this will turn into an
> implementation discussion, which is better done by email.

Well, the discussion got a bit technical, but as Josh said, I see no
point in doing that sort of talk (for technical discussion there's
always the RFC thread [0]). I think what would be of interest is the
way the workflow changes and the infrastructure you need to maintain.
For example, at the moment, can you actually send an Oops directly to
kernel.org by posting it in a query?

Thanks,
Teodora

[0] https://lkml.org/lkml/2014/3/17/525