I asked advances in usability for cryptography/authentication and one of the commenters raises a good point: should this be in Security.SE?
Is there a good rule of thumb between the two? e.g. if it has actual algorithms in mind, should it stay here?
|
|
There are some questions which apply to both security.SE and crypto.SE, but will (should) receive different answers. For instance, if you ask about whether SHA-1 is appropriate for hashing passwords, the crypto.SE response will detail things about relevance of collisions and differentials and the Merkle-Damgard construction to the problem of hashing passwords; while the security.SE response will rather courteously but firmly insist on using bcrypt or PBKDF2. The rule of thumb, here, being that you should post to crypto.SE if you want to understand the internals, and to security.SE if you want to know what you should do now. |
|||
|
|
One gray area to all of this is cryptographic protocols. Here there can be little-to-no math, and it's more in the area of algorithm design. General discussion of cryptographic protocols may be hard to decide which site to post to. Cryptography.SE and Security.SE provide two different (but related) groups of listeners, and there's reasons to want input from each. |
|||
|
|
|
I think if it is about theory, math, algorithm design, etc it is good here. But if it is about practice, implementation, coding, risk management, usability, etc. it should be on Security.SE. See Frequently Asked Questions - IT Security - Stack Exchange for the scope of that site. Questions that are about usage of crypto applications may also be better suited for Superuser, if security/risk/etc isn't the focus. See e.g. How can I add my picture to my public key using GnuPG? - Crypto |
||||
|
