> I'm also of the opinion that security isn't secrecy. If there is a security concern with node itself, > then it's probably best for the whole community to know
To quote isaacs re: a similar security concern<http://blog.nodejs.org/2012/05/07/http-server-security-vulnerability-please-upgrade-to-0-6-17/> : > A few weeks ago, Matthew Daley found a security vulnerability in Node's HTTP implementation, > and thankfully did the responsible thing and reported it to us via email. > The innocuous commit message does not give away the security implications, > precisely because we wanted to get a fix out before making a big deal about it. > I'm extremely grateful that Matthew took the time to report the problem > ... in such a way that we had a reasonable amount of time to fix the issue before making it public. -- peter -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
