According to @Maeher, we are not allowed to illustrate questions on crypto.stackexchange.com with executable code—such questions are permissible only on stackoverflow.com:
Squeamish Ossifrage: Are we forbidden from illustrating questions with executable code?
Maeher: @SqueamishOssifrage As I understand the scope of the site, yes.
Executable code that demonstrates a particular computation is sometimes the clearest way to phrase a computational question. Are we allowed to use it to illustrate questions about cryptographic algorithms, or must any questions with executable code be migrated to stackoverflow.com?
To be clear, I am not asking about questions on debugging software, about API usage, about higher-level security assessments of systems, about coding practices, about development tools, about program organization, etc.—I'm only asking about questions on cryptographic algorithms that are illustrated using executable code.
I am also not asking about any particular languages or libraries—I'm only asking whether the mere executability of code used for illustration is grounds for migrating or closing a question. Obviously languages like Unlambda are not useful for illustration, obviously it is not helpful to copy & paste an entire Java class library to point out a question about a single line, obviously this is not an OpenSSL help site (a deityforsaken place where questions go to meet horrible deaths)—and obviously questions illustrated by Unlambda or Java class library copypasta or questions about how to use OpenSSL could rightly be closed for being unclear or too broad or be migrated to stackoverflow.com.
I don't have any questions, but here are some answers I have written with code fragments that, it seems to me, could plausibly have appeared in questions too; these are principally about algorithms and not about API usage, development tools, program organization, or anything that seems to be the domain of stackoverflow.com:
- How many trials does it take to break HMAC-MD5?
- What is the “Random Oracle Model” and why is it controversial?
- Bob has an EC key pair. How can he receive a small integer in the least compute intensive way?
- SHA1 calculation for millions of strings having common prefix
- Uniformly distributed secure floating point numbers in [0,1)
- How to stop an attacker from repeating the same ciphertext?
Are these all forbidden from crypto.stackexchange.com?