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*
- 2Not that I agree or disagree, but "widely agreed" by whom? This is not a sentiment that I've actually heard expressed.Steven Evers– Steven Evers2012-11-24 10:22:08 +00:00Commented Nov 24, 2012 at 10:22
- Thanks for the quick response man! And it does make sense when I think about it, it's a trade-off between sharing something that would have already been found by skilled hackers and getting proper input from well-intentioned programmers. Clearly I hadn't though about it this way.. Thanks again!federicot– federicot2012-11-24 10:25:46 +00:00Commented Nov 24, 2012 at 10:25
- @SnOrfus: see Linus' Law and Kerckhoffs's principle. Admittedly, "widely agreed" may be a bit of an exaggeration, but I'd wager that the majority of experienced programmers would agree.Michael Borgwardt– Michael Borgwardt2012-11-24 10:36:42 +00:00Commented Nov 24, 2012 at 10:36
- 1@MichaelBorgwardt, I'd wager that the majority of experienced programmers would disagree. So-called "more eyeballs = less vulnerable" isn't based on actual proper research. Heartbleed is not the first and will not be the last. Also see blog.codinghorror.com/given-enough-money-all-bugs-are-shallowPacerier– Pacerier2015-06-05 09:12:22 +00:00Commented Jun 5, 2015 at 9:12
- 1@Pacerier: I'll take you up on that wager anytime. Note that the statement is that open source increases security, not that it results in perfect security. You can cite examples for bugs in OSS until the cows come home and it proves absolutely nothing to the contrary. There actually is proper research: archive.wired.com/software/coolapps/news/2004/12/66022 - yes, it's over 10 years old, but until you can find something concrete with contrary findings, it stands.Michael Borgwardt– Michael Borgwardt2015-06-07 20:31:53 +00:00Commented Jun 7, 2015 at 20:31
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you