Linux Crypto

• Thread Index

• Re: [PATCH v3 0/2] crypto, x86: assembler implementation of SHA1
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: picoxcell: fix possible invalid pointer dereference
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] crypto: picoxcell - convert to platform ID table
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] n2_crypto: Fix a get/put_cpu() imbalance
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] treewide: Update sha_transform
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Cryptomgr race vs built-in aesni
  • From: Josh Boyer <jwboyer@xxxxxxxxxx>
• Re: [PATCH] treewide: Update sha_transform
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] treewide: Update sha_transform
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] lib/sha1: remove memsets and allocate workspace on the stack
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: remove memsets and allocate workspace on the stack
  • From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: remove memsets and allocate workspace on the stack
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: remove memsets and allocate workspace on the stack
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH] lib/sha1: remove memsets and allocate workspace on the stack
  • From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
• Re: [PATCH v2 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Sandy Harris <sandyinchina@xxxxxxxxx>
• Re: [PATCH] n2_crypto: Fix a get/put_cpu() imbalance
  • From: David Miller <davem@xxxxxxxxxxxxx>
• RE: [PATCH v2 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: "Locktyukhin, Maxim" <maxim.locktyukhin@xxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Nicolas Pitre <nico@xxxxxxxxxxx>
• [PATCH] treewide: Remove direct uses of SHA_WORKSPACE_WORDS
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] treewide: Remove direct uses of SHA_WORKSPACE_WORDS
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Joachim Eastwood <manabian@xxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Andreas Schwab <schwab@xxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Joachim Eastwood <manabian@xxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Joachim Eastwood <manabian@xxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Joachim Eastwood <manabian@xxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Joachim Eastwood <manabian@xxxxxxxxx>
• [PATCH] n2_crypto: Fix a get/put_cpu() imbalance
  • From: Thomas Meyer <thomas@xxxxxxxx>
• [PATCH] lib/sha1: use the git implementation of SHA-1
  • From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
• Re: [PATCH v3 0/2] crypto, x86: assembler implementation of SHA1
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH v3 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH v3 1/2] crypto, sha1: export sha1_update for reuse
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH v3 0/2] crypto, x86: assembler implementation of SHA1
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock-aes - Make module loading even quieter when hardware is missing
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: picoxcell: fix possible invalid pointer dereference
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• [PATCH 3/3] crypto: picoxcell - support for device tree matching
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• [PATCH 2/3] crypto: picoxcell - add connection ID to the clock name
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• [PATCH 1/3] crypto: picoxcell - convert to platform ID table
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] crypto, sha1: export sha1_update for reuse
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] crypto, sha1: export sha1_update for reuse
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: padlock-aes - Make module loading even quieter when hardware is missing
  • From: Jonathan Nieder <jrnieder@xxxxxxxxx>
• Re: Bug#485070: cryptsetup: "FATAL" padlock_{aes,sha} error during boot
  • From: Ben Hutchings <ben@xxxxxxxxxxxxxxx>
• Re: cryptsetup: "FATAL" padlock_{aes,sha} error during boot
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] crypto, sha1: export sha1_update for reuse
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] crypto, sha1: export sha1_update for reuse
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• cryptsetup: "FATAL" padlock_{aes,sha} error during boot
  • From: Ralf Jung <ralfjung-e@xxxxxx>
• Re: [Bug 37862] padlock related kernel NULL pointer dereference
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [Bugme-new] [Bug 37862] New: padlock related kernel NULL pointer dereference
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [lm-sensors] [PATCH 01/34] System Firmware Interface
  • From: Jean Delvare <khali@xxxxxxxxxxxx>
• [PATCH v2 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH v2 1/2] crypto, sha1: export sha1_update for reuse
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH v2 0/2] crypto, x86: assembler implementation of SHA1
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Crypto Update for 3.1
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 08/34] drivers/crypto changes for SMBIOS and System Firmware
  • From: Prarit Bhargava <prarit@xxxxxxxxxx>
• [PATCH 01/34] System Firmware Interface
  • From: Prarit Bhargava <prarit@xxxxxxxxxx>
• [PATCH 34/34] Remove old DMI & SMBIOS code and make SMBIOS default on
  • From: Prarit Bhargava <prarit@xxxxxxxxxx>
• [PATCH 02/34] New SMBIOS driver for x86 and ia64.
  • From: Prarit Bhargava <prarit@xxxxxxxxxx>
• [PATCH 2/2] crypto, x86: SSSE3 based SHA1 implementation for x86-64
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH 1/2] crypto, sha1: export sha1_update for reuse
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH 0/2] crypto, x86: assembler implementation of SHA1
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: [PATCH 1/8] crypto: talitos - ensure request ordering within a single tfm
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 7/8] crypto: caam - faster aead implementation
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 8/8] crypto: caam - ablkcipher support
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 5/8] crypto: caam - shorter names
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 4/8] crypto: talitos - don't bad_key in ablkcipher setkey
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 6/8] crypto: caam - structure renaming
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 3/8] crypto: talitos - remove unused giv from ablkcipher methods
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 2/8] crypto: talitos - don't set done notification in hot path
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 1/8] crypto: talitos - ensure request ordering within a single tfm
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Announce loop-AES-v3.6d file/swap crypto package
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto, gf128: fix call to memset()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto, gf128: fix call to memset()
  • From: pageexec@xxxxxxxxxxx
• Re: [PATCH] crypto, gf128: fix call to memset()
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH] crypto, gf128: fix call to memset()
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Hamid Nassiby <h.nassiby@xxxxxxxxx>
• Re: [PATCH] s390: support hardware accelerated SHA-224
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Crypto Fixes for 3.0
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: caam - fix operator precedence in shared descriptor allocation
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Frederick Gazerblezeebe <fgazerblezeebe@xxxxxxxxx>
• Re: [PATCH] crypto: caam - fix operator precedence in shared descriptor allocation
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH] s390: support hardware accelerated SHA-224
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Crypto: Don't use err uninitialized in algif_hash.c:hash_sendmsg()
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PATCH v3] crypto: sha1: use SHA1_BLOCK_SIZE
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: crypto4xx - Perform read/modify/write on device control register
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Crypto: Don't use err uninitialized in algif_hash.c:hash_sendmsg()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Crypto: Don't use err uninitialized in algif_hash.c:hash_sendmsg()
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH] Crypto: Don't use err uninitialized in algif_hash.c:hash_sendmsg()
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PATCH 00/35]: System Firmware and SMBIOS Support
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• [PATCH v3] crypto: sha1: use SHA1_BLOCK_SIZE
  • From: Mandeep Singh Baines <msb@xxxxxxxxxx>
• Re: [PATCH] hwrng: ppc4xx - add support for ppc4xx TRNG
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH] hwrng: ppc4xx - add support for ppc4xx TRNG
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH] crypto: crypto4xx - Perform read/modify/write on device control register
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• PROBLEM: padlock related kernel NULL pointer dereference
  • From: "Jethro Beekman - E.T.S.V. Scintilla" <jethrob@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 2/5] clocksource: add support for entropy-generation function
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 5/5] misc: add clocksource-based entropy generation driver
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH 2/5] clocksource: add support for entropy-generation function
  • From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: hpas@xxxxxxxxx
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: HW Accelerated IPSEC?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: HW Accelerated IPSEC?
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Matt Mackall <mpm@xxxxxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: john stultz <johnstul@xxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH 4/5] tsc: wire up entropy generation function
  • From: Venkatesh Pallipadi <venki@xxxxxxxxxx>
• [PATCH 2/5] clocksource: add support for entropy-generation function
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH 4/5] tsc: wire up entropy generation function
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH 1/5] random: add new clocksource entropy interface
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH 3/5] hpet: wire up entropy generation function
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH 5/5] misc: add clocksource-based entropy generation driver
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH 0/5] Feed entropy pool via high-resolution clocksources
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: HW Accelerated IPSEC?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: HW Accelerated IPSEC?
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: HW Accelerated IPSEC?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: HW Accelerated IPSEC?
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 00/11] crypto: omap-sham driver fixes
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• Re: [PATCH] crypto: picoxcell: fix possible invalid pointer dereference
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: caam - fix build warning when DEBUG_FS not configured
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 00/11] crypto: omap-sham driver fixes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: UML build fixes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• HW Accelerated IPSEC?
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Frederick Gazerblezeebe <fgazerblezeebe@xxxxxxxxx>
• [PATCH] crypto: picoxcell: fix possible invalid pointer dereference
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• [PATCH] crypto: caam - fix build warning when DEBUG_FS not configured
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Frederick Gazerblezeebe <fgazerblezeebe@xxxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Frederick Gazerblezeebe <fgazerblezeebe@xxxxxxxxx>
• [PATCH 05/11] omap-sham: move some flags to device context
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 02/11] omap-sham: remove unused code
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 01/11] omap-sham: remove extra reference
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 09/11] omap-sham: irq handler must not clear error code
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 11/11] omap-sham: do not schedule tasklet if there is no active requests
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 10/11] omap-sham: clear device flags when finishing request
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 07/11] omap-sham: remove dedicated queue handling tasklet
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 08/11] omap-sham: irq and dma handling changes
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 06/11] omap-sham: remove unnecessary local variable
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 03/11] omap-sham: replace flags bit mask with bit number
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 04/11] omap-sham: replace flags operation with atomic bit operations
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• [PATCH 00/11] crypto: omap-sham driver fixes
  • From: Dmitry Kasatkin <dmitry.s.kasatkin@xxxxxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Frederick Gazerblezeebe <fgazerblezeebe@xxxxxxxxx>
• [PATCH] crypto: UML build fixes
  • From: Richard Weinberger <richard@xxxxxx>
• Re: loop-aes encrypted root on Fedora 15 using systemd
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] [crypto] testmgr: add xts-aes-256 self-test
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• loop-aes encrypted root on Fedora 15 using systemd
  • From: Frederick Gazerblezeebe <fgazerblezeebe@xxxxxxxxx>
• [PATCH v2] [crypto] testmgr: add xts-aes-256 self-test
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH v2] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE
  • From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
• Re: [PATCH] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] crypto: caam - fix operator precedence in shared descriptor allocation
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/8] x86: Fix set but not used in ghash_async_setkey()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: sha1: modify sha1_update to use SHA1_BLOCK_SIZE
  • From: Mandeep Singh Baines <msb@xxxxxxxxxxxx>
• Re: [PATCH] crypto/testmgr: add xts-aes-256 self-test
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH] crypto/testmgr: add xts-aes-256 self-test
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• [PATCH] crypto: caam - fix operator precedence in shared descriptor allocation
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Crypto Update for 2.6.40
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/8] x86: Fix set but not used in ghash_async_setkey()
  • From: "Gustavo F. Padovan" <padovan@xxxxxxxxxxxxxx>
• Re: [PATCH 1/4] crypto: caam - platform_bus_type migration
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH -next] crypto: fix aesni build on i386
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH -next] crypto: fix aesni build on i386
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: [PATCH] aesni-intel: Merge with fpu.ko
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 4/4] crypto: caam - add support for sha512 variants of existing AEAD algorithms
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 3/4] crypto: caam - remove unused authkeylen from caam_ctx
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 2/4] crypto: caam - fix decryption shared vs. non-shared key setting
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 1/4] crypto: caam - platform_bus_type migration
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: [PATCH 01/10] crypto: mv_cesa - use ablkcipher_request_cast instead of the manual container_of
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] aesni-intel: Merge with fpu.ko
  • From: Andy Lutomirski <luto@xxxxxxx>
• Re: aesni-intel as module = cryptsetup failure
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• aesni-intel as module = cryptsetup failure
  • From: Andrew Lutomirski <luto@xxxxxxx>
• [PATCH 06/10] mv_cesa: refactor copy_src_to_buf()
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 04/10] mv_cesa: print a warning when registration of AES algos fail
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 07/10] mv_cesa: fill inner/outer IV fields only in HMAC case
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 08/10] mv_cesa: move digest state initialisation to a better place
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 02/10] mv_cesa: the descriptor pointer register needs to be set just once
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 10/10] mv_cesa: make count_sgs() null-pointer proof
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 01/10] mv_cesa: use ablkcipher_request_cast instead of the manual container_of
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 03/10] mv_cesa: drop this call to mv_hash_final from mv_hash_finup
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 09/10] mv_cesa: copy remaining bytes to SRAM only when needed
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• [PATCH 05/10] mv_cesa: no need to save digest state after the last chunk
  • From: Phil Sutter <phil.sutter@xxxxxxxxxxxx>
• Re: blowfish from openSSL to kernel cryptoAPI
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] s390: add System z hardware support for CTR mode
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] crypto: caam - fix printk recursion for long error texts
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] s390: add System z hardware support for CTR mode
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] crypto: testmgr: add support for aes ofb mode
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: blowfish from openSSL to kernel cryptoAPI
  • From: Tzvi Chumash <tzvi@xxxxxxxxxxxxxxxx>
• Re: blowfish from openSSL to kernel cryptoAPI
  • From: Emanuele Cesena <emanuele.cesena@xxxxxxxxx>
• Re: blowfish from openSSL to kernel cryptoAPI
  • From: Tzvi Chumash <tzvi@xxxxxxxxxxxxxxxx>
• Re: blowfish from openSSL to kernel cryptoAPI
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/4] crypto: caam - handle interrupt lines shared across rings
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] crypto: caam - fix printk recursion for long error texts
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 1/2] crypto: caam - remove unused keylen from session context
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: [PATCH 1/4] crypto: caam - handle interrupt lines shared across rings
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• blowfish from openSSL to kernel cryptoAPI
  • From: Tzvi Chumash <tzvi@xxxxxxxxxxxxxxxx>
• Announce loop-AES-v3.6c file/swap crypto package
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] s390: add System z hardware support for CTR mode
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] s390: add System z hardware support for CTR mode
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• Re: shash_alg size fields and stomping memory
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH v3] crypto: testmgr: add support for aes ofb mode
  • From: puneets@xxxxxxxxxx
• Re: [PATCH 0/4] crypto: omap-sham driver fixes
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH v2] crypto: testmgr: add support for aes ofb mode
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] crypto: omap-sham driver fixes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] s390: add System z hardware support for CTR mode
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH v2] crypto: testmgr: add support for aes ofb mode
  • From: puneets@xxxxxxxxxx
• [PATCH] crypto: testmgr: add support for aes ofb mode
  • From: puneets@xxxxxxxxxx
• Re: [PATCH] s390: add fallback for unsupported XTS-384 mode
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] s390: add fallback for unsupported XTS-384 mode
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 7/8] tcrypt: disable 384 bit key XTS test
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 7/8] tcrypt: disable 384 bit key XTS test
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/4] crypto: omap-sham - fix concurrent sha1 calculations
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCH 2/4] crypto: omap-sham - remove debug print
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCH 4/4] crypto: omap-sham - hmac calculation bug fix for sha1 base hash
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCH 3/4] crypto: omap-sham - enable driver for EMU chips
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCH 0/4] crypto: omap-sham driver fixes
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH 7/8] tcrypt: disable 384 bit key XTS test
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 8/8] tcrypt: CTR mode speed test for AES
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 3/8] s390: add System z hardware support for XTS mode
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 4/8] s390: add System z hardware support for CTR mode
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 7/8] tcrypt: disable 384 bit key XTS test
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 6/8] s390: cleanup s390 Kconfig options
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 5/8] s390: add System z hardware support for GHASH
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 1/8] s390: extend crypto facility check
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 0/8] (3rd take) add support for z196 CPACF algorithms
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 2/8] s390: cleanup DES code
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 1/1] s390: extend crypto facility check
  • From: jang@xxxxxxxxxxxxxxxxxx
• [PATCH 0/1] add support for z196 CPACF algorithms
  • From: jang@xxxxxxxxxxxxxxxxxx
• shash_alg size fields and stomping memory
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH 1/8] s390:
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/8] s390:
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/4] crypto: caam - handle interrupt lines shared across rings
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: aead: driver side documentation
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 3/4] crypto: caam - remove WAIT-FOR-COMPLETIONs from givencrypt descriptor
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 4/4] crypto: caam - remove duplicate dev_err
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 2/4] crypto: caam - fix queue interface detection
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 1/4] crypto: caam - handle interrupt lines shared across rings
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: aead: driver side documentation
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: [PATCH] crypto: blowfish: Fixed a multi line macro issue
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] crypto: blowfish: Fixed a multi line macro issue
  • From: Aditya Shevade <aditya.shevade@xxxxxxxxx>
• Re: [PATCH] crypto: blowfish: Fixed a multi line macro issue
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/6] drivers/crypto/caam/caamalg.c: introduce missing kfree
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: add S5PV210 advanced crypto engine support.
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: aead: driver side documentation
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] crypto: blkcipher: Fixed some whitespace style issues
  • From: Aditya Shevade <aditya.shevade@xxxxxxxxx>
• [PATCH] crypto: blowfish: Fixed a multi line macro issue
  • From: Aditya Shevade <aditya.shevade@xxxxxxxxx>
• Re: aead: driver side documentation
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: aead: driver side documentation
  • From: Phil Sutter <phil@xxxxxx>
• Re: aead: driver side documentation
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• aead: driver side documentation
  • From: Phil Sutter <phil@xxxxxx>
• [ANN] Linux Security Summit 2011 - Announcement and CFP
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: loop-aes: It is not longer possible to create a filesystem on an encrypted DVD-RAM
  • From: markus reichelt <ml@xxxxxxxxxxxxxx>
• [PATCH] crypto: add S5PV210 advanced crypto engine support.
  • From: Vladimir Zapolskiy <vzapolskiy@xxxxxxxxx>
• Re: crypto_alg and alignment
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/6] drivers/crypto/caam/caamalg.c: introduce missing kfree
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 2/6] drivers/crypto/caam/caamalg.c: introduce missing kfree
  • From: Julia Lawall <julia@xxxxxxx>
• crypto_alg and alignment
  • From: Vladimir Zapolskiy <vzapolskiy@xxxxxxxxx>
• Re: loop-aes: It is not longer possible to create a filesystem on an encrypted DVD-RAM
  • From: Thomas Siedlich <thomas.siedlich@xxxxxxxxx>
• Re: loop-aes: It is not longer possible to create a filesystem on an encrypted DVD-RAM
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: loop-aes: It is not longer possible to create a filesystem on an encrypted DVD-RAM
  • From: Thomas Siedlich <thomas.siedlich@xxxxxxxxx>
• Crypto Fixes for 2.6.39
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: loop-aes: It is not longer possible to create a filesystem on an encrypted DVD-RAM
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• loop-aes: It is not longer possible to create a filesystem on an encrypted DVD-RAM
  • From: Thomas Siedlich <thomas.siedlich@xxxxxxxxx>
• Re: [PATCH] picoxcell-crypto: fix possible status FIFO overflow
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock - Add SHA-1/256 module for VIA Nano
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• cryptodev rebased
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• RE: [PATCH] RFC4106 AES-GCM Driver - fixed problem with packets that are not multiple of 64bytes
  • From: "Struk, Tadeusz" <tadeusz.struk@xxxxxxxxx>
• Re: [PATCH] RFC4106 AES-GCM Driver - fixed problem with packets that are not multiple of 64bytes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• RE: [PATCH] RFC4106 AES-GCM Driver - fixed problem with packets that are not multiple of 64bytes
  • From: "Struk, Tadeusz" <tadeusz.struk@xxxxxxxxx>
• RE: [PATCH] crypto: padlock - Add SHA-1/256 module for VIA Nano
  • From: <BrillyWu@xxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock - Add SHA-1/256 module for VIA Nano
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] picoxcell-crypto: fix possible status FIFO overflow
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• Re: [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [patch] crypto: caam - ARRAY_SIZE() vs sizeof()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [patch] crypto: caam - dereferencing ERR_PTR on allocation failure
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: caam - standardize device tree naming convention to utilize '-vX.Y'
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: RSA signature verification
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: RSA signature verification
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH] crypto: padlock - Add SHA-1/256 module for VIA Nano
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: RSA signature verification
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: RSA signature verification
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: RSA signature verification
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCH] crypto: padlock - Add SHA-1/256 module for VIA Nano
  • From: <BrillyWu@xxxxxxxxxxxxxx>
• Re: RSA signature verification
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• RSA signature verification
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
  • From: Grant Likely <grant.likely@xxxxxxxxxxxx>
• Re: [patch] crypto: caam - dereferencing ERR_PTR on allocation failure
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: [patch] crypto: caam - ARRAY_SIZE() vs sizeof()
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Crypto Update for 2.6.39
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [patch] crypto: caam - ARRAY_SIZE() vs sizeof()
  • From: Dan Carpenter <error27@xxxxxxxxx>
• [patch] crypto: caam - dereferencing ERR_PTR on allocation failure
  • From: Dan Carpenter <error27@xxxxxxxxx>
• [PATCH] crypto: caam - standardize device tree naming convention to utilize '-vX.Y'
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [RFC v2 PATCH 1/9] crypto: authencesn - Add algorithm to handle IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• Re: [RFC v2 PATCH 1/9] crypto: authencesn - Add algorithm to handle IPsec extended sequence numbers
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC v2 PATCH 1/9] crypto: authencesn - Add algorithm to handle IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] RFC4106 AES-GCM Driver - fixed problem with packets that are not multiple of 64bytes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: add support for the Freescale SEC4/CAAM
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC v2 PATCH 2/9] xfrm: Add basic infrastructure to support IPsec extended sequence numbers
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC v2 PATCH 2/9] xfrm: Add basic infrastructure to support IPsec extended sequence numbers
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [RFC v2 PATCH 2/9] xfrm: Add basic infrastructure to support IPsec extended sequence numbers
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC v2 PATCH 1/9] crypto: authencesn - Add algorithm to handle IPsec extended sequence numbers
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/2] Add struct crypto_alg->cra_check_optimized for crc32c_intel
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• [PATCH 1/2] crypto: Add struct crypto_alg->cra_check_optimized
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• [PATCH 2/2] crypto/crc32c: Add crc32c_cra_check_optimized for crc32c_intel
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• [PATCH 2/3] crypto: add header files for the Freescale SEC4/CAAM
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 3/3] crypto: add support for the Freescale SEC4/CAAM
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 1/3] crypto: add device tree bindings for the Freescale SEC4/CAAM
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH 0/3] crypto: add support for the Freescale SEC4/CAAM
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• [PATCH] RFC4106 AES-GCM Driver - fixed problem with packets that are not multiple of 64bytes
  • From: tadeusz.struk@xxxxxxxxx
• [RFC PATCH] iproute2: Add IPsec extended sequence number support
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 9/9] xfrm: Add user interface for esn and big anti-replay windows
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 8/9] xfrm: Add support for IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 7/9] xfrm: Support anti-replay window size bigger than 32 packets
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 6/9] xfrm: Move IPsec replay detection functions to a separate file
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 5/9] esp6: Add support for IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 4/9] esp4: Add support for IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 3/9] xfrm: Use separate low and high order bits of the sequence numbers in xfrm_skb_cb
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 2/9] xfrm: Add basic infrastructure to support IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 1/9] crypto: authencesn - Add algorithm to handle IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC v2 PATCH 0/9] Add IPsec extended (64-bit) sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH 06/11] esp4: Add support for IPsec extended sequence numbers
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: do not attempt to write to readonly variable
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [RFC 12/12] iscsi-target: Add Makefile/Kconfig and update TCM top level
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• aes-generic.c: what mode is it?
  • From: Kent Borg <kentborg@xxxxxxxx>
• Announce loop-AES-v3.6b file/swap crypto package
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2.6.37.2 1/1] crypto: Uninitialized variable fix.
  • From: Greg KH <gregkh@xxxxxxx>
• [PATCH 2.6.37.2 1/1] crypto: Uninitialized variable fix.
  • From: Atul Sowani <sowani@xxxxxxxxx>
• Development of asynchronous deflate for IPComp
  • From: "Mark Burkley" <crypto-dev@xxxxxxxxxx>
• [PATCH] crypto: do not attempt to write to readonly variable
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH] picoxcell_crypto: add support for the picoxcell crypto engines
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: crypto: sha1 - Add test vector to test partial block processing
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: crypto: sha1 - Add test vector to test partial block processing
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• Re: crypto: sha1 - Add test vector to test partial block processing
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] cifs: Use ecb des kernel crypto APIs instead of local cifs functions
  • From: Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx>
• Re: crypto: sha1 - Add test vector to test partial block processing
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• crypto: sha1 - Add test vector to test partial block processing
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Crypto Fixes for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH](updated) rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey()..
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] picoxcell_crypto: add support for the picoxcell crypto engines
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• [PATCH] cifs: Use ecb des kernel crypto APIs instead of local cifs functions
  • From: shirishpargaonkar@xxxxxxxxx
• RE: [PATCH](updated) rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey()..
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• RE: [PATCH](updated) rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey()..
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• RE: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• RE: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: "Paoloni, Gabriele" <gabriele.paoloni@xxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH] picoxcell_crypto: add support for the picoxcell crypto engines
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• Re: [PATCH] picoxcell_crypto: add support for the picoxcell crypto engines
  • From: Kim Phillips <kim.phillips@xxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• [PATCH] picoxcell_crypto: add support for the picoxcell crypto engines
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: tadeusz.struk@xxxxxxxxx
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: tadeusz.struk@xxxxxxxxx
• Re: crypto: sha-s390 - Reset index after processing partial block
  • From: Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>
• crypto: sha-s390 - Reset index after processing partial block
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• RE: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PATCH 02/16] crypto: omap-sham: don't treat NULL clk as an error
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: mark ghash as fips_allowed
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypt: ablkcipher: remove redundant NULL check
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• encrypt memory before suspending to ram
  • From: "bogdan" <bogdann@xxxxxxx>
• Re: hash finup() issue
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: hash finup() issue
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: hash finup() issue
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: mark ghash as fips_allowed
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Hamid Nassiby <h.nassiby@xxxxxxxxx>
• Re: hash finup() issue
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Hamid Nassiby <h.nassiby@xxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: hash finup() issue
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: mark xts(aes) as fips_allowed
  • From: Jarod Wilson <jarod@xxxxxxxxxx>
• Re: [PATCH] crypt: ablkcipher: remove redundant NULL check
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH] crypt: ablkcipher: remove redundant NULL check
  • From: Davidlohr Bueso <dave@xxxxxxx>
• hash finup() issue
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Announce loop-AES-v3.6a file/swap crypto package
  • From: Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] cifs: Replace cifs md5 hashing functions with kernel crypto APIs
  • From: Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx>
• Re: [PATCH] cifs: Replace cifs md5 hashing functions with kernel crypto APIs
  • From: "Stefan (metze) Metzmacher" <metze@xxxxxxxxx>
• Re: [PATCH] cifs: Replace cifs md5 hashing functions with kernel crypto APIs
  • From: Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx>
• Re: [PATCH] cifs: Replace cifs md5 hashing functions with kernel crypto APIs
  • From: Jeff Layton <jlayton@xxxxxxxxxx>
• [PATCH] cifs: Replace cifs md5 hashing functions with kernel crypto APIs
  • From: shirishpargaonkar@xxxxxxxxx
• Re: [PATCH] Add RNG support to AF_ALG (v2)
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG (v2)
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG (v2)
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG (v2)
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG (v2)
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: [PATCH -v2 1/6] functions to either extract or create av_ pair/ti_info blob
  • From: Shirish Pargaonkar <shirishpargaonkar@xxxxxxxxx>
• [PATCH] cifs: Replace remaining use of md5 hashing functions local to cifs with kernel crypto APIs
  • From: shirishpargaonkar@xxxxxxxxx
• [PATCH -v2 1/6] functions to either extract or create av_ pair/ti_info blob
  • From: shirishpargaonkar@xxxxxxxxx
• RE: [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: "Struk, Tadeusz" <tadeusz.struk@xxxxxxxxx>
• [PATCH] rfc4106, Intel, AES-NI: Don't leak memory in rfc4106_set_hash_subkey().
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: RSA verification in the kernel
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: RSA verification in the kernel
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: RSA verification in the kernel
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: RSA verification in the kernel
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• RSA verification in the kernel
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH 01/16] crypto: omap-aes: don't treat NULL clk as an error
  • From: Tobias Karnat <tobias.karnat@xxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 01/16] crypto: omap-aes: don't treat NULL clk as an error
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• Re: [PATCH 01/16] crypto: omap-aes: don't treat NULL clk as an error
  • From: Tobias Karnat <tobias.karnat@xxxxxxxxxxxxxx>
• Re: [PATCH 02/16] crypto: omap-sham: don't treat NULL clk as an error
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH 01/16] crypto: omap-aes: don't treat NULL clk as an error
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: Why are there multiple defines of scatter_walk?
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Disregard my last question I found out the answer
  • From: Mark Allyn <allyn@xxxxxxxx>
• Why are there multiple defines of scatter_walk?
  • From: Mark Allyn <allyn@xxxxxxxx>
• Re: [PATCH 02/16] crypto: omap-sham: don't treat NULL clk as an error
  • From: Aaro Koskinen <aaro.koskinen@xxxxxxxxx>
• Re: [PATCH 01/16] crypto: omap-aes: don't treat NULL clk as an error
  • From: Aaro Koskinen <aaro.koskinen@xxxxxxxxx>
• [PATCH 01/16] crypto: omap-aes: don't treat NULL clk as an error
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• [PATCH 02/16] crypto: omap-sham: don't treat NULL clk as an error
  • From: Jamie Iles <jamie@xxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Dag Arne Osvik <da@xxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Nikos Mavrogiannopoulos <nmav@xxxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Hamid Nassiby <h.nassiby@xxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• hwrng: via_rng - Fix memory scribbling on some CPUs
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• crypto: padlock - Move padlock.h into include/crypto
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Mihai Donțu <mihai.dontu@xxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Pavel Roskin <proski@xxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Update for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: [PATCH] crypto: use __devexit not __exit in n2_unregister_algs
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Crypto Update for 2.6.38
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: use __devexit not __exit in n2_unregister_algs
  • From: Dennis Gilmore <dgilmore@xxxxxxxxxx>
• Re: [PATCH] crypto: use __devexit not __exit in n2_unregister_algs
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: [PATCH 05/32] crypto: mark crypto workqueues CPU_INTENSIVE
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: dont return PTR_ERR() of wrong pointer
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: ripemd - Set module author and update email address.
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 05/32] crypto: mark crypto workqueues CPU_INTENSIVE
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH] crypto: dont return PTR_ERR() of wrong pointer
  • From: roel kluin <roel.kluin@xxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Larry Finger <Larry.Finger@xxxxxxxxxxxx>
• Re: 2.6.37-rc7: Regression: b43: crashes in hwrng_register()
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: crypto accelerator driver problems
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] omap-sham: backlog handling fix
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/1] crypto: omap-sham backlog handling fix
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCH 1/1] omap-sham: backlog handling fix
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: unmet direct dependencies (CRYPTO && EXPERIMENTAL)
  • From: Toralf Förster <toralf.foerster@xxxxxx>
• Re: unmet direct dependencies (CRYPTO && EXPERIMENTAL)
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• unmet direct dependencies (CRYPTO && EXPERIMENTAL)
  • From: Toralf Förster <toralf.foerster@xxxxxx>
• [PATCH] crypto: ripemd - Set module author and update email address.
  • From: Adrian-Ken Rueegsegger <ken@xxxxxxxxxxx>
• Improving SHA-1 performance with Intel SSE3
  • From: Phil Sutter <phil@xxxxxx>
• Fwd: crypto accelerator driver problems
  • From: Hamid Nassiby <h.nassiby@xxxxxxxxx>
• Re: [PATCH -next] crypto: fix af_alg memory_allocated data type
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• crypto accelerator driver problems
  • From: Hamid Nassiby <h.nassiby@xxxxxxxxx>
• [PATCH -next] crypto: fix af_alg memory_allocated data type
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: Crypto Fixes for 2.6.37
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Fixes for 2.6.37
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: Crypto Fixes for 2.6.37
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Crypto Fixes for 2.6.37
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: ghash-clmulni-intel_glue needs err.h
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: ghash-clmulni-intel_glue needs err.h
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Questions on ahash
  • From: Mark Allyn <allyn@xxxxxxxx>
• Re: [PATCH 2/3] RFC4106 AES-GCM Driver Using Intel New Instructions
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] Add RNG support to AF_ALG (v2)
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: Crypto Hardware Drivers?
  • From: Kent Borg <kentborg@xxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG
  • From: Miloslav Trmac <mitr@xxxxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: Crypto Hardware Drivers?
  • From: Tobias Karnat <tobias.karnat@xxxxxxxxxxxxxx>
• Re: [PATCH] Add RNG support to AF_ALG
  • From: Miloslav Trmac <mitr@xxxxxxxxxx>
• [PATCH] Add RNG support to AF_ALG
  • From: Neil Horman <nhorman@xxxxxxxxxxxxx>
• Re: [PATCH 2/3 v2] RFC4106 AES-GCM Driver Using Intel New Instructions - fixed build with binutils 2.16
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [CRYPTO] skein hash updated
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3)
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH 2/3 v2] RFC4106 AES-GCM Driver Using Intel New Instructions - fixed build with binutils 2.16
  • From: tadeusz.struk@xxxxxxxxx
• Re: [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3)
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Crypto Hardware Drivers?
  • From: Kent Borg <kentborg@xxxxxxxx>
• [PATCH 1/3] xfrm: Add Traffic Flow Confidentiality padding XFRM attribute
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3)
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 3/3] xfrm: Traffic Flow Confidentiality for IPv6 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• Re: [PATCH v1.5 5/5] keys: add new key-type encrypted
  • From: David Howells <dhowells@xxxxxxxxxx>
• Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• Re: [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Make sure sk_security is initialized on accept()ed sockets
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
  • From: Harald Welte <HaraldWelte@xxxxxxxxxxx>
• Re: [PATCH v1.5 5/5] keys: add new key-type encrypted
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
  • From: Phil Sutter <phil@xxxxxx>
• Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
  • From: Phil Sutter <phil@xxxxxx>
• [PATCH 1/3] xfrm: Add Traffic Flow Confidentiality padding XFRM attribute
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v2)
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 3/3] xfrm: Traffic Flow Confidentiality for IPv6 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• Re: [PATCHv2 0/6] omap-aes off mode and error handling fixes
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH 3/5] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/5] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• http://eprint.iacr.org/2010/594 (Access Based Cache Attacks on AES) a problem?
  • From: Christoph Sievers <christoph.sievers@xxxxxxxxx>
• Re: [PATCH v1.5 5/5] keys: add new key-type encrypted
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH] Make sure sk_security is initialized on accept()ed sockets
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH] Add missing lockdep class names
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• RE: [PATCH 2/3] RFC4106 AES-GCM Driver Using Intel New Instructions
  • From: "Struk, Tadeusz" <tadeusz.struk@xxxxxxxxx>
• Re: [PATCH 3/5] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/5] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• Re: [PATCH 3/5] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Add missing lockdep class names for AF_ALG
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Install <linux/if_alg.h> for user-space applications
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] RFC4106 AES-GCM Driver Using Intel New Instructions
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] RFC4106 AES-GCM Driver Using Intel New Instructions
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] Install <linux/if_alg.h> for user-space applications
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: [PATCH] Install <linux/if_alg.h> for user-space applications
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] Install <linux/if_alg.h> for user-space applications
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: [PATCHv2 0/6] omap-aes off mode and error handling fixes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] RFC v2: AF_ALG auditing
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH 06/11] esp4: Add support for IPsec extended sequence numbers
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH 02/11] crypto: Use scatterwalk_crypto_chain
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: padlock: fix for non-64byte aligned data
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1.5 4/5] keys: add new trusted key-type
  • From: David Safford <safford@xxxxxxxxxxxxxx>
• Re: [PATCH v1.5 4/5] keys: add new trusted key-type
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH 1/5] xfrm: Add Traffic Flow Confidentiality padding XFRM attribute
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 4/5] xfrm: Traffic Flow Confidentiality for IPv6 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 2/5] xfrm: Remove unused ESP padlen field
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 5/5] xfrm: Add TFC padding option to automatically pad to PMTU
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 0/5] xfrm: ESP Traffic Flow Confidentiality padding
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• [PATCH 3/5] xfrm: Traffic Flow Confidentiality for IPv4 ESP
  • From: Martin Willi <martin@xxxxxxxxxxxxxx>
• Re: [PATCH v1.5 3/5] key: add tpm_send command
  • From: David Safford <safford@xxxxxxxxxxxxxx>
• Re: [PATCH v1.5 3/5] key: add tpm_send command
  • From: David Howells <dhowells@xxxxxxxxxx>
• [PATCH] Add missing lockdep class names for AF_ALG
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: crypto: algif_skcipher - Fixed overflow when sndbuf is page aligned
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: crypto: algif_skcipher - Fixed overflow when sndbuf is page aligned
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• crypto: algif_skcipher - Handle unaligned receive buffer
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• crypto: algif_skcipher - Fixed overflow when sndbuf is page aligned
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCHv2 5/6] omap-aes: initialize aes module once per request
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCHv2 4/6] omap-aes: unnecessary code removed
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCHv2 2/6] omap-aes: redundant locking is removed
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCHv2 6/6] omap-aes: checkpatch --file warning fixes
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCHv2 1/6] omap-aes: DMA initialization fixes for OMAP off mode
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCHv2 3/6] omap-aes: error handling implementation improved
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• [PATCHv2 0/6] omap-aes off mode and error handling fixes
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: [PATCH v3 0/8] omap-sham: OMAP SHA1/MD5 driver fixes and improvements
  • From: Dmitry Kasatkin <dmitry.kasatkin@xxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29
  • From: Zimny Lech <napohybelskurwysynom2010@xxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• Re: linux-next: Tree for November 29 (aesni-intel)
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29
  • From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
• Re: linux-next: Tree for November 29
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] crypto: aesni-intel - Fixed build error on x86-32
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1.5 0/5] keys: trusted and encrypted keys
  • From: James Morris <jmorris@xxxxxxxxx>
• question about OCF and crypto API
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• [PATCH v2] crypto: aesni-intel - Fixed build error on x86-32
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• [PATCH] crypto: aesni-intel - Fixed build error on x86-32
  • From: Mathias Krause <minipli@xxxxxxxxxxxxxx>
• crypto: algif_skcipher - Pass on error from af_alg_make_sg
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/8] omap-sham: OMAP SHA1/MD5 driver fixes and improvements
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4] x86, crypto: ported aes-ni implementation to x86
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Crypto: Makefile: Makefile clean up
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 06/49] crypto: Use vzalloc
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 4/4] crypto: algif_skcipher - User-space interface for skcipher operations
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/4] crypto: af_alg - User-space interface for Crypto API
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 3/4] crypto: algif_hash - User-space interface for hash operations
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/4] net - Add AF_ALG macros
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/4] crypto: algif_skcipher - User-space interface for skcipher operations
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] crypto: pcrypt - Fix use after free on padata_free
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• Re: [PATCH] crypto: pcrypt - Fix use after free on padata_free
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] crypto: pcrypt - Fix use after free on padata_free
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [PATCH 5/5] Audit type-specific crypto operations
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 4/5] Audit type-independent events
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 2/5] Add unique IDs to AF_ALG sockets
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 3/5] Add "alg_name" operation to af_alg_type.
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 1/5] Add general crypto auditing infrastructure
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 0/5] RFC v2: AF_ALG auditing
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• Re: [PATCH v1.5 3/5] key: add tpm_send command
  • From: David Safford <safford@xxxxxxxxxxxxxx>
• [PATCH v1.5 5/5] keys: add new key-type encrypted
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1.5 3/5] key: add tpm_send command
  • From: Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>
• Re: [PATCH v1.5 3/5] key: add tpm_send command
  • From: David Safford <safford@xxxxxxxxxxxxxx>
• Re: [PATCH v1.5 3/5] key: add tpm_send command
  • From: Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>
• Re: [PATCH v1.5 2/5] tpm: add module_put wrapper
  • From: Serge Hallyn <serge.hallyn@xxxxxxxxxxxxx>
• [PATCH v1.5 3/5] key: add tpm_send command
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [PATCH v1.5 1/5] lib: hex2bin converts ascii hexadecimal string to binary
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [PATCH v1.5 4/5] keys: add new trusted key-type
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [PATCH v1.5 0/5] keys: trusted and encrypted keys
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [PATCH v1.5 2/5] tpm: add module_put wrapper
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/5] Add general crypto auditing infrastructure
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: [PATCH 1/5] Add general crypto auditing infrastructure
  • From: Miloslav Trmac <mitr@xxxxxxxxxx>
• Re: [PATCH 1/5] Add general crypto auditing infrastructure
  • From: Eric Paris <eparis@xxxxxxxxxx>
• Re: crypto_shash_digest API
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxxx>
• crypto_shash_digest API
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [PATCH 5/5] Audit type-specific crypto operations
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 4/5] Audit type-independent events
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 1/5] Add general crypto auditing infrastructure
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 3/5] Add "alg_name" operation to af_alg_type.
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• [PATCH 2/5] Add unique IDs to AF_ALG sockets
  • From: Miloslav Trmač <mitr@xxxxxxxxxx>
• RFC: AF_ALG auditing
  • From: Miloslav Trmac <mitr@xxxxxxxxxx>
• Re: [PATCH v1.4 5/5] keys: add new key-type encrypted
  • From: Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx>
• [RFC] [PATCH] iproute2: Add IPsec extended sequence number support
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>
• [RFC] [PATCH 11/11] xfrm: Add user interface for esn and big anti-replay windows
  • From: Steffen Klassert <steffen.klassert@xxxxxxxxxxx>