In my last few posts we talked a lot about substitution ciphers, but I hinted at transposition ciphers and promised to follow up with a post, so here it is.
Right now I am on my way to NCDevCon (Yay for free inflight internet!!).
If you are going to be at the conference this weekend, please do not hesitate to introduce yourself. One of the main reasons I go to conferences is to meet others.
On Saturday I will be speaking about Security in Adobe AIR applications. I will point out that this session is targeted toward experienced AIR developers (either Flex or HTML JS).
Anyway, I am looking forward to the conference. Last year's CFinNC was amazing, and I am positive that this year will be just as good.
In my first entry in this series I challenged you to do a little bit of cryptanalysis. This was, hopefully, a fun exercise to get you thinking about cryptography works and how it can be easily broken if it is not implemented properly.
Of course the examples I am using in this series are extremely simple and I hope that no one would consider using any of them in production code. The point of showing you these things is partly for fun and partly to get you thinking about how cryptanalysts work on cracking more complicated algorithms using crazy mathematics and powerful computers.
OK, first, let's get this out of the way. I am not a math guy. Not even close. I enjoyed "Math for the Liberal Arts Major" back in my community college days, but I never even completed college algebra (though it is on my list of things to go back and do). So I am about to explain some math, but there is a GOOD chance that I am going to butcher this. If so, please correct me.
Now with my disclaimer out of the way, I can say, "MATH IS COOL"! I really do enjoy the little bit of math that I know and while researching cryptography, I came across a little more. In Cryptography: A very short Introduction I was introduced to modular arithmetic.
Wow, 20+ days since my last post. :( It has been a busy few weeks getting ready for cf.Objective() 2010, and I have been slack in my blogging. But no more! Back to it.
Today I am going to continue my security series with a discussion of cryptography. This is a HUGE subject about which I am no expert, but I am learning and, as always, I feel the need to share this knowledge.
Recently I started graduate school and my first class required a research paper. I chose to do an "Introduction to Cryptography". I also turned it into a presentation for cf.Objective(). Now I am going to continue that and incorporate it into my security series. Repetition makes it stick, right?
So let's get started. And be sure to stick with me, cause somewhere in this post, I will have a contest.
Tomorrow night at the Twin Cities CFUG meeting, Kurt Wiersma and I will each be presenting one of our cf.Objective() presentations. I think we each have three presentations to give at cf.O(). This is your opportunity to see two of the six early (or at all if you are not going to the conference for some bizarre reason). :)
Would you like to win a seat at the "Building Secure CFML Applications" pre-conference training at cf.Objective()?
In case you don't know, Pete Freitag and I are offering a full-day training on writing secure applications with CFML at cf.Objective() 2010 in Minneapolis. The training will be on Wednesday the 21st of April, 2010 (which is the day before cf.O() starts).
We are going to give away one seat at this training.
In April I will be presenting a lot of things at cf.Objective(). Here is a short list:
Secure CFML trainingPete Freitag and I will be doing a full-day training on building secure CFML applications. We are going to be taking a fun, pragmatic approach to the topic.
We will start with an application that is full of vulnerabilities and we are going to hack that applications. We are actually going to deploy real attacks against the application to see how it works. We'll even use some hacker tools to automate attacks. By doing this we can better learn how to think like a hacker, which better enables us to code while thinking "how could this be exploited?".