Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Theodore Ts'o <tytso@mit.edu>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/2] Add in-kernel /dev/random equivalent
Date: Fri, 06 Jun 2014 14:23:23 +0200	[thread overview]
Message-ID: <33386917.yDDF1yg5fp@tauon> (raw)
In-Reply-To: <20140606115900.GA4367@amd.pavel.ucw.cz>

Am Freitag, 6. Juni 2014, 13:59:00 schrieb Pavel Machek:

Hi Pavel,

>On Mon 2014-05-12 00:36:01, Stephan Mueller wrote:
>> Hi,
>> 
>> as discussed in thread [1], an in-kernel equivalent to the blocking
>> /dev/random device behavior is suggested. This in-kernel blocking
>> access to the RNG can be used to seed deterministic random number
>> generators with random numbers that are directly backed by the
>> underlying noise sources.
>> 
>> The following patch implements this concept by adding a third output
>> pool, the kernel_pool that is only accessible inside the kernel.
>> That kernel_pool feeds the blocking operation API calls to obtain
>> random numbers.
>> 
>> Please find a test kernel module attached. You can unload it even
>> while the collection process is ongoing.
>> 
>> [1] https://lkml.org/lkml/2014/4/27/174
>> 
>> Stephan Mueller (2):
>>   Addition of kernel_pool
>>   Asynchronous and syncronous API for accessing kernel_pool
>>  
>>  drivers/char/random.c  | 163
>> 
>> +++++++++++++++++++++++++++++++++++++++++++++----
>> 
>>  include/linux/random.h |  16 +++++
>>  2 files changed, 166 insertions(+), 13 deletions(-)
>
> * Copyright (c) 2014
> *
> * Permission is hereby granted, free of charge, to any person
> *obtaining a copy
> * of this software and associated documentation files (the
> *"Software"), to deal
> * in the Software without restriction, including without limitation
> *the rights
> * to use, copy, modify, merge, publish, distribute, sublicense,
> *and/or sell
> * copies of the Software, and to permit persons to whom the Software
> *is
> * furnished to do so, subject to the following conditions:
>
>...but module_license says this is GPL...

Thank you very much for the hint -- this is an oversight on my behalf. I 
wanted the test kernel code to be licensed in a dual BSD/GPLv2 style.

As this is just a test module to demonstrate the appropriateness of the 
offered patch, I hope you can still live with it until a potential new 
submission is provided. Though, if you insist I can resubmit the test 
module with the dual BSD/GPLv2 clause.

Ciao
Stephan

      reply	other threads:[~2014-06-06 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 22:36 [PATCH 0/2] Add in-kernel /dev/random equivalent Stephan Mueller
2014-05-11 22:37 ` [PATCH 1/2] Addition of kernel_pool Stephan Mueller
2014-05-11 22:38   ` [PATCH 2/2] Asynchronous and syncronous API for accessing kernel_pool Stephan Mueller
2014-06-06 11:59 ` [PATCH 0/2] Add in-kernel /dev/random equivalent Pavel Machek
2014-06-06 12:23   ` Stephan Mueller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=33386917.yDDF1yg5fp@tauon \
    --to=smueller@chronox.de \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox