security - Pitfalls of cryptographic code -

I am modifying the current security code, the specification is very clear, the example code, but I am not a cryptographic expert. In fact, a disclaimer in the example code is saying, in fact, "do not use this code literally."

I am modifying the code (which is believed to be fully facilitated) by auditing the code. This small gem is used to generate the challenge:

  RandomSeed random uint16; ... uint16 GetRandomValue (zero) {random random ++; / * This is not a good example of very random generation: o) * /}  

Of course, the first thing I did immediately was it passed near the office so that we all get laugh Could.

The programmer who produced this code knew that it was not a good algorithm (as indicated by the comment), but I do not think they understand the security effect. They did not even bother to call it in the main loop, so at least the free running counter would be - still not ideal, but the world beyond it

However, I know that the code I am producing is

• The most common security problems are specific to cryptography, why do I have to understand?
• What are some good resources that I should know beyond common mistakes, I will get the right knowledge about it?

- Adam

Crypto and help you understand the code To have an excellent book. It depends on a lot of basics, like how block ciphers work, and why choosing poor cipher mode will make your code unusable, even if you are using the most implemented version of the AES.

Trying to design your own algorithm or protocol - never do it.

This code is not being reviewed, preferably by publishing it online.

Not using a well-established library and trying to write it yourself.

Crabuto as a panacea - encrypting the data does not secure it safely

key management