When compiling the DRBG statically into the kernel, the testmgr
allocation of the DRBG may be done at a time the Jitter RNG is
not available. The testmgr instantiates a number of DRBGs for performing
testing which may cause a flurry of logs about unavailable Jitter RNG.
Note, the Jitter RNG is not
This patch uses a list to track the asynchronous seeding requests until
the nonblocking pool is fully initialized. The random.c is provided with
two API calls: the get_blocking_random_bytes_cb allows the caller to
provide a callback function that is triggered once the nonblocking pool
is initialize
On Thu, Apr 30, 2015 at 4:00 AM, George Spelvin wrote:
> Sorry for the long silence; the last e-mails arrived as I went on a trip,
> and the packet got lost.
>
> I just upgraded my laptop to 4.0.1 and had to remember the magic
> incantation to get the wireless working. ("modprobe ctr")
>
>> Georg
This patch fixes an issue when building an internal AD representation.
We need to check assoclen and not only blindly loop over assoc sgl.
Signed-off-by: Tadeusz Struk
---
drivers/crypto/qat/qat_common/qat_algs.c | 32 +++---
1 file changed, 20 insertions(+), 12 deletio
The device doensn't support the default value and will change it to 256, which
will cause performace degradation for biger packets.
Add an explicit write to set it to 1024.
Reported-by: Tianliang Wang
Signed-off-by: Tadeusz Struk
---
drivers/crypto/qat/qat_dh895xcc/adf_drv.c |2 ++
1 file c
On 06/04/2015 08:57 PM, Herbert Xu wrote:
> Existing AEAD implementations should be completely unaware of
> the new interface because we recreate the old req->assoc in the
> crypto API.
Yes, assuming that one is using req->assoclen not only req->assoc ;)
>
> However, if you are creating a new AE
On 06/05/2015 01:50 AM, Paul Bolle wrote:
> This builds two modules if PUBLIC_KEY_ALGO_RSA = 'm': rsa.ko and
> rsa_pkcs1_v1_5.ko. Is that what you want?
No, this not what I wanted.
>
> public_key.c uses this, so it can end up in public_key.ko. But it's not
> exported. So a _quick and dirty_ buil
On Friday, June 05, 2015 at 05:54:33 AM, Herbert Xu wrote:
> On Thu, Jun 04, 2015 at 05:34:39PM +0200, Marek Vasut wrote:
> > Is this really a valid way to go about crypto -- introduce all kinds
> > of obscure nuances into the API which are driver specific at best ?
>
> So what do you suggest?
We
Am Freitag, 5. Juni 2015, 13:28:06 schrieb Herbert Xu:
Hi Herbert,
>
> Steffen, I think we need to revisit the idea of having a list
> of callbacks.
Ok, I will reactivate my patch with the list.
>
> Cheers,
--
Ciao
Stephan
--
To unsubscribe from this list: send the line "unsubscribe linux-cr
Hello
I was adding a test to testmgr for cbc(aes) but I hesitate on the
cipher_testvec parameter also_non_np.
A few remarks, perhaps not of the kind you'd like for an RFC, that I
hope are still relevant after Herbert's comment.
On Wed, 2015-06-03 at 15:44 -0700, Tadeusz Struk wrote:
> --- a/crypto/asymmetric_keys/Makefile
> +++ b/crypto/asymmetric_keys/Makefile
> @@ -8,6 +8,7 @@ asymmetric_keys-y := asymm
11 matches
Mail list logo