Hi,
On Wed, Oct 26, 2016 at 07:54:00PM -0400, Paul Gortmaker wrote:
> So, no EXPORT_SYMBOL, and any .config which has ACOMP2=m will fail.
I sent a patch for this:
https://patchwork.kernel.org/patch/9396503/
Regards,
--
Giovanni
--
To unsubscribe from this list: send the line "unsubscribe linux-c
Am Mittwoch, 26. Oktober 2016, 22:05:28 CEST schrieb Jeffrey Walton:
Hi Jeffrey,
> > The Linux kernel exports a network interface of type AF_ALG to allow user
> > space to utilize the kernel crypto API. libkcapi uses this network
> > interface and exports an easy to use API so that a developer do
> The Linux kernel exports a network interface of type AF_ALG to allow user
> space to utilize the kernel crypto API. libkcapi uses this network interface
> and exports an easy to use API so that a developer does not need to consider
> the low-level network interface handling.
>
> The library does
Hi,
The Linux kernel exports a network interface of type AF_ALG to allow user
space to utilize the kernel crypto API. libkcapi uses this network interface
and exports an easy to use API so that a developer does not need to consider
the low-level network interface handling.
The library does no
Hi Herbert,
for this patch, I have updated the testing for libkcapi accordingly and all
tests pass. I will push the libkcapi code 0.12 with that test code change
out shortly. Using the current upstream version of 0.11.1 will show failures
as it expects the correct recv return code. As stated below
On Wed, Oct 26, 2016 at 10:48 AM, Randy Dunlap wrote:
> On 10/25/16 19:51, Stephen Rothwell wrote:
>> Hi all,
>>
>> There will probably be no linux-next releases next week while I attend
>> the Kernel Summit.
>>
>> Changes since 20161025:
>>
>
> on x864_64:
>
> ERROR: "crypto_acomp_scomp_alloc_ctx
On Tue, Oct 25, 2016 at 07:38:55AM +0200, LABBE Corentin wrote:
> On Mon, Oct 24, 2016 at 10:10:20PM +0200, Maxime Ripard wrote:
> > On Sat, Oct 22, 2016 at 03:53:28PM +0200, Corentin Labbe wrote:
> > > Since SID's content is constant over reboot,
> >
> > That's not true, at least not across all t
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index d999373..58f903d 100644
--- a/crypto/testmgr.c
+++ b/crypto
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index 58f903d..cfafd24 100644
--- a/crypto/testmgr.c
+++ b/crypto
This series adds null tests for all sha*-mb internal algorithms so they can
be used in FIPS mode without further problems.
Since they are 3 separated modules I decided to use a separated commit for
each one.
Marcelo Cerri (3):
crypto: testmgr - Add missing tests for internal sha1-mb
impleme
Add null tests for the internal algorithm to avoid errors when running
in FIPS mode.
Signed-off-by: Marcelo Cerri
---
crypto/testmgr.c | 8
1 file changed, 8 insertions(+)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index ded50b6..d999373 100644
--- a/crypto/testmgr.c
+++ b/crypto
Am Mittwoch, 26. Oktober 2016, 18:17:14 CEST schrieb Juan Pablo Nariño
Mendoza:
Hi Juan,
> Sorry in advance for making what shall be a basic question for this
> list, but I have really ran out of ideas.
>
> Can someone explain me please, how does the memory layout and sg lists
> work for the IP
Sorry in advance for making what shall be a basic question for this
list, but I have really ran out of ideas.
Can someone explain me please, how does the memory layout and sg lists
work for the IPSec case, with generated IV case?
As I understand, it is like this (ascii art)
AD | IV Space | Plain
On 10/25/16 19:51, Stephen Rothwell wrote:
> Hi all,
>
> There will probably be no linux-next releases next week while I attend
> the Kernel Summit.
>
> Changes since 20161025:
>
on x864_64:
ERROR: "crypto_acomp_scomp_alloc_ctx" [crypto/acompress.ko] undefined!
ERROR: "crypto_acomp_scomp_free_
Then what is the role of the "for" structure? Why not do just a single
encryption/decryption call?
Regards,
Cata
>From: Hamid Nassiby
>Sent: Wednesday, October 26, 2016 10:16 AM
>To: Cata Vasile
>Cc: linux-crypto@vger.kernel.org
>Subject: Re: ARM-CE aes encryption on uneven blocks
>
>Hi,>
On 21-10-2016 07:50, Herbert Xu wrote:
> On Thu, Oct 13, 2016 at 04:39:35PM +0530, Harsh Jain wrote:
>> Remove malloc/free in crypto operation and allocate memory via cra_ctxsize.
>> Added new structure chcr_wr to populate Work Request Header.
>> Fixes: 324429d74127 (chcr: Support for Chelsio's C
Hi,
On Wed, Oct 26, 2016 at 08:47:16AM +0800, kbuild test robot wrote:
> >> ERROR: "crypto_acomp_scomp_free_ctx" [crypto/acompress.ko] undefined!
> >> ERROR: "crypto_acomp_scomp_alloc_ctx" [crypto/acompress.ko] undefined!
> >> ERROR: "crypto_init_scomp_ops_async" [crypto/acompress.ko] undefined!
Hi,
Based on my old experience with "struct crypto_alg" based drivers, the
data you receive there, is padded beforehand(in the upper layers);
Therefore the plaintext contains integral multiple of AES block size
of data and based on the number of blocks, the crypto transform can be
computed.
Regar
18 matches
Mail list logo
