scrypt  

Messages by Thread

• scrypt 1.3.3 released Colin Percival
• Please test: scrypt 1.3.2.99 Colin Percival
  • Re: Please test: scrypt 1.3.2.99 Simon Josefsson
  • Re: Please test: scrypt 1.3.2.99 Graham Percival
  • Re: Please test: scrypt 1.3.2.99 Graham Percival
  • Re: Please test: scrypt 1.3.2.99 Simon Josefsson
  • Re: Please test: scrypt 1.3.2.99 Graham Percival
  • Re: Please test: scrypt 1.3.2.99 Simon Josefsson
  • Re: Please test: scrypt 1.3.2.99 Graham Percival
• scrypt 1.3.2 released Colin Percival
• Please test: scrypt 1.3.1.99 Colin Percival
• Miscompilation under strict C aliasing rules Quentin Carbonneaux
  • Re: Miscompilation under strict C aliasing rules Colin Percival
  • Re: Miscompilation under strict C aliasing rules Graham Percival
  • Re: Miscompilation under strict C aliasing rules Solar Designer
  • Re: Miscompilation under strict C aliasing rules Quentin Carbonneaux
  • Re: Miscompilation under strict C aliasing rules Graham Percival
• scrypt 1.3.1 released Colin Percival
• Please test: scrypt 1.3.0.99 Colin Percival
• scrypt 1.3.0 released Colin Percival
  • Re: scrypt 1.3.0 released Ted Unangst
  • Re: scrypt 1.3.0 released Colin Percival
  • Re: scrypt 1.3.0 released Graham Percival
  • Re: scrypt 1.3.0 released Ted Unangst
  • Re: scrypt 1.3.0 released Graham Percival
• Please test: scrypt 1.2.99.1 Colin Percival
• Please test: scrypt 1.2.99 Colin Percival
  • Re: Please test: scrypt 1.2.99 James Turner
  • Re: Please test: scrypt 1.2.99 James Turner
  • Re: Please test: scrypt 1.2.99 Graham Percival
  • Re: Please test: scrypt 1.2.99 Colin Percival
  • Re: Please test: scrypt 1.2.99 Graham Percival
  • Re: Please test: scrypt 1.2.99 James Turner
  • Re: Please test: scrypt 1.2.99 James Turner
  • Re: Please test: scrypt 1.2.99 jungle boogie
  • Re: Please test: scrypt 1.2.99 Graham Percival
  • Re: Please test: scrypt 1.2.99 jungle boogie
• Security bits Dmitry Chestnykh
  • Re: Security bits Colin Percival
  • Re: Security bits Dmitry Chestnykh
• scrypt 1.2.1 released Colin Percival
• Please test: scrypt 1.2.1a Colin Percival
  • Please test: scrypt 1.2.1a Colin Percival
  • Re: Please test: scrypt 1.2.1a Christoph Borsbach
  • Re: Please test: scrypt 1.2.1a Graham Percival
• scryptenc_buf/scryptdec_buf and key stores Joacim Grebenö
• ' command -p' in Makefile.in Sebastian Messmer
  • Re: ' command -p' in Makefile.in Graham Percival
  • Re: ' command -p' in Makefile.in Sebastian Messmer
• scrypt command line tool - file format? danielw
  • Re: scrypt command line tool - file format? Dmitry Chestnykh
  • Re: scrypt command line tool - file format? danielw
• Use MD2 - RC4 for Scrypt Ryan Carboni
  • Re: Use MD2 - RC4 for Scrypt Colin Percival
• Re: Using scrypt as a library Colin Percival
• Spritz with Scrypt Ryan Carboni
  • Re: Spritz with Scrypt Colin Percival
• scrypt: Decrypting file would require too much memory Christoph Borsbach
  • Re: scrypt: Decrypting file would require too much memory Dmitry Chestnykh
  • Re: scrypt: Decrypting file would require too much memory Colin Percival
  • Re: scrypt: Decrypting file would require too much memory Christoph Borsbach
  • Re: scrypt: Decrypting file would require too much memory Colin Percival
  • Re: scrypt: Decrypting file would require too much memory Christoph Borsbach
  • Re: scrypt: Decrypting file would require too much memory Colin Percival
  • Re: scrypt: Decrypting file would require too much memory Christoph Borsbach
  • Re: scrypt: Decrypting file would require too much memory Colin Percival
  • Re: scrypt: Decrypting file would require too much memory Christoph Borsbach
• Modular Crypt Format? James Bellinger
• scrypt 1.2.0 released Colin Percival
• Please test: scrypt 1.2.0b Colin Percival
• Please test: scrypt 1.2.0a Colin Percival
  • Re: Please test: scrypt 1.2.0a jungle Boogie
  • Re: Please test: scrypt 1.2.0a Colin Percival
• chaining multiple key derivation functions together Maricel Gregoraschko
  • Re: chaining multiple key derivation functions together Colin Percival
  • Re: chaining multiple key derivation functions together Maricel Gregoraschko
• Showing progress during scrypt - how good is this idea? danielw
  • Re: Showing progress during scrypt - how good is this idea? Dmitry Chestnykh
• How much data should I request from scrypt? danielw
  • Re: How much data should I request from scrypt? Bill Cox
• Can someone help me estimate the costs of doing this? danielw
  • Re: Can someone help me estimate the costs of doing this? danielw
  • Re: Can someone help me estimate the costs of doing this? Ray Callaghan
• identical input, different output? Maarten Billemont
  • Re: identical input, different output? Colin Percival
  • Re: identical input, different output? danielw
  • Re: identical input, different output? Colin Percival
  • Re: identical input, different output? Arnold Reinhold
  • Re: identical input, different output? Colin Percival
  • Re: identical input, different output? Solar Designer
  • Re: identical input, different output? Solar Designer
  • Re: identical input, different output? Solar Designer
  • Re: identical input, different output? Robert Ransom
  • Re: identical input, different output? Solar Designer
  • Re: identical input, different output? Arnold Reinhold
  • Re: identical input, different output? Ray Callaghan
  • Re: identical input, different output? Solar Designer
  • Re: identical input, different output? Ron Garret
  • Re: identical input, different output? danielw
  • Re: identical input, different output? Ray Callaghan
  • Re: identical input, different output? danielw
  • Re: identical input, different output? Solar Designer
• scrypt has three different implementations of crypto_scrypt(), ref, sse, and nosse. What do they mean? danielw
  • Re: scrypt has three different implementations of crypto_scrypt(), ref, sse, and nosse. What do they mean? Colin Percival
  • Re: scrypt has three different implementations of crypto_scrypt(), ref, sse, and nosse. What do they mean? danielw
• Stand-alone code for scrypt danielw
  • Re: Stand-alone code for scrypt danielw
  • Re: Stand-alone code for scrypt danielw
  • Re: Stand-alone code for scrypt danielw
  • Re: Stand-alone code for scrypt Iburi Noc
  • Re: Stand-alone code for scrypt Colin Percival
• Scrypt security proof weakness? Ryan Carboni
• OS support for scrypt Nicolai
  • Re: OS support for scrypt Colin Percival
  • Re: OS support for scrypt Solar Designer
• Scrypt using SHA-3 Ryan Carboni
  • Re: Scrypt using SHA-3 Laurens Van Houtven
  • Re: Scrypt using SHA-3 Colin Percival
  • Re: Scrypt using SHA-3 Ryan Carboni
  • Re: Scrypt using SHA-3 Colin Percival
• Debian Packaging Build Patches (aka bike shed painting) Barak A. Pearlmutter
  • Re: Debian Packaging Build Patches (aka bike shed painting) Colin Percival
• Behaviour with Null Bytes Andrew Dunham
  • Re: Behaviour with Null Bytes Colin Percival
  • Re: Behaviour with Null Bytes Andrew Dunham
• Small fixes for compiling on Windows Dāvis Mosāns
  • Re: Small fixes for compiling on Windows Dāvis Mosāns
  • Re: Small fixes for compiling on Windows Dāvis Mosāns
• Scrypt code repository? Dāvis Mosāns
  • Re: Scrypt code repository? Colin Percival
• Scrypt as a filter Matthew Pherigo
• Building scrypt on Windows using Visual Studio 2008 Dinesh Shanbhag
  • Re: Building scrypt on Windows using Visual Studio 2008 Ted Unangst
  • Re: Building scrypt on Windows using Visual Studio 2008 Dinesh Shanbhag
• Re: [Cryptography] Why don't we protect passwords properly? Arnold Reinhold
  • Re: [Cryptography] Why don't we protect passwords properly? Krisztián Pintér
  • A modification to scrypt to reduce side channel risk Arnold Reinhold
  • Re: A modification to scrypt to reduce side channel risk Krisztián Pintér
  • Re: A modification to scrypt to reduce side channel risk Colin Percival
  • Re: A modification to scrypt to reduce side channel risk Bill Cox
  • Re: [Cryptography] A modification to scrypt to reduce side channel risk Jerry Leichter
  • Re: A modification to scrypt to reduce side channel risk Arnold Reinhold
• Is a constant time string compare necessary? Laurens Van Houtven
  • Re: Is a constant time string compare necessary? Solar Designer
• Canonical way to invoke the KDF? Laurens Van Houtven
  • Re: Canonical way to invoke the KDF? Kevin Cantu
  • Re: Canonical way to invoke the KDF? Colin Percival
  • Re: Canonical way to invoke the KDF? Ron Garret
  • Re: Canonical way to invoke the KDF? Colin Percival
  • Re: Canonical way to invoke the KDF? Ron Garret
  • scrypt with "odd" r or N (Re: Canonical way to invoke the KDF?) Solar Designer
  • Re: scrypt with "odd" r or N (Re: Canonical way to invoke the KDF?) Colin Percival
  • Re: scrypt with "odd" r or N (Re: Canonical way to invoke the KDF?) Solar Designer
  • Re: scrypt with "odd" r or N (Re: Canonical way to invoke the KDF?) Solar Designer
  • Re: scrypt with "odd" r or N (Re: Canonical way to invoke the KDF?) Colin Percival
  • Re: Canonical way to invoke the KDF? Laurens Van Houtven
• Test vectors vampire7
• small man page patch Jean-Philippe Ouellet
• Possible double close in code Barry Steyn
  • Re: Possible double close in code Colin Percival
• [ANN] scrypt command-line utility and library JK
  • Re: [ANN] scrypt command-line utility and library Solar Designer
  • Re: [ANN] scrypt command-line utility and library JK
  • Re: [ANN] scrypt command-line utility and library Solar Designer
  • Re: [ANN] scrypt command-line utility and library JK
• Re: Scrypt questions Solar Designer
• scrypt TMTO in numbers Solar Designer
• scrypt encryption utility - choice of IV/nonce (and command line interface) Derek (Tarsnap)
  • Re: scrypt encryption utility - choice of IV/nonce (and command line interface) Colin Percival
  • Re: scrypt encryption utility - choice of IV/nonce (and command line interface) Derek (Tarsnap)
  • Re: scrypt encryption utility - choice of IV/nonce (and command line interface) Colin Percival
  • Re: scrypt encryption utility - choice of IV/nonce (and command line interface) Derek (Tarsnap)
• scrypt Integerify Solar Designer
  • Re: scrypt Integerify Solar Designer
  • Re: scrypt Integerify Colin Percival
  • Re: scrypt Integerify Solar Designer
• optimized/specialized/revised scrypt implementations Solar Designer
  • Re: optimized/specialized/revised scrypt implementations Colin Percival
  • Re: optimized/specialized/revised scrypt implementations Solar Designer
• Re: scrypt time-memory tradeoff Solar Designer
  • Re: scrypt time-memory tradeoff Solar Designer
  • Re: scrypt time-memory tradeoff Colin Percival
  • Re: scrypt time-memory tradeoff Solar Designer
  • Re: scrypt time-memory tradeoff Colin Percival
  • Re: scrypt time-memory tradeoff Colin Percival
  • Re: scrypt time-memory tradeoff Solar Designer
  • Re: scrypt time-memory tradeoff Colin Percival
• scrypt's malloc() alignment Solar Designer
  • Re: scrypt's malloc() alignment Solar Designer
  • Re: scrypt's malloc() alignment Colin Percival
  • Re: scrypt's malloc() alignment Solar Designer
• crypto_scrypt-sse.c speedup Solar Designer
  • Re: crypto_scrypt-sse.c speedup Colin Percival
  • Re: crypto_scrypt-sse.c speedup Solar Designer
  • Re: crypto_scrypt-sse.c speedup Solar Designer
  • Re: crypto_scrypt-sse.c speedup Solar Designer
  • Re: crypto_scrypt-sse.c speedup Colin Percival
  • Re: crypto_scrypt-sse.c speedup Solar Designer
  • Re: crypto_scrypt-sse.c speedup Solar Designer
  • Re: crypto_scrypt-sse.c speedup Colin Percival

• Earlier messages