|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, March 27, 2013 3:22 PM
Points: 1,276,
Visits: 1,112
|
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Friday, April 26, 2013 5:29 PM
Points: 88,
Visits: 113
|
|
Nice article. An excellent book on the whole subject is "The Code Book" by Simon Singh ISBN: 0385495323. (I think he also presented a four-part miniseries on Channel4 UK on the subject). It is more of a history book than a techie book but does explain how all of the codes/ ciphers work including the Enigma (with diagrams!)
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Friday, May 17, 2013 1:59 AM
Points: 1,126,
Visits: 924
|
|
Great article. Nice to see a not so SQL-intensive article, but still showing how SQL can be used in this context. Good stuff
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, September 15, 2005 4:07 AM
Points: 2,
Visits: 1
|
|
Good Read. I don't know much on the subject and found it very interesting, think you've inspired me to find out abit more. Thanks, Chris.
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Monday, September 18, 2006 8:30 AM
Points: 4,
Visits: 1
|
|
The title of the article mentions the word "cryptology," yet the article discusses "cryptography." Similar yet distinctly different words.
I got confused, so I did some quick web searching. For those who desire further illucidation, this is what I found:
From Google:
The science of cryptology is the science of secure communications.
From Wikipedia:
The study of how to circumvent the use of cryptography is called cryptanalysis, or codebreaking. Cryptography and cryptanalysis are sometimes grouped together under the umbrella term cryptology, encompassing the entire subject.
Craig
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, March 27, 2013 3:22 PM
Points: 1,276,
Visits: 1,112
|
|
Yes, I forgot to add a title when I submitted it, so Cryptology was added to the title afterwards. Cryptology includes both Cryptography (securing messages) and Cryptanalysis (defeating cryptography/"codebreaking"). I think the title was probably chosen because it covers both Cryptography and Cryptanalysis, although I do focus more on the Cryptography side. Thanks!
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, March 27, 2013 3:22 PM
Points: 1,276,
Visits: 1,112
|
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, March 27, 2013 3:22 PM
Points: 1,276,
Visits: 1,112
|
|
A typo was discovered by Douglas Chrystall in the article. In the section on Asymmetric Encryption, I wrote: "You encrypt a message with your public key, and it can be decrypted by the receiver using your publicly available public key and their private key." I meant to write: "You encrypt a message with the receiver's public key, and it can be decrypted by the receiver using their private key." Thanks for the catch Douglas!
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, September 21, 2010 12:22 PM
Points: 171,
Visits: 18
|
|
Nice intro to a very complex field.  I particularly enjoyed your timeline image. Another further reading book I would add for those who love details is Making, Breaking CODES: An Introduction to Cryptology. ISBN 0-13-030369-0 http://vig.prenhall.com/catalog/academic/product/0,1144,0130303690,00.html Another good book like the The Code Book mention in an earlier post is: Crypto: How the Code Rebels Beat the Government Saving Privacy in the Digital Age. I find it goes into more details about the break through of Asymmetric Encryption how its relevant to the key distribution problem.
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Thursday, August 18, 2005 4:21 PM
Points: 75,
Visits: 1
|
|
If Douglas hadn't caught it, I would have mentioned your public/private error. In your image, (Figure 4) you have "Marian Rejewski beings work...1932" That would be "...begins work..." OK SSL (Secure Sockets Layer) doesn't involve SQL directly, but I'm a little surprised you didn't include that in your Asymmetric Key section, because it is a heavy user of this technology to encript client data that may eventually be stored in a SQL DB.
|
|
|
|