Comment #16 on issue 192 by [email protected]: Crash when sending
specially crafted packet
http://code.google.com/p/memcached/issues/detail?id=192
I am in firm defense of dormando on this one. If people would actually
contribute a good patch with tests, this likely could have been closed long
ago.
The reality is, this is only an issue for people stupid enough to have your
memcached listening on a public network. Otherwise, how is someone
malicious going to send that packet to my memcached? Secondly, it
segfaults. That can cause a DOS. If your infrastructure has memcached on a
public port AND also relies on it so much that your arch falls because
memcached is restarted, you have bigger issues in your arch and need to
rethink a lot of things.
And yes, he didn't create memcached. He has however been the only person
doing any real work on a daemon that powers thousands of web applications
world wide for several years now. The person that made it has moved on to
Google and the other people that were putting a lot of work into it are
doing their own noSQL memcached in the cloud kind of database thing.
So, kudos to Dormando for giving this bug all the attention it deserves.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "memcached" 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/groups/opt_out.
