sci.crypt

• Date Index

---

• x.509 issuer subject - no match exploits, MajorSoul
• Re: REPOST: Generic code breaking, Douglas A. Gwyn
• timestamp based protocol, cicap
  • Re: timestamp based protocol, stan
    • Re: timestamp based protocol, cicap
      • Re: timestamp based protocol, stan
• Re: Get Rich, Luc The Perverse
  • Message not available
    • Re: Get Rich, David Taylor
      • Message not available
      • Re: Get Rich, David Taylor
      • Re: Get Rich, Luc The Perverse
      • Message not available
      • Re: Get Rich, Luc The Perverse
• Problem is "pure math", jstevh
  • Re: Problem is "pure math", Anon E. Maus
    • Re: Problem is "pure math", googleuser
• Re: REPOST: Osama and the J. Edgar Hoover Memorial Vacuum Cleaner, christo
• REPOST: Enig4, crypticator
• Enig4, crypticator
  • Re: Enig4, Joseph Ashwood
    • Re: Enig4, crypticator
• Idle curiosity (ieee bitorder), Tom St Denis
  • Re: Idle curiosity (ieee bitorder), BRG
    • Re: Idle curiosity (ieee bitorder), Tom St Denis
      • Re: Idle curiosity (ieee bitorder), BRG
      • Re: Idle curiosity (ieee bitorder), Tom St Denis
      • REPOST: Re: Idle curiosity (ieee bitorder), Tom St Denis
      • REPOST: Re: Idle curiosity (ieee bitorder), BRG
    • REPOST: Re: Idle curiosity (ieee bitorder), Tom St Denis
  • REPOST: Re: Idle curiosity (ieee bitorder), BRG
  • <Possible follow-ups>
  • Idle curiosity (ieee bitorder), BRG
• Are Our Political Leaders Really as Mad as We Suspect? Read Here!, ragnell
• 3-DES, M5vip
  • Re: 3-DES, Joseph Ashwood
    • Re: 3-DES, stan
      • Re: 3-DES, Joseph Ashwood
      • Re: 3-DES, stan
      • REPOST: Re: 3-DES, Joseph Ashwood
  • <Possible follow-ups>
  • 3-DES, M5vip
    • Re: 3-DES, Joseph Ashwood
    • REPOST: Re: 3-DES, Joseph Ashwood
• hi, nk
• *** surviving my new CANCEL attack***, Francois Grieu
  • Re: *** surviving my new CANCEL attack***, Juuso Hukkanen
  • Re: *** surviving my new CANCEL attack***, JP LR
    • Re: *** surviving my new CANCEL attack***, Luc The Perverse
    • REPOST: Re: *** surviving my new CANCEL attack***, Luc The Perverse
  • REPOST: Re: *** surviving my new CANCEL attack***, JP LR
  • Re: *** surviving my new CANCEL attack***, John Savard
    • Re: *** surviving my new CANCEL attack***, Luc The Perverse
  • REPOST: Re: *** surviving my new CANCEL attack***, John Savard
  • Re: *** surviving my new CANCEL attack***, Francois Grieu
    • Re: *** surviving my new CANCEL attack***, Phil Carmody
      • Re: *** surviving my new CANCEL attack***, Grumble
      • Re: *** surviving my new CANCEL attack***, Phil Carmody
      • Re: *** surviving my new CANCEL attack***, cryptonom@xxxxxxx
      • Re: *** surviving my new CANCEL attack***, Francois Grieu
      • Re: *** surviving my new CANCEL attack***, Phil Carmody
• Decode, Enigma
  • Re: Decode, Sebastian Gottschalk
• Proof doesn't work, examples don't work, jstevh
  • Re: Proof doesn't work, examples don't work, Volker Hetzer
• Q: How to test new hash algorithm?, Martin Hvidberg
  • Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
    • Re: Q: How to test new hash algorithm?, Martin Hvidberg
      • Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
      • Re: Q: How to test new hash algorithm?, Martin Hvidberg
      • REPOST: Re: Q: How to test new hash algorithm?, Martin Hvidberg
  • Re: Q: How to test new hash algorithm?, Kristian Gjøsteen
    • Re: Q: How to test new hash algorithm?, Martin Hvidberg
      • Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
      • Re: Q: How to test new hash algorithm?, Martin Hvidberg
      • Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
      • REPOST: Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
      • REPOST: Re: Q: How to test new hash algorithm?, Martin Hvidberg
      • Re: Q: How to test new hash algorithm?, Mike Amling
      • REPOST: Re: Q: How to test new hash algorithm?, Mike Amling
      • Re: Q: How to test new hash algorithm?, Carlos Moreno
  • Re: How to test new hash algorithm?, Joseph Ashwood
  • Re: Q: How to test new hash algorithm?, Martin Hvidberg
    • Re: Q: How to test new hash algorithm?, Unruh
      • Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
      • REPOST: Re: Q: How to test new hash algorithm?, Sebastian Gottschalk
    • REPOST: Re: Q: How to test new hash algorithm?, Unruh
  • REPOST: Re: Q: How to test new hash algorithm?, Martin Hvidberg
• An hash-Encryption algorithm, Neo
  • Re: An hash-Encryption algorithm, Sebastian Gottschalk
    • Re: An hash-Encryption algorithm, Neo
      • Re: An hash-Encryption algorithm, Kristian Gjøsteen
      • Re: An hash-Encryption algorithm, Neo
      • Re: An hash-Encryption algorithm, Kristian Gjøsteen
      • Re: An hash-Encryption algorithm, Neo
      • Re: An hash-Encryption algorithm, Kristian Gjøsteen
      • Re: An hash-Encryption algorithm, Neo
      • Re: An hash-Encryption algorithm, Kristian Gjøsteen
      • Re: An hash-Encryption algorithm, Harald Hanche-Olsen
      • Re: An hash-Encryption algorithm, Neo
      • Re: An hash-Encryption algorithm, Kristian Gjøsteen
      • Re: An hash-Encryption algorithm, Neo
      • REPOST: Re: An hash-Encryption algorithm, Neo
  • Re: An hash-Encryption algorithm, Gregory G Rose
    • Re: An hash-Encryption algorithm, Gregory G Rose
      • Re: An hash-Encryption algorithm, Neo
• X509 question, MajorSoul
  • Re: X509 question, Thomas Pornin
    • Re: X509 question, MajorSoul
      • Re: X509 question, Thomas Pornin
      • Re: X509 question, MajorSoul
      • Re: X509 question, Bryan Olson
      • Re: X509 question, MajorSoul
      • Re: X509 question, MajorSoul
      • Re: X509 question, Thomas Pornin
      • Re: X509 question, MajorSoul@xxxxxxxxx
      • Re: X509 question, Bryan Olson
      • Re: X509 question, MajorSoul@xxxxxxxxx
      • Re: X509 question, Bryan Olson
      • Re: X509 question, MajorSoul@xxxxxxxxx
      • REPOST: Re: X509 question, MajorSoul@xxxxxxxxx
      • REPOST: Re: X509 question, Bryan Olson
      • Re: X509 question, Bryan Olson
      • Re: X509 question, MajorSoul@xxxxxxxxx
      • REPOST: Re: X509 question, MajorSoul@xxxxxxxxx
• Cache Timing attacks on AES : Replication or further Development?, rohit
  • Re: Cache Timing attacks on AES : Replication or further Development?, Tom St Denis
    • Re: Cache Timing attacks on AES : Replication or further Development?, rohit
      • Re: Cache Timing attacks on AES : Replication or further Development?, Tom St Denis
  • Re: Cache Timing attacks on AES : Replication or further Development?, BRG
  • Re: Cache Timing attacks on AES : Replication or further Development?, Phil Carmody
    • Re: Cache Timing attacks on AES : Replication or further Development?, stan
      • Re: Cache Timing attacks on AES : Replication or further Development?, Tom St Denis
      • Re: Cache Timing attacks on AES : Replication or further Development?, stan
      • Re: Cache Timing attacks on AES : Replication or further Development?, Tom St Denis
      • Re: Cache Timing attacks on AES : Replication or further Development?, stan
      • Re: Cache Timing attacks on AES : Replication or further Development?, rohit
      • REPOST: Re: Cache Timing attacks on AES : Replication or further Development?, stan
  • Re: Cache Timing attacks on AES : Replication or further Development?, karl malbrain
• Osama and the J. Edgar Hoover Memorial Vacuum Cleaner, ragnell
• Call for Papers: Special Issue on Security Certification, imecs_2006
• miller rabin test, cicap
  • Re: miller rabin test, Sebastian Gottschalk
    • Re: miller rabin test, cicap
  • Re: miller rabin test, Pubkeybreaker
    • Re: miller rabin test, Mike Amling
      • Re: miller rabin test, Unruh
• codebreaking puzzle, Fawle R
  • Re: codebreaking puzzle, Enigma
  • <Possible follow-ups>
  • Codebreaking puzzle, Enigma
    • Message not available
      • Re: REPOST: Re: Codebreaking puzzle, Douglas A. Gwyn
      • Re: REPOST: Re: Codebreaking puzzle, David Taylor
• Generic code breaking, enigma
• Cryptanalysis, chaoticseth
  • <Possible follow-ups>
  • Cryptanalysis, Fawle R
• OpenSSL receives FIPS 140-2 certification, Paul Rubin
  • Re: OpenSSL receives FIPS 140-2 certification, Tom St Denis
  • Message not available
    • Re: REPOST: Re: OpenSSL receives FIPS 140-2 certification, Douglas A. Gwyn
• Hash only (Pepper) data transmission, Lars Schoening
  • Re: Hash only (Pepper) data transmission, Lars Schoening
• doubts about signature, cicap
  • Re: doubts about signature, David Wagner
    • Re: doubts about signature, cicap
      • Re: doubts about signature, David Wagner
• ANNOUNCE: L14 -> L15, robin_carey5
• Number of iterations in PKCS#5, Jostein Tveit
  • Re: Number of iterations in PKCS#5, Joseph Ashwood
• Public Key Encryption: The Weakest Link, TwistyCreek
  • Re: Public Key Encryption: The Weakest Link, Tino Schwarze
    • Re: Public Key Encryption: The Weakest Link, Gregory G Rose
    • Re: Public Key Encryption: The Weakest Link, Luc The Perverse
  • Re: Public Key Encryption: The Weakest Link, Kristian Gjøsteen
  • Re: Public Key Encryption: The Weakest Link, Joseph Ashwood
  • Re: Public Key Encryption: The Weakest Link, Steven Jones
• Sources to decript wanted, Alex
  • Re: Sources to decript wanted, scottsanz
• *** Surviving this new CANCEL attack ***, Francois Grieu
  • Re: *** Surviving this new CANCEL attack ***, Kristian Gjøsteen
• Proof, demonstration useless, what?, jstevh
• Need help decipher...., Shane
  • Re: Need help decipher...., Peter Pearson
    • Re: Need help decipher...., Shane
      • Re: Need help decipher...., Peter Pearson
      • Re: Need help decipher...., Douglas A. Gwyn
      • Re: Need help decipher...., Shane
      • Re: Need help decipher...., Stefan Krah
      • Re: Need help decipher...., Phil Carmody
      • Re: Need help decipher...., Peter Pearson
      • Re: Need help decipher...., Shane
      • Re: Need help decipher...., Paul Rubin
      • Re: Need help decipher...., Shane
      • Re: Need help decipher...., Paul Rubin
• Virtual Copy of Printed Document, frequencieme
• Simple Python elliptic curves and ECDSA, Peter Pearson
  • Re: Simple Python elliptic curves and ECDSA, Tom St Denis
• Re: none, Douglas A. Gwyn
• the merits of NTRU, Juuso Hukkanen
  • Re: the merits of NTRU, Joseph Ashwood
    • Re: the merits of NTRU, Tom St Denis
• More perspective, factoring, jstevh
  • Re: More perspective, factoring, Ben Livengood
    • Re: More perspective, factoring, jstevh
  • Re: More perspective, factoring, Bruce Stephens
  • Re: More perspective, factoring, Tim Peters
    • Re: More perspective, factoring, Gregory G Rose
      • Re: More perspective, factoring, Tom St Denis
• What will happen, jstevh
• explanation of unilateral authentication nonce based protocol, cicap
  • Re: explanation of unilateral authentication nonce based protocol, David Wagner
• Using Gimp For Key Material, TomFoolery
  • Re: Using Gimp For Key Material, Sebastian Gottschalk
  • Re: Using Gimp For Key Material, TomFoolery
  • Re: Using Gimp For Key Material, Joseph Ashwood
  • Re: Using Gimp For Key Material, Douglas A. Gwyn
• So why lie?, jstevh
  • Re: So why lie?, Sebastian Gottschalk
• break it - protect confidentiality and integrity with symmetric key, 000
  • Re: break it - protect confidentiality and integrity with symmetric key, Tom St Denis
    • Re: break it - protect confidentiality and integrity with symmetric key, 000
      • Re: break it - protect confidentiality and integrity with symmetric key, 000
• protect confidentiality and integrity with symmetric key, 000
  • <Possible follow-ups>
  • protect confidentiality and integrity with symmetric key, 000
• implementing sha1, ness
  • Re: implementing sha1, Will Dickson
    • Re: implementing sha1, ness
      • Re: implementing sha1, ness
      • Re: implementing sha1, Tom St Denis
      • Re: implementing sha1, ness
• Re: Proof of fraud, flawed number theory still taught, David Eather
  • Re: Proof of fraud, flawed number theory still taught, Unruh
  • <Possible follow-ups>
  • Re: Proof of fraud, flawed number theory still taught, Bruce Stephens
  • Re: Proof of fraud, flawed number theory still taught, Proginoskes
• Re: I need some help., Abraham Wolk
• Comparison, datacrush
  • Re: Comparison, Joseph Ashwood
    • Re: Comparison, fatal.serpent
• New attacks on Bluetooth encryption - please clarify, Markus Jansson
• How this algorithm of prime factor decomposition works?, rickyzhang
  • Re: How this algorithm of prime factor decomposition works?, NS
• Encryption used in Oxford English Dictionary, tjwolf
  • Re: Encryption used in Oxford English Dictionary, Paul Rubin
    • Re: Encryption used in Oxford English Dictionary, tjwolf
    • Re: Encryption used in Oxford English Dictionary, tjwolf
  • Re: Encryption used in Oxford English Dictionary, Tino Schwarze
    • Re: Encryption used in Oxford English Dictionary, Paul Rubin
      • Re: Encryption used in Oxford English Dictionary, Tino Schwarze
• simple protocol (execrise), cicap
  • Re: simple protocol (execrise), Kristian Gjøsteen
  • Re: simple protocol (execrise), NS
    • Re: simple protocol (execrise), cicap
      • Re: simple protocol (execrise), NS
      • Re: simple protocol (execrise), Kristian Gjøsteen
• Files Unreadable (.doc, .url, .mht), ftrye38
  • Re: Files Unreadable (.doc, .url, .mht), Sebastian Gottschalk
• OT: Virus spammers getting bolder..., John Savard
  • Re: OT: Virus spammers getting bolder..., Paul Rubin
  • Re: Virus spammers getting bolder..., Luc The Perverse
    • Re: Virus spammers getting bolder..., Jean-Luc Cooke
• What field to study, wschlanger
  • Re: What field to study, Douglas A. Gwyn
• Re: easy stealth encryption?, Douglas A. Gwyn
• [OT] Point of wiping in-memory keys?, Will Dickson
  • Re: [OT] Point of wiping in-memory keys?, Paul Rubin
  • Re: [OT] Point of wiping in-memory keys?, Jean-Luc Cooke
    • Re: [OT] Point of wiping in-memory keys?, Mike Amling
      • Re: [OT] Point of wiping in-memory keys?, Paul Rubin
      • Re: [OT] Point of wiping in-memory keys?, Joseph Ashwood
    • Re: [OT] Point of wiping in-memory keys?, Colin Percival
      • Re: [OT] Point of wiping in-memory keys?, Sebastian Gottschalk
      • Re: [OT] Point of wiping in-memory keys?, David Wagner
      • Re: [OT] Point of wiping in-memory keys?, Luc The Perverse
      • Re: [OT] Point of wiping in-memory keys?, David Wagner
      • Re: [OT] Point of wiping in-memory keys?, Sebastian Gottschalk
      • Re: [OT] Point of wiping in-memory keys?, David Wagner
      • Re: [OT] Point of wiping in-memory keys?, Mike Amling
      • Re: [OT] Point of wiping in-memory keys?, David Wagner
      • Re: [OT] Point of wiping in-memory keys?, Paul Rubin
      • Re: [OT] Point of wiping in-memory keys?, David Wagner
      • Re: [OT] Point of wiping in-memory keys?, Sebastian Gottschalk
      • Re: [OT] Point of wiping in-memory keys?, Mike Amling
      • Re: [OT] Point of wiping in-memory keys?, David Wagner
      • Re: [OT] Point of wiping in-memory keys?, Bryan Olson
      • Re: [OT] Point of wiping in-memory keys?, Mike Amling
  • Re: [OT] Point of wiping in-memory keys?, nemo_outis
  • Re: [OT] Point of wiping in-memory keys?, Bryan Olson
    • Re: [OT] Point of wiping in-memory keys?, David Taylor
    • Re: [OT] Point of wiping in-memory keys?, Will Dickson
• Chosen attacks, fermisoft
  • Re: Chosen attacks, Unruh
  • Re: Chosen attacks, Francois Grieu
    • Re: Chosen attacks, Gordon Burditt
    • Re: Chosen attacks, Francois Grieu
  • Re: Chosen attacks, Mike Amling
    • Re: Chosen attacks, Mike Nelson
      • Re: Chosen attacks, Unruh
      • Re: Chosen attacks, Luc The Perverse
      • Re: Chosen attacks, Unruh
  • Re: Chosen attacks, Douglas A. Gwyn
• Pre-call for submissions for IEEE Std 1363-2000 revision, William Whyte
• Open positions at Concordia University, Canada, youssef
• Tenure-track faculty positions, youssef
• Electronic Codebook, s_4
  • Re: Electronic Codebook, Paul Rubin
    • Re: Electronic Codebook, s_4
      • Re: Electronic Codebook, Andrew Swallow
      • Re: Electronic Codebook, Mike Scott
      • Re: Electronic Codebook, Andrew Swallow
      • Re: Electronic Codebook, Paul Rubin
  • Re: Electronic Codebook, Douglas A. Gwyn
    • Re: Electronic Codebook, s_4
      • Re: Electronic Codebook, s_4
  • Re: Electronic Codebook, Kristian Gjøsteen
  • Re: Electronic Codebook, Unruh
• AES4_UICE_slides.pdf, Jean Easter
• FlexiProvider: an open source cryptography provider for the JCA/JCE, Martin Döring
  • Re: FlexiProvider: an open source cryptography provider for the JCA/JCE, Mike Amling
    • Re: FlexiProvider: an open source cryptography provider for the JCA/JCE, daniel bleichenbacher
    • Re: FlexiProvider: an open source cryptography provider for the JCA/JCE, daniel bleichenbacher
  • Re: FlexiProvider: an open source cryptography provider for the JCA/JCE, Paul Rubin
• US nu-cu-lear bases.. access is kids stuff :-), Jan Panteltje
  • Re: US nu-cu-lear bases.. access is kids stuff :-), Mxsmanic
    • Re: US nu-cu-lear bases.. access is kids stuff :-), Jan Panteltje
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Mxsmanic
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Jan Panteltje
    • Re: US nu-cu-lear bases.. access is kids stuff :-), Andrew Swallow
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Jan Panteltje
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Mack
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Mxsmanic
      • Re: US nu-cu-lear bases.. access is kids stuff :-), David Eather
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Jan Panteltje
      • Re: US nu-cu-lear bases.. access is kids stuff :-), Mxsmanic
• multi-key encryption algorithm is meaningful?, chaeso
  • Re: multi-key encryption algorithm is meaningful?, Pubkeybreaker
  • Re: multi-key encryption algorithm is meaningful?, Mxsmanic
    • Re: multi-key encryption algorithm is meaningful?, chaeso
      • Re: multi-key encryption algorithm is meaningful?, Phil Carmody
      • Re: multi-key encryption algorithm is meaningful?, chaeso
      • Re: multi-key encryption algorithm is meaningful?, chaeso
      • Re: multi-key encryption algorithm is meaningful?, Bob
      • Re: multi-key encryption algorithm is meaningful?, Mxsmanic
      • Re: multi-key encryption algorithm is meaningful?, Mxsmanic
  • Re: multi-key encryption algorithm is meaningful?, Bryan Olson
    • Re: multi-key encryption algorithm is meaningful?, chaeso
      • Re: multi-key encryption algorithm is meaningful?, Phil Carmody
• OEF for DH?, Tom St Denis
• Why should the primes p and q be safe primes?, bobic
  • Re: Why should the primes p and q be safe primes?, Tom St Denis
    • Re: Why should the primes p and q be safe primes?, Colin Percival
• RSA key length and more, Pesso
  • Re: RSA key length and more, Paul Rubin
  • Re: RSA key length and more, Paul Leyland
    • Re: RSA key length and more, Pubkeybreaker
      • Re: RSA key length and more, Paul Leyland
      • Re: RSA key length and more, Unruh
    • Re: RSA key length and more, Unruh
    • Re: RSA key length and more, sillybanter
• some question about RSA, Wang
  • Re: some question about RSA, Tom St Denis
    • Re: some question about RSA, Wang
      • Re: some question about RSA, Tom St Denis
      • Re: some question about RSA, Wang
      • Re: some question about RSA, Tom St Denis
      • Re: some question about RSA, Wang
      • Re: some question about RSA, Tom St Denis
      • Re: some question about RSA, Wang
  • Re: some question about RSA, Joseph Ashwood
• A New Encryption Algorithm, healyd
  • Re: A New Encryption Algorithm, fbloveu
  • Re: A New Encryption Algorithm, Unruh
    • Re: A New Encryption Algorithm, Luc The Perverse
    • Re: A New Encryption Algorithm, Tom St Denis
      • Re: A New Encryption Algorithm, John Savard
      • Re: A New Encryption Algorithm, Unruh
      • Re: A New Encryption Algorithm, John Savard
      • Re: A New Encryption Algorithm, Unruh
      • Re: A New Encryption Algorithm, John Savard
  • Re: A New Encryption Algorithm, Bill Unruh
• Re: Call for Papers: SAM'06 (part of WORLDCOMP'06), Tom St Denis
  • <Possible follow-ups>
  • Re: Call for Papers: SAM'06 (part of WORLDCOMP'06), Douglas A. Gwyn
    • Re: Call for Papers: SAM'06 (part of WORLDCOMP'06), Pubkeybreaker
    • Re: Call for Papers: SAM'06 (part of WORLDCOMP'06), Colin Percival
• [NEWBIE]vigenere, cicap
  • Re: [NEWBIE]vigenere, Sebastian Gottschalk
    • Re: [NEWBIE]vigenere, Kristian Gjøsteen
      • Re: [NEWBIE]vigenere, Sebastian Gottschalk
      • Re: [NEWBIE]vigenere, Mike Amling
      • Re: [NEWBIE]vigenere, Sebastian Gottschalk
      • Re: [NEWBIE]vigenere, Kristian Gjøsteen
      • Re: [NEWBIE]vigenere, Sebastian Gottschalk
      • Re: [NEWBIE]vigenere, Kristian Gjøsteen
  • Re: [NEWBIE]vigenere, Douglas A. Gwyn
  • Re: [NEWBIE]vigenere, Mike Amling
• Is it a hard problem?, fbloveu
  • Re: Is it a hard problem?, Tom St Denis
    • Re: Is it a hard problem?, fbloveu
  • Re: Is it a hard problem?, Peter Pearson
  • Re: Is it a hard problem?, Paul Rubin
    • Re: Is it a hard problem?, fbloveu
  • Re: Is it a hard problem?, Bryan Olson
    • Re: Is it a hard problem?, fbloveu
      • Re: Is it a hard problem?, Bryan Olson
    • Re: Is it a hard problem?, Pubkeybreaker
• Questoin about the security of Discrete Log Problem, fbloveu
  • Re: Questoin about the security of Discrete Log Problem, Unruh
    • Re: Questoin about the security of Discrete Log Problem, fbloveu
      • Re: Questoin about the security of Discrete Log Problem, Unruh
      • Re: Questoin about the security of Discrete Log Problem, fbloveu
• RSA Security Group - Feel Free to Join -, Information Security
• project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Kasparov
  • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Joseph Ashwood
    • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Mike Amling
      • Re: project - signing (and verifying) a message (text) using DSA(Visual Basic.NET implementation, or VB), David Eather
  • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), elgersmad
  • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Tom St Denis
    • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), The Flavored Coffee Guy
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Tom St Denis
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), kurt wismer
    • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), laughing
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Tom St Denis
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Anon E. Maus
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), laughing
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), laughing
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Pubkeybreaker
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), laughing
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Pubkeybreaker
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Tom St Denis
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), laughing
  • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Berryo
  • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Ichinin
    • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Tom St Denis
      • Re: project - signing (and verifying) a message (text) using DSA (Visual Basic.NET implementation, or VB), Ichinin
• HMAC vs Salt, Hieu
  • Re: HMAC vs Salt, Tom St Denis
    • Re: HMAC vs Salt, Hieu
  • Re: HMAC vs Salt, Joseph Ashwood
  • Re: HMAC vs Salt, Mike Amling
    • Re: HMAC vs Salt, Hieu
  • Re: HMAC vs Salt, Shai Halevi
• DNA used as cipher, christo
  • Re: DNA used as cipher, wbhart
    • Re: DNA used as cipher, Doug
  • Re: DNA used as cipher, Douglas A. Gwyn
  • Re: DNA used as cipher, A. Caspis
    • Re: DNA used as cipher, christo
      • Re: DNA used as cipher, Bob
• Re: blind signature is not blind enough?, Jeff
  • Re: blind signature is not blind enough?, Mike Amling
    • Re: blind signature is not blind enough?, Bryan Olson
• efficiency question about modular exponention operation, laicko
  • Re: efficiency question about modular exponention operation, Tom St Denis
  • Re: efficiency question about modular exponention operation, Mike Scott
  • Re: efficiency question about modular exponention operation, David Wagner
    • Re: efficiency question about modular exponention operation, laicko
      • Re: efficiency question about modular exponention operation, David Wagner
      • Re: efficiency question about modular exponention operation, laicko
      • Re: efficiency question about modular exponention operation, Tom St Denis
      • Re: efficiency question about modular exponention operation, laicko
• Re: rsa key generation question, kaskati2003
  • Re: rsa key generation question, Mike Amling
• How to represent a message as a point M in ECC with Miracl, jean_lee1998id
  • Re: How to represent a message as a point M in ECC with Miracl, Tom St Denis
    • Re: How to represent a message as a point M in ECC with Miracl, Berlid
• RSA encrypt/decrypt in C++ (with OpenSSL), Carlos Moreno
• msieve is FAST!!, wbhart
  • Re: msieve is FAST!!, Phil Carmody
    • Re: msieve is FAST!!, wbhart
    • Re: msieve is FAST!!, Chris Card
      • Re: msieve is FAST!!, wbhart
      • Re: msieve is FAST!!, Chris Card
      • Re: msieve is FAST!!, wbhart
      • Re: msieve is FAST!!, Pubkeybreaker
      • Re: msieve is FAST!!, wbhart
      • Re: msieve is FAST!!, Paul Leyland
• Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Richard Herring
  • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Mxsmanic
    • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Jan Panteltje
      • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Mxsmanic
      • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Richard Herring
      • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Paul Rubin
      • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Jan Panteltje
    • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Richard Herring
      • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Mxsmanic
      • Re: EU decides to keep all connectio ndata for 6 month to 2 years, how to circumvent / elude ?, Richard Herring
• How to construct one-way permutation from one-way function?, dan
  • Re: How to construct one-way permutation from one-way function?, Peter Pearson
  • Re: How to construct one-way permutation from one-way function?, Mike Amling
• Computing big numbers, toorandom@xxxxxxxxx
  • Re: Computing big numbers, ink
    • Re: Computing big numbers, cryptonom
      • Re: Computing big numbers, Paul Rubin
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Paul Rubin
      • porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Paul Rubin
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Gregory G Rose
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Gabriel Lear
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Sevenhundred Elves
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Sevenhundred Elves
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, ink
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, samvaknin
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Tom St Denis
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, Luc The Perverse
      • Re: porting GnuPG to PPC {Re: Computing big numbers}, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
    • Re: Computing big numbers, Eduardo Ruiz
    • Re: Computing big numbers, Eduardo Ruiz
  • Re: Computing big numbers, Michael Harrington
  • Re: Computing big numbers, Pubkeybreaker
    • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Michael Harrington
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, BRG
      • Re: Computing big numbers, David Wagner
      • Re: Computing big numbers, BRG
      • Re: Computing big numbers, daniel bleichenbacher
      • Re: Computing big numbers, Juuso Hukkanen
      • Re: Computing big numbers, Douglas A. Gwyn
      • Re: Computing big numbers, Paul Rubin
      • Re: Computing big numbers, Mike Amling
      • Re: Computing big numbers, David Wagner
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, BRG
      • Re: Computing big numbers, cryptonom
      • Re: Computing big numbers, Paul Rubin
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, cryptonom
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, BRG
      • Re: Computing big numbers, cryptonom@xxxxxxx
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, ink
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Douglas A. Gwyn
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, David Eather
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Douglas A. Gwyn
      • Re: Computing big numbers, Pubkeybreaker
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Paul Rubin
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Paul Rubin
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Erik Naggum
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Gabriel Lear
      • Re: Computing big numbers, Jean-Luc Cooke
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Douglas A. Gwyn
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, Erik Naggum
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Erik Naggum
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, Erik Naggum
      • Re: Computing big numbers, stan
      • Re: Computing big numbers, ink
      • Re: Computing big numbers, cryptonom
      • Re: Computing big numbers, Douglas A. Gwyn
      • Re: Computing big numbers, cryptonom
      • Re: Computing big numbers, Tom St Denis
      • Re: Computing big numbers, cryptonom
  • Re: Computing big numbers, Juuso Hukkanen
• rosary-based low-tech crypto?, johnicholas . hines
  • Re: rosary-based low-tech crypto?, Mike Amling
    • Re: rosary-based low-tech crypto?, johnicholas . hines
      • Re: rosary-based low-tech crypto?, David Eather
  • Re: rosary-based low-tech crypto?, wbhart
  • Re: rosary-based low-tech crypto?, Douglas A. Gwyn
    • Re: rosary-based low-tech crypto?, wbhart
      • Re: rosary-based low-tech crypto?, David Eather
• A factoring algorithm, hart_wb
  • Re: A factoring algorithm, Juuso Hukkanen
    • Re: A factoring algorithm, hart_wb
      • Re: A factoring algorithm, Juuso Hukkanen
      • Re: A factoring algorithm, Juuso Hukkanen
  • Re: A factoring algorithm, Phil Carmody
    • Re: A factoring algorithm, hart_wb
    • Re: A factoring algorithm, hart_wb
    • Re: A factoring algorithm, hart_wb
    • Re: A factoring algorithm, hart_wb
    • Re: A factoring algorithm, hart_wb
  • Re: A factoring algorithm, Bryan Olson
    • Re: A factoring algorithm, Mike Amling
      • Re: A factoring algorithm, Phil Carmody
    • Re: A factoring algorithm, hart_wb
  • Re: A factoring algorithm, Mike Amling
    • Re: A factoring algorithm, hart_wb
      • Re: A factoring algorithm, Bryan Olson
  • Re: A factoring algorithm, Joseph Ashwood
    • Re: A factoring algorithm, JP LR
      • Re: A factoring algorithm, wbhart
    • Message not available
      • Message not available
      • Re: A factoring algorithm, wbhart
    • Message not available
      • Message not available
      • Message not available
      • Re: A factoring algorithm, Chris Card
      • Re: A factoring algorithm, Phil Carmody
      • Re: A factoring algorithm, Chris Card
      • Re: A factoring algorithm, Chris Card
      • Re: A factoring algorithm, Tom St Denis
      • Re: A factoring algorithm, Chris Card
    • Message not available
      • Re: A factoring algorithm, David Wagner
    • Message not available
      • Re: A factoring algorithm, Mike Amling
      • Re: A factoring algorithm, wbhart
  • Re: A factoring algorithm, Pubkeybreaker
    • Re: A factoring algorithm, Phil Carmody
      • Re: A factoring algorithm, David Wagner
      • Re: A factoring algorithm, Phil Carmody
      • Re: A factoring algorithm, David Wagner
      • Re: A factoring algorithm, Phil Carmody
      • Re: A factoring algorithm, wbhart
      • Re: A factoring algorithm, David Wagner
      • Re: A factoring algorithm, Pubkeybreaker
      • Re: A factoring algorithm, wbhart
      • Re: A factoring algorithm, Pubkeybreaker
      • Re: A factoring algorithm, Phil Carmody
    • Re: A factoring algorithm, wbhart
      • Re: A factoring algorithm, wbhart
    • Re: A factoring algorithm, wbhart
      • Re: A factoring algorithm, David Wagner
      • Re: A factoring algorithm, wbhart
      • Re: A factoring algorithm, Paul Rubin
• Re: SIGS How to get the sieving polynoms, hart_wb
• Recommentations for research topic and mentor, truevalue
  • Re: Recommentations for research topic and mentor, David A Molnar
    • Re: Recommentations for research topic and mentor, Carlos Moreno
      • Re: Recommentations for research topic and mentor, David A Molnar
      • Re: Recommentations for research topic and mentor, MrFix3
      • Re: Recommentations for research topic and mentor, David A Molnar
• Double-applied symmetric algorithm, David F
  • Re: Double-applied symmetric algorithm, David Wagner
    • Re: Double-applied symmetric algorithm, Douglas A. Gwyn
      • Re: Double-applied symmetric algorithm, David Wagner
      • Re: Double-applied symmetric algorithm, Tino Schwarze
• Help needed with encryption algorithm, Nemok
  • Re: Help needed with encryption algorithm, Sebastian Gottschalk
    • Re: Help needed with encryption algorithm, Nemok
      • Re: Help needed with encryption algorithm, Jameson King
      • Re: Help needed with encryption algorithm, Nemok
      • Re: Help needed with encryption algorithm, Tom St Denis
      • Re: Help needed with encryption algorithm, Andrew Swallow
      • Re: Help needed with encryption algorithm, Paul Rubin
      • Re: Help needed with encryption algorithm, Nemok
      • Re: Help needed with encryption algorithm, Luc The Perverse
      • Re: Help needed with encryption algorithm, Unruh
      • Re: Help needed with encryption algorithm, Luc The Perverse
      • Re: Help needed with encryption algorithm, Gregory G Rose
      • Re: Help needed with encryption algorithm, Nemok
      • Re: Help needed with encryption algorithm, David Wagner
      • Re: Help needed with encryption algorithm, Joseph Ashwood
      • Re: Help needed with encryption algorithm, Tuna Fish
  • Re: Help needed with encryption algorithm, Tom St Denis
  • Re: Help needed with encryption algorithm, Mike Amling
  • Re: Help needed with encryption algorithm, Unruh
  • Re: Help needed with encryption algorithm, Douglas A. Gwyn
  • Re: Help needed with encryption algorithm, David Wagner
  • Re: Help needed with encryption algorithm, Paul Rubin
  • Re: Help needed with encryption algorithm, Joseph Ashwood
• Biotechnology********Intellectual Property Rights, contactme4u
• Java iButton discontinued, Paul Rubin
• project - signing (and verifying) a message using XTR algorithm (java implementation), Tomasz Leskier
  • Re: project - signing (and verifying) a message using XTR algorithm (java implementation), WiteG
    • Re: project - signing (and verifying) a message using XTR algorithm (java implementation), Tom St Denis
      • Re: project - signing (and verifying) a message using XTR algorithm (java implementation), Tomasz Leskier
      • Re: project - signing (and verifying) a message using XTR algorithm (java implementation), Tom St Denis
      • Re: project - signing (and verifying) a message using XTR algorithm (java implementation), Tomasz Leskier
      • Re: project - signing (and verifying) a message using XTR algorithm (java implementation), Kristian Gjøsteen
• RS-232 random number generator, David Eather
  • Re: RS-232 random number generator, Paul Rubin
    • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Paul Rubin
  • Re: RS-232 random number generator, Mike Amling
    • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Jan Panteltje
      • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Jan Panteltje
      • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Jan Panteltje
      • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Luc The Perverse
      • Re: RS-232 random number generator, Vernon Schryver
      • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Mike Amling
      • Re: RS-232 random number generator, Jan Panteltje
      • Re: RS-232 random number generator, Unruh
  • Re: RS-232 random number generator, Will Dickson
    • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Terry Ritter
      • Re: RS-232 random number generator, David Eather
      • Re: RS-232 random number generator, Mack
      • Re: RS-232 random number generator, Terry Ritter
      • self-appointed expert? {Re: RS-232 random number generator}, cryptonom
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Kristian Gjøsteen
      • Re: self-appointed expert? {Re: RS-232 random number generator}, stan
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom@xxxxxxx
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Tom St Denis
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom@xxxxxxx
      • Re: self-appointed expert? {Re: RS-232 random number generator}, John E. Hadstate
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Mike Amling
      • Re: self-appointed expert? {Re: RS-232 random number generator}, stan
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Paul Rubin
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom@xxxxxxx
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Paul Rubin
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Mike Amling
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom@xxxxxxx
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Mike Amling
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom@xxxxxxx
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Mike Amling
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Bryan Olson
      • Re: self-appointed expert? {Re: RS-232 random number generator}, David Eather
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Phil Carmody
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Paul Rubin
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Mike Amling
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Bill Unruh
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Colin Percival
      • Re: self-appointed expert? {Re: RS-232 random number generator}, Terry Ritter
      • Re: self-appointed expert? {Re: RS-232 random number generator}, cryptonom
• enigmail, evolution with signature and encryption, Peter Schwabe
• PKI question, trusting subordinate CA, hagaiy
• Re: Can you crack this, Siddharam Shingshetty
  • Re: Can you crack this, Luc The Perverse
  • Re: Can you crack this, John E. Hadstate
    • Re: Can you crack this, teslacoils2006
      • Re: Can you crack this, Mike Amling
• how to manage certificate store, jay25dec@xxxxxxxxx
• Typo in "Guide to Elliptic Curve Cryptography", Tom St Denis
  • Re: Typo in "Guide to Elliptic Curve Cryptography", Tom St Denis
    • Re: Typo in "Guide to Elliptic Curve Cryptography", Tom St Denis
  • <Possible follow-ups>
  • Typo in "Guide to Elliptic Curve Cryptography", Tom St Denis
• Re: OEF curve, Kristian Gjøsteen
  • Re: OEF curve, WiteG
    • Re: OEF curve, Darrel Hankerson
    • Re: OEF curve, Kristian Gjøsteen
• Re: AES operation order, Kristian Gjøsteen
• On IVs, Ivan Voras
  • Re: On IVs, Tom St Denis
    • Re: On IVs, Ivan Voras
      • Re: On IVs, Tom St Denis
      • Re: On IVs, Ivan Voras
  • Re: On IVs, David Wagner
    • Re: On IVs, Ivan Voras
• Re: OT: Why include this in your reply?, stan
  • Re: OT: Why include this in your reply?, Gabriel Lear
    • Re: OT: Why include this in your reply?, Phil Carmody
      • Re: OT: Why include this in your reply?, Gabriel Lear
      • Re: OT: Why include this in your reply?, Tom St Denis
      • Re: OT: Why include this in your reply?, Gabriel Lear
      • Re: OT: Why include this in your reply?, Tom St Denis
      • Re: OT: Why include this in your reply?, Gabriel Lear
      • Re: OT: Why include this in your reply?, stan
      • Re: OT: Why include this in your reply?, Gabriel Lear
      • Re: OT: Why include this in your reply?, stan
      • Re: OT: Why include this in your reply?, cryptonom
      • Re: OT: Why include this in your reply?, Phil Carmody
• sending hidden messages, hassan.jameel@xxxxxxxxx
  • Re: sending hidden messages, Peter Fairbrother
  • Re: sending hidden messages, Twittering One
• Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, vedaal
  • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, David Eather
  • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Joseph Ashwood
    • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, vedaal
  • <Possible follow-ups>
  • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Francois Grieu
    • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, David Eather
      • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Francois Grieu
  • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, fermisoft
    • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Jean-Luc Cooke
      • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Tom St Denis
      • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Luc The Perverse
      • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Anon E. Maus
      • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Luc The Perverse
      • Re: DES doubts. why we use 56 bit key when ony 48 bits are used?, Anon E. Maus
• Non-computer randomization, snaga
  • Re: Non-computer randomization, Paul Rubin
    • Re: Non-computer randomization, snaga
      • Re: Non-computer randomization, Unruh
      • Re: Non-computer randomization, snaga
      • Re: Non-computer randomization, Doug
      • Re: Non-computer randomization, snaga
      • Re: Non-computer randomization, Paul Rubin
      • Re: Non-computer randomization, David Wagner
      • Re: Non-computer randomization, Doug
      • Re: Non-computer randomization, Paul Rubin
      • Re: Non-computer randomization, Mike Amling
  • Message not available
    • Re: Non-computer randomization, snaga
• Re: SHA Question, Ichinin
  • Re: SHA Question, Tom St Denis
  • <Possible follow-ups>
  • Re: SHA Question, Neo
    • Re: SHA Question, Luc The Perverse
• Re: Basic tools of encryption: Transposition and substitution?, Doug
  • Re: Basic tools of encryption: Transposition and substitution?, Paul Rubin
    • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Joseph Ashwood
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Joseph Ashwood
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, David Wagner
      • Re: Basic tools of encryption: Transposition and substitution?, Paul Rubin
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
  • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
    • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
      • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
      • Re: Basic tools of encryption: Transposition and substitution?, Doug
      • Re: Basic tools of encryption: Transposition and substitution?, Phil Carmody
      • Re: Basic tools of encryption: Transposition and substitution?, Unruh
      • Re: Basic tools of encryption: Transposition and substitution?, Peter Fairbrother
  • <Possible follow-ups>
  • Re: Basic tools of encryption: Transposition and substitution?, Douglas A. Gwyn
• Re: Password length and bit number of encryption algorithm?, Joseph Ashwood
• Re: Why include this in your reply?, Joseph Ashwood
  • Re: Why include this in your reply?, Gabriel Lear

• Security
• UNIX
• Linux
• Coding
• Usenet

• News
• Mailing-Lists
• Newsgroups
• Service
• About
• Privacy
• Search
• Imprint

www.derkeiler.com  > Newsgroups  > sci.crypt  > 2006-01