Linux Crypto
[Prev Page][Next Page]
- [PATCH] crypto: Validate output length in (de)compression tests
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: linux-next: Tree for November 26 (lib80211 + crypto)
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: linux-next: Tree for November 26 (lib80211 + crypto)
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [warnings] 37 warning fixes in networking related files
- From: David Miller <davem@xxxxxxxxxxxxx>
- [warnings] 37 warning fixes in networking related files
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH/RFC 0/4] Partial decompression API (was: Re: [patch 1/3] crypto: Add a zlib crypto module)
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH/RFC 1/4] crypto: Add partial decompression support to the CRYPTO API
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN] Use softirq kernel mapping in bh context.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH/RFC 0/4] Partial decompression API (was: Re: [patch 1/3] crypto: Add a zlib crypto module)
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: fix error flow of crypto/testmgr.c:test_comp()
- From: Ingo Molnar <mingo@xxxxxxx>
- Re: [PATCH] ansi_cprng: zero out key data on exit
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [PATCH/RFC 4/4] squashfs: Make SquashFS 4 use the new "zlib" crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [PATCH/RFC 3/4] crypto: Add a test for the "zlib" crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [PATCH/RFC 2/4] crypto: Add a "zlib" crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [PATCH/RFC 1/4] crypto: Add partial decompression support to the CRYPTO API
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [PATCH/RFC 0/4] Partial decompression API (was: Re: [patch 1/3] crypto: Add a zlib crypto module)
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [HIFN] Use softirq kernel mapping in bh context.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN] Bugfix series.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] ansi_cprng: zero out key data on exit
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: ansi_cprng: fix inverted DT increment routine
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Updated Openssl Patch to support Linux CryptoAPI
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH 1/1 v8] Add CryptoAPI User Interface Support v8
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Updated Openssl Patch to support Linux CryptoAPI
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- Re: [PATCH] short benchmarks
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] short benchmarks
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH] short benchmarks
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] short benchmarks
- From: Andreas Gerlich <linux-crypto@xxxxxxxxx>
- [PATCH] Fix DMA setup.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Have HW invalidate src and dest descriptors after processing
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Fix queue management.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Fix request context corruption.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Don't copy src sg list.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Move command descriptor setup to seperate function as preparation
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [HIFN] Bugfix series.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Fix queue processing.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH] Remove some unused cruft.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH 1/1 v8] Add CryptoAPI User Interface Support v8
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- [PATCH] ansi_cprng: zero out key data on exit
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v3]
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: ansi_cprng: fix inverted DT increment routine
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [PATCH] crypto: ansi_cprng: fix inverted DT increment routine
- From: Jarod Wilson <jarod@xxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v3]
- From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH linux-next] : Tree for November 12 (libcrc32c)
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: HIFN driver update.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: HIFN driver update.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH] crypto: ansi_cprng: avoid incorrect extra call to _get_more_prng_bytes
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: HIFN driver update.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/8] crypto/md4.c: use ARRAY_SIZE
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v3]
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v3]
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: dm-crypt using hifn_795x - still broken
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: dm-crypt using hifn_795x - still broken
- From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: "Barry G" <mr.scada@xxxxxxxxx>
- [PATCH linux-next] : Tree for November 12 (libcrc32c)
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: dm-crypt using hifn_795x - still broken
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH] crypto: ansi_cprng: avoid incorrect extra call to _get_more_prng_bytes
- From: Jarod Wilson <jarod@xxxxxxxxxx>
- Re: [PATCH] crypto: ansi_cprng: avoid incorrect extra call to _get_more_prng_bytes
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [PATCH] crypto: ansi_cprng: avoid incorrect extra call to _get_more_prng_bytes
- From: Jarod Wilson <jarod@xxxxxxxxxx>
- Re: dm-crypt using hifn_795x - still broken
- From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
- dm-crypt using hifn_795x - still broken
- From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
- Re: dm-crypt using hifn_795x - still broken
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: HIFN driver update.
- From: Andreas Gerlich <agl@xxxxxxxxx>
- HIFN driver update.
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: [PATCH] libcrc32c: Fix "crc32c undefined" compilation error
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] libcrc32c: Fix "crc32c undefined" compilation error
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: Are there any drivers that use aead.ko
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Unloading hardware based crypto to fallback to software based crypto
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: What is the difference between aead.ko and authenc.ko ?
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 1/8] crypto/md4.c: use ARRAY_SIZE
- From: Julia Lawall <julia@xxxxxxx>
- [PATCH] AMCC Crypto4xx Device Driver v3]
- From: James Hsiao <jhsiao@xxxxxxxx>
- Module load sequence
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- Are there any drivers that use aead.ko
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- libcrc32c: Move implementation to crypto crc32c
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Unloading hardware based crypto to fallback to software based crypto
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- What is the difference between aead.ko and authenc.ko ?
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- [PATCH 10/10] crypto: crc32c - Test descriptor context format
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 8/10] crypto: crc32c - Switch to shash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 9/10] crypto: crc32c-intel - Switch to shash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 7/10] crypto: hash - Export shash through hash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 6/10] crypto: api - Call type show function before legacy for proc
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 5/10] crypto: hash - Add import/export interface
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 4/10] crypto: hash - Export shash through ahash
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3/10] crypto: hash - Add shash interface
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 2/10] crypto: api - Rebirth of crypto_alloc_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 1/10] crypto: api - Move type exit function into crypto_tfm
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [0/10] New crypto hash interface
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: add test vectors for skein256/512/1024
- From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
- manual keying with OpenSwan 2.6.18
- From: Eran Ben-Avi <eranpublic@xxxxxxxxx>
- Re: [PATCH] crypto: extend ansi_cprng to allow resetting of DT value
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: extend ansi_cprng to allow resetting of DT value
- From: Jarod Wilson <jarod@xxxxxxxxxx>
- [PATCH] crypto: extend ansi_cprng to allow resetting of DT value
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: Can anyone explain the AEAD implementation
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: IPsec books and how to add async hardware encryption ?
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Can anyone explain the AEAD implementation
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- Re: IPsec books and how to add async hardware encryption ?
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- Re: [PATCH] crypto: add test vectors for skein256/512/1024
- From: Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: add test vectors for skein256/512/1024
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: [PATCH] crypto: add test vectors for skein256/512/1024
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- [PATCH] crypto: add test vectors for skein256/512/1024
- From: Sebastian Andrzej Siewior <sebastian@xxxxxxxxxxxxx>
- [PATCH] crypto: Add Skein hash algorithm variants
- From: Jeff Garzik <jeff@xxxxxxxxxx>
- Re: hifn_795x and geode-aes module
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- hifn_795x and geode-aes module
- From: Andreas Gerlich <linux-crypto@xxxxxxxxx>
- Re: IPsec books and how to add async hardware encryption ?
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- Re: hifn_7955 and Linux
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- IPsec books and how to add async hardware encryption ?
- From: Dean Jenkins <djenkins@xxxxxxxxxx>
- hifn_7955 and Linux
- From: Andreas Gerlich <agl@xxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: "Barry G" <mr.scada@xxxxxxxxx>
- RE: Enabling Talitos kills all IPsec traffic
- From: "Nipper Lee" <Lee.Nipper@xxxxxxxxxxxxx>
- RE: Enabling Talitos kills all IPsec traffic
- From: "Nipper Lee" <Lee.Nipper@xxxxxxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: "Barry G" <mr.scada@xxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: "Barry G" <mr.scada@xxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] ixp4xx_crypto: avoid firmware loading during module initialisation
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v2
- From: James Hsiao <jhsiao@xxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: "Barry G" <mr.scada@xxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v2
- From: Sebastian Andrzej Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: Enabling Talitos kills all IPsec traffic
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v2
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH] AMCC Crypto4xx Device Driver v2
- From: James Hsiao <jhsiao@xxxxxxxx>
- RE: [PATCH 1/1 v7] Add Crypto API User Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH 1/1 v7] Add Crypto API User Interface Support
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- RE: [PATCH 1/1 v7] Add Crypto API User Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH 1/1 v7] Add Crypto API User Interface Support
- From: Evgeniy Polyakov <zbr@xxxxxxxxxxx>
- [PATCH 1/1 v7] Add Crypto API User Interface Support
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- Enabling Talitos kills all IPsec traffic
- From: "Barry G" <mr.scada@xxxxxxxxx>
- Re: [PATCH] ixp4xx_crypto: avoid firmware loading during module initialisation
- From: Christian Hohnstaedt <christian@xxxxxxxxxxxxx>
- Re: [PATCH] AMCC Crypto4xx Device Driver v2
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: talitos Preempt overflow interrupts off-by-one fix
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: talitos Preempt overflow interrupts off-by-one fix
- From: Vishnu Suresh <Vishnu@xxxxxxxxxxxxx>
- Re: [PATCH 1/3] crypto: talitos - pass correct interrupt status to error handler
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- Re: [PATCH] trigger a panic when operating in FIPS mode and a crypto self test fails.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] crypto: talitos - pass correct interrupt status to error handler
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] crypto: talitos - pass correct interrupt status to error handler
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Crypto Update for 2.6.28
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] crypto: talitos - pass correct interrupt status to error handler
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: Crypto Update for 2.6.28
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: Crypto Update for 2.6.28
- From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Crypto Update for 2.6.28
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3/3] crypto: talitos - perform auth check in h/w if on sec 2.1 and above
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- [PATCH 2/3] crypto: talitos - done interrupt mitigation
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- [PATCH 1/3] crypto: talitos - pass correct interrupt status to error handler
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- Re: PadLock XSHA
- From: Harald Welte <laforge@xxxxxxxxxxxx>
- Re: PadLock XSHA
- From: Harald Welte <laforge@xxxxxxxxxxxx>
- Re: CTS (cipher text stealing mode) and short packets
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: CTS (cipher text stealing mode) and short packets
- From: "Russ Dill" <russ.dill@xxxxxxxxx>
- Re: CTS (cipher text stealing mode) and short packets
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: CTS (cipher text stealing mode) and short packets
- From: "Russ Dill" <russ.dill@xxxxxxxxx>
- Re: CTS (cipher text stealing mode) and short packets
- From: "Kevin Coffman" <kwc@xxxxxxxxxxxxxx>
- CTS (cipher text stealing mode) and short packets
- From: "Russ Dill" <russ.dill@xxxxxxxxx>
- Re: [PATCH] crypto: AMCC Crypto4xx Device Driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH 1/1 v6] Add CryptoAPI User Interface Support Patch v6
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Dimitri Puzin <max@xxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: hifn_795x in Linux-2.6.27-rc7
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [PATCH 1/1 v6] Add CryptoAPI User Interface Support Patch v6
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- [PATCH] trigger a panic when operating in FIPS mode and a crypto self test fails.
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- hifn_795x in Linux-2.6.27-rc7
- From: Dimitri Puzin <max@xxxxxxxxxx>
- [PATCH] crypto: AMCC Crypto4xx Device Driver
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: Crypto Fixes for 2.6.27
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 2.6.27] crypto: talitos - avoid consecutive packets going out with same IV
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: Camellia encryption module: incompatible
- From: "Carlo E. Prelz" <fluido@xxxxxxxxx>
- Re: Crypto Fixes for 2.6.27
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Camellia encryption module: incompatible
- From: Harvey Harrison <harvey.harrison@xxxxxxxxx>
- Re: Camellia encryption module: incompatible
- From: "Carlo E. Prelz" <fluido@xxxxxxxxx>
- Re: Camellia encryption module: incompatible
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [Squashfs-devel] [patch 0/3] [RFC] zlib crypto module
- From: Phillip Lougher <phillip@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/1 v5] Add CryptoAPI User Interface Patch v5
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: PadLock XSHA
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: PadLock XSHA
- From: Michal Ludvig <michal@xxxxxxxx>
- Re: [RFC] [crypto] padlock-aes loadkey ondemand
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: PadLock XSHA
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: PadLock XSHA
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: PadLock XSHA
- From: Michal Ludvig <michal@xxxxxxxx>
- PadLock XSHA
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [patch 1/3] crypto: Add a zlib crypto module
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Re: [patch 1/3] crypto: Add a zlib crypto module
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [patch 3/3] squashfs: Switch from zlib/inflate to "zlib" crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [patch 2/3] tcrypt: Add a self test for the zlib crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [patch 1/3] crypto: Add a zlib crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [patch 0/3] [RFC] zlib crypto module
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- [PATCH 1/1 v5] Add CryptoAPI User Interface Patch v5
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- Re: Crypto Fixes for 2.6.27
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: how can I verify that CRYPTO_DEV_IXP4XX (ixp4xx_crypto) works?
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- how can I verify that CRYPTO_DEV_IXP4XX (ixp4xx_crypto) works?
- From: Tomasz Chmielewski <mangoo@xxxxxxxx>
- Re: Oops in authenc: 2.6.26.3
- From: Sascha Biberhofer <biberhofer@xxxxxxxx>
- Re: Oops in authenc: 2.6.26.3
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Oops in authenc: 2.6.26.3
- From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
- Re: Oops in authenc: 2.6.26.3
- From: Matt LaPlante <kernel1@xxxxxxxxxxxxxxxx>
- Re: [PATCH 4/5] crypto: cryptomgr - Add test infrastructure
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Oops in authenc: 2.6.26.3
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Oops in authenc: 2.6.26.3
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: add fips_enable flag
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: add fips_enable flag
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: add fips_enable flag
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: fix larval lookup
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] ixp4xx_crypto: avoid firmware loading during module initialisation
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: fix larval lookup
- From: Christian Hohnstaedt <christian@xxxxxxxxxxxxx>
- [PATCH] ixp4xx_crypto: avoid firmware loading during module initialisation
- From: Christian Hohnstaedt <christian@xxxxxxxxxxxxx>
- crypto: cryptomgr - Test ciphers using ECB
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: obscure state information on free
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: crypto: skcipher - Use RNG interface instead of get_random_bytes
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: obscure state information on free
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: use kernel-provided bitops, unaligned access helpers
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: crypto: skcipher - Use RNG interface instead of get_random_bytes
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- crypto: skcipher - Use RNG interface instead of get_random_bytes
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: obscure state information on free
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: obscure state information on free
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] remove unnecessary variable in xfrm_output_resume()
- From: Jean-Christophe Dubois <jcd@xxxxxxxxxxxxxxx>
- Re: Crypto Fixes for 2.6.27
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] remove unnecessary variable in xfrm_output_resume()
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH] remove unnecessary variable in xfrm_output_resume()
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH] remove unnecessary variable in xfrm_output_resume()
- From: Jean-Christophe Dubois <jcd@xxxxxxxxxxxxxxx>
- Re: [PATCH] remove unnecessary variable in xfrm_output_resume()
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Pavel Machek <pavel@xxxxxxx>
- [PATCH] remove unnecessary variable in xfrm_output_resume()
- From: Jean-Christophe Dubois <jcd@xxxxxxxxxxxxxxx>
- Re: [PATCH 1/1 v1] Add CryptoAPI PKA Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- RE: [PATCH 1/1 v1] Add CryptoAPI PKA Support
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- question on offloaded crypto engine for network device.
- From: Jean-Christophe Dubois <jcd@xxxxxxxxxxxxxxx>
- [PATCH] crypto: obscure state information on free
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: OpenSSL patch to support Linux CryptoAPI.
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- RE: OpenSSL patch to support Linux CryptoAPI.
- From: "Loc Ho" <lho@xxxxxxxx>
- [PATCH] crypto: expand crypto lib api to include rng allocation
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 1/1 v1] Add CryptoAPI PKA Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC] [crypto] padlock-aes loadkey ondemand
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: OpenSSL patch to support Linux CryptoAPI.
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- RE: OpenSSL patch to support Linux CryptoAPI.
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: OpenSSL patch to support Linux CryptoAPI.
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [PATCH 1/1 v1] Add CryptoAPI PKA Support
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- OpenSSL patch to support Linux CryptoAPI.
- From: "Shasi Pulijala" <spulijala@xxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: "Ulrich Drepper" <drepper@xxxxxxxxx>
- Re: [RFC] [crypto] padlock-aes loadkey ondemand
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Pavel Machek <pavel@xxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Pavel Machek <pavel@xxxxxxx>
- Re: [PATCH 1/1 v4] Add CryptoAPI User Interface Support
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V3.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V2.
- From: Adrian Bunk <bunk@xxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V2.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API -V2.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: add fips_enable flag
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: add fips_enable flag
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: "Benoit Boissinot" <bboissin@xxxxxxxxx>
- RE: [PATCH 1/1 v4] Add CryptoAPI User Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Chris Mason <chris.mason@xxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Chris Mason <chris.mason@xxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Re: [PATCH 1/1 v4] Add CryptoAPI User Interface Support
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
- [PATCH] Using Intel CRC32 instruction to accelerate CRC32c algorithm by new crypto API.
- From: Austin Zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH 4/5] crypto: cryptomgr - Add test infrastructure
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 5/5] crypto: api - Use test infrastructure
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 3/5] crypto: tcrypt - Add alg_test interface
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 2/5] crypto: tcrypt - Abort and only log if there is an error
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 1/5] crypto: tcrypt - Avoid using contiguous pages
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [0/5] New algorithm testing infrastructure
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- crypto: hash - Fix digest size check for digest type
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 1/1 v4] Add CryptoAPI User Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: crypto: tcrypt - Fix AEAD testing
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- crypto: tcrypt - Fix AEAD testing
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: talitos - add handling for SEC 3.x treatment of link table
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: talitos - add handling for SEC 3.x treatment of link table
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- Crypto Fixes for 2.6.27
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: crypto stuff broken in -mm?
- From: Johannes Weiner <hannes@xxxxxxxxxxxx>
- Re: crypto stuff broken in -mm?
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Debugging Talitos
- From: "Barry G" <mr.scada@xxxxxxxxx>
- Re: Debugging Talitos
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Debugging Talitos
- From: "Barry G" <mr.scada@xxxxxxxxx>
- crypto stuff broken in -mm?
- From: Johannes Weiner <hannes@xxxxxxxxxxxx>
- Re: [PATCH] crypto: Cleaning some more minor nits in prng
- From: Joe Perches <joe@xxxxxxxxxxx>
- [PATCH] crypto: Cleaning some more minor nits in prng
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/6] crypto: talitos - remove calls to of_node_put
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] prng; bring prng into better alignment with specification
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] prng: fix a few misc bugs in prng
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] prng; bring prng into better alignment with specification
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] prng: fix a few misc bugs in prng
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Kumar Gala <galak@xxxxxxxxxxxxxxxxxxx>
- [PATCH 6/6] crypto: talitos - sparse fix
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 5/6] crypto: talitos - stop leaking memory in error path
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 4/6] crypto: talitos - fix GFP flag usage
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 3/6] crypto: talitos - preempt overflow interrupts
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 2/6] crypto: talitos - correct dst != src case handling
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 1/6] crypto: talitos - remove calls to of_node_put
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH] prng; bring prng into better alignment with specification
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [PATCH] prng: fix a few misc bugs in prng
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [2.6 patch] properly indent the CRYPTO_RMD* kconfig entries
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Change in cryptoloop?
- From: almafa <almafa@xxxxxxx>
- Re: [stable] Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [stable] Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [stable] Crypto Fixes for 2.6.26
- From: Greg KH <greg@xxxxxxxxx>
- Re: Crypto Fixes for 2.6.26
- From: "Oliver Pinter" <oliver.pntr@xxxxxxxxx>
- Re: Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [2.6 patch] properly indent the CRYPTO_RMD* kconfig entries
- From: Adrian Bunk <bunk@xxxxxxxxxx>
- Crypto Update for 2.6.27
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] The IXP4xx crypto driver should select CRYPTO_AUTHENC
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] check for s390 crypto facility availablility
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] The IXP4xx crypto driver should select CRYPTO_AUTHENC
- From: Imre Kaloz <kaloz@xxxxxxxxxxx>
- Re: [PATCH] check for s390 crypto facility availablility
- From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] check for s390 crypto facility availablility
- From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
- Re: [PATCH] check for s390 crypto facility availablility
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Regarding integration with cryptodev
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Regarding integration with cryptodev
- From: Manish RATHI <manish.rathi@xxxxxx>
- [PATCH] check for s390 crypto facility availablility
- From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
- Re: FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: austin zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: talitos - add support for sha256 and md5 variants
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Ideas about Linux CryptoAPI userspace interface
- From: Arturas K <arturas@xxxxxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: hash - Added scatter list walking helper
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: talitos - add support for sha256 and md5 variants
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- Re: FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: hash - Added scatter list walking helper
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] padlock: don't whinge when loaded on a non-VIA cpu
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Freescale SEC driver with cryptoloop on MPC8567e
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Freescale SEC driver with cryptoloop on MPC8567e
- From: "mike zheng" <mail4mz@xxxxxxxxx>
- Re: FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: FW: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: austin zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH] crypto/tcrypt.c fix resource leak
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto/tcrypt.c fix resource leak
- From: "Darren Jenkins\\" <darrenrjenkins@xxxxxxxxx>
- Re: [PATCH] prng: fix repetition test to properly update on each iteration
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] prng: fix repetition test to properly update on each iteration
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: crypto: hash - Removed bogus ahash base field
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- crypto: hash - Removed bogus ahash base field
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: hash - Fixed digest size check
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [Fwd: [PATCH]Using Intel CRC32 instruction to implement hardware accelerated CRC32c algorithm.]
- From: austin zhang <austin_zhang@xxxxxxxxxxxxxxx>
- Re: [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] crypto: use kernel-provided bitops, unaligned access helpers
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Andi Kleen <andi@xxxxxxxxxxxxxx>
- Re: [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- [PATCH 2/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [PATCH 1/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [PATCH 0/2] RNG: Add Pseudo Random Number Generator to kernel
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] talitos: Add support for 3des.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: tcrpyt - Remove unnecessary kmap/kunmap calls
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] [CRYPTO] talitos: Add support for 3des.
- From: Lee Nipper <lee.nipper@xxxxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: "deflate" crypto module questions
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- "deflate" crypto module questions
- From: Geert Uytterhoeven <Geert.Uytterhoeven@xxxxxxxxxxx>
- Re: [PATCH] ixp4xx: Hardware crypto support for IXP4xx CPUs
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- RE: [PATCH 1/1 v2] crypto: Add CryptoAPI User Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH 1/1 v2] crypto: Add CryptoAPI User Interface Support
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 1/4] crypto/talitos: rm duplicate timeout definition
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: remove duplicate include of linux/interrupt.h
- From: Andre Haupt <andre@xxxxxxxxxxxxxxx>
- Re: [PATCH] crypto: remove duplicate include of linux/interrupt.h
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [PATCH] crypto: remove duplicate include of linux/interrupt.h
- From: Andre Haupt <andre@xxxxxxxxxxxxxxx>
- [PATCH 1/4] crypto/talitos: rm duplicate timeout definition
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 2/4] crypto/talitos: unmap h/w generated IV
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 3/4] crypto/talitos: fix premature done handling
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH 4/4] crypto/talitos: add hwrng support
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- [PATCH] ixp4xx: Hardware crypto support for IXP4xx CPUs
- From: Christian Hohnstaedt <christian@xxxxxxxxxxxxx>
- [PATCH 1/1 v2] crypto: Add CryptoAPI User Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH 2/2 v2] talitos: Freescale integrated security engine (SEC) driver
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2 v2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2 v2] talitos: Freescale integrated security engine (SEC) driver
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- RE: Linux CryptoAPI Userspace API proposal
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: BUG in scatterlist.h when loading tcrypt
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- BUG in scatterlist.h when loading tcrypt
- From: Eric Sesterhenn <snakebyte@xxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [RFC PATCH] [XFRM] xfrm_algo: correct usage of RIPEMD-160
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [PATCH 2/2 v2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Scott Wood <scottwood@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Scott Wood <scottwood@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Scott Wood <scottwood@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Re: [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Re: IPSec ESP Authenc Offload
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 2/2] talitos: Freescale integrated security engine (SEC) driver
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- RE: IPSec ESP Authenc Offload
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: IPSec ESP Authenc Offload
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- RE: IPSec ESP Authenc Offload
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: calculte md5 sum?
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: IPSec ESP Authenc Offload
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- calculate md5 sum?
- From: "Tobias Koeck" <tobias.koeck@xxxxxxxxx>
- calculte md5 sum?
- From: "Tobias Koeck" <tobias.koeck@xxxxxxxxx>
- RE: IPSec ESP Authenc Offload
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: IPSec ESP Authenc Offload
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- IPSec ESP Authenc Offload
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH 0/3] [CRYPTO] ripemd: Fix endian issues
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] CRYPTO: Simplify code using ARRAY_SIZE() macro.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH] CRYPTO: Simplify code using ARRAY_SIZE() macro.
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- [PATCH] CRYPTO: Simplify code using ARRAY_SIZE() macro.
- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] tcrypt: add self test for des3_ebe cipher operating in cbc mode
- From: Neil Horman <nhorman@xxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: Hardware Acceleration on Freescale MPC8349
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH 0/3] [CRYPTO] ripemd: Fix endian issues
- From: Sebastian Siewior <sebastian@xxxxxxxxxxxxx>
- [PATCH 3/3] [CRYPTO] rmd320: Fix endian problems
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 2/3] [CRYPTO] rmd256: Fix endian problems
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 1/3] [CRYPTO] rmd160: Fix endian problems
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 0/3] [CRYPTO] ripemd: Fix endian issues
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: Hardware Acceleration on Freescale MPC8349
- From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
- Hardware Acceleration on Freescale MPC8349
- From: "Barry G" <mr.scada@xxxxxxxxx>
- Re: [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: linux-next 20080519 build failure
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Linux CryptoAPI Userspace API proposal
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()
- From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
- [BUILD_FAILURE] linux-next: Tree for May 19 - build fails on cryptd_alloc_hash ()
- From: Kamalesh Babulal <kamalesh@xxxxxxxxxxxxxxxxxx>
- linux-next 20080519 build failure
- From: Philippe Roussel <p.o.roussel@xxxxxxx>
- Re: [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- [PATCH] [CRYPTO] rmd128: Fix endian problems
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: David Miller <davem@xxxxxxxxxxxxx>
- Re: [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- [PATCH v2] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Geode-CBC
- From: Vasile Marii <vascim@xxxxxxxxx>
- Linux CryptoAPI Userspace API proposal
- From: "Loc Ho" <lho@xxxxxxxx>
- [PATCH] crypto: rmd128: make it work on my prefered architecture
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [HIFN 1/1] Remove duplicated include
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Userspace API proposal was: Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- RE: Userspace API proposal was: Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- RE: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [PATCH 1/3] [CRYPTO] hash: Add Async Hash Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] [CRYPTO] hash: Add Async Hash Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/3] [CRYPTO] hash: Add Async Hash Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Userspace API proposal was: Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Userspace API proposal was: Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: tcrypt: hmac test with keys > blocksize fail
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 1/1] RFC: Add CryptoAPI User Space Interface Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- [PATCH 3/3] [CRYPTO] tcrypt: Add Async Hash Support
- From: "Loc Ho" <lho@xxxxxxxx>
- [PATCH 2/3] [CRYPTO] cryptd: Add Async Hash Support
- From: "Loc Ho" <lho@xxxxxxxx>
- [PATCH 1/3] [CRYPTO] hash: Add Async Hash Support
- From: "Loc Ho" <lho@xxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- [HIFN 1/1] Remove duplicated include
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [RESEND][PATCH 0/4][CRYPTO] add support for extended RIPEMD hash algorithms
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [RESEND][PATCH 2/4][CRYPTO] RIPEMD: Add support for RIPEMD-256 and RIPEMD-320.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [RESEND][PATCH 3/4][CRYPTO] tcrypt: Add test vectors for RIPEMD-256 and RIPEMD-320.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [RESEND][PATCH 4/4][CRYPTO] RIPEMD: Add Kconfig entries for extended RIPEMD hash algorithms
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [RESEND][PATCH 1/4][CRYPTO] RIPEMD: put all common RIPEMD values in header file.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [RESEND][PATCH 0/4][CRYPTO] add support for extended RIPEMD hash algorithms
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH 2/5][CRYPTO] RIPEMD: put all common RIPEMD values in header file
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH 2/5][CRYPTO] RIPEMD: put all common RIPEMD values in header file
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 1/5][CRYPTO] RIPEMD: fix Makefile entry for rmd128.o
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC, TCRYPT]: Catch cipher destination memory corruption
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC, TCRYPT]: Catch cipher destination memory corruption
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [RFC, TCRYPT]: Catch cipher destination memory corruption
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH 5/5][CRYPTO] RIPEMD: Add Kconfig entries for extended RIPEMD hash algorithms
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 4/5][CRYPTO] tcrypt: Add test vectors for RIPEMD-256 and RIPEMD-320
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 3/5][CRYPTO] RIPEMD: Add support for RIPEMD-256 and RIPEMD-320
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 2/5][CRYPTO] RIPEMD: put all common RIPEMD values in header file
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 1/5][CRYPTO] RIPEMD: fix Makefile entry for rmd128.o
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 0/5][CRYPTO] add support for extended RIPEMD hash algorithms
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [HIFN 01/n]: Endianess fixes
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [CRYPTO] tcrpyt: Get rid of change log in source
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH 0/3][CRYPTO] RIPEMD: add support for RIPEMD hash algorithms.
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN 01/n]: Endianess fixes
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 01/n]: Endianess fixes
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [CRYPTO] cryptd: Fix EINPROGRESS notification context
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN 01/n]: Endianess fixes
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 11/n]: Have HW invalidate src and dest descriptors after processing
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH 1/1] CryptoAPI: Add Async Hash Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN 11/n]: Have HW invalidate src and dest descriptors after processing
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 10/n]: Move command descriptor setup to seperate function
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 1/1] CryptoAPI: Add Async Hash Support
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 07/n]: Use unique driver names for different algos
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 01/n]: Endianess fixes
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 06/n]: Properly handle requests for less than the full scatterlist
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [PATCH 1/1] CryptoAPI: Add Async Hash Support
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN 01/n]: Endianess fixes
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [HIFN 11/n]: Have HW invalidate src and dest descriptors after processing
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 10/n]: Move command descriptor setup to seperate function
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [HIFN 09/n]: Fix max queue length value
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 04/n]: Handle ablkcipher_walk errors
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 05/n]: Fix data alignment checks
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [HIFN 09/n]: Fix max queue length value
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 08/n]: Properly initialize ivsize for CBC modes
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 07/n]: Use unique driver names for different algos
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 06/n]: Properly handle requests for less than the full scatterlist
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 03/n]: Indicate asynchronous processing to crypto API
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 05/n]: Fix data alignment checks
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [HIFN 02/n]: Remove printk_ratelimit() for debugging printk
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [HIFN 03/n]: Indicate asynchronous processing to crypto API
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- [HIFN 04/n]: Handle ablkcipher_walk errors
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 03/n]: Indicate asynchronous processing to crypto API
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 02/n]: Remove printk_ratelimit() for debugging printk
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [HIFN 01/n]: Endianess fixes
- From: Patrick McHardy <kaber@xxxxxxxxx>
- [RFC, TCRYPT]: Catch cipher destination memory corruption
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: "Huang, Ying" <ying.huang@xxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: "Huang, Ying" <ying.huang@xxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: tcrypt: hmac test with keys > blocksize fail
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: tcrypt: hmac test with keys > blocksize fail
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [dm-devel] Desynchronizing dm-raid1
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
- Re: tcrypt: hmac test with keys > blocksize fail
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- [PATCH 0/3][CRYPTO] RIPEMD: add support for RIPEMD hash algorithms.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 2/3]CRYPTO] RIPEMD: add test vectors for RIPEMD-128 and RIPEMD-160.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 3/3][CRYPTO] RIPEMD: add Kconfig entries for RIPEMD hash algorithms.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- [PATCH 1/3][CRYPTO] RIPEMD: add support for RIPEMD hash algorithms.
- From: Adrian-Ken Rueegsegger <rueegsegger@xxxxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: dean gaudet <dean@xxxxxxxxxx>
- Re: tcrypt: hmac test with keys > blocksize fail
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Re: tcrypt: hmac test with keys > blocksize fail
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- tcrypt: hmac test with keys > blocksize fail
- From: Adrian-Ken Rüegsegger <rueegsegger@xxxxxxxxxxx>
- Crypto Fixes for 2.6.26
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [revised PATCH] crypto: Correct kzalloc error test
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
- Re: [revised PATCH] crypto: Correct kzalloc error test
- From: Julia Lawall <julia@xxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH] crypto: Correct kzalloc error test
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [PATCH] crypto: Correct kzalloc error test
- From: Julia Lawall <julia@xxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [RFC XFRM]: esp: fix scatterlist of out bounds access with crypto_eseqiv
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [CRYPTO]: authenc: fix async crypto crash in crypto_authenc_genicv()
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- [CRYPTO]: authenc: fix async crypto crash in crypto_authenc_genicv()
- From: Patrick McHardy <kaber@xxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: "Huang, Ying" <ying.huang@xxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: "Huang, Ying" <ying.huang@xxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- Re: [PATCH -mm crypto] AES: x86_64 asm implementation optimization
- From: Sebastian Siewior <linux-crypto@xxxxxxxxxxxxxxxx>
- [PATCH 1/1] CryptoAPI: Add Async Hash Support
- From: "Loc Ho" <lho@xxxxxxxx>
[Index of Archives]
[Kernel]
[Netfilter]
[Bugtraq]
[GNU Crypto]