Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • 4
    For reference, D.W. posted a great starting point here. Commented Aug 6, 2012 at 15:41
  • 38
    A couple people that thought they knew enough got together and created an encryption scheme called WEP for wireless networks. You can crack WEP encryption in just a few minutes. A "roll your own" methodology was used. Read about it, I'm just reminding you of this (you probably already know). Commented Aug 7, 2012 at 1:55
  • 17
    @Everett - Was WEP "roll your own"? In hindsight, yes it was weak and flawed (attacks quickly found), but it was the product of a large consortium of industry representatives creating a standard. Many of the attacks focused on WEPs small keys (and hence small and repeated IVs) (partially because strong encryption was illegal in the US for export at the time ). (I guess the industry "rolled their own" then and did it wrong again with WPA, and the WPS part of WPA2). Commented Aug 7, 2012 at 5:04
  • 3
    @Ramhound I'm aware, I'm just asking the question for the sake of having a go-to answer. It'd be great if you could offer a second answer to compete with dr jimbob's. Commented Aug 7, 2012 at 12:32
  • 3
    That's not a security scheme, that's a system design. A security scheme is mechanism or set of mechanisms aimed at solving a single security problem, e.g. a hashing scheme, a symmetric crypto scheme. You choose which schemes to use in your system design, but you should never invent your own security schemes. Commented Aug 8, 2012 at 5:46