* I've fixed the instructions for the buildpack, since they were still using the legacy multi-buildpack addon ( )
#Stunnel github update#
* I requested memcachier update their docs to actually mention the existence of the buildpack ( )
which adds an stunnel daemon to every dyno. I only noticed after spotting this undocumented (and not very maintained) repository by Memcacher: > There are cases, however, where memcached is deployed in untrusted networks or where administrators would like to exercise a bit more control over the clients that are connecting. > Most deployments of memcached today exist within trusted networks where clients may freely connect to any server and the servers don't discriminate against them. > SASL (as described in RFC2222) is a standard for adding authentication mechanisms to protocols in a way that is protocol independent.
a cloudy ISP where the infrastructure is shared and you can't control it), you're going to want some kind of way to keep people from messing with your cache servers. > In order to use memcached in a hostile network (e.g. Worse, the memcached wiki pages for SASL state: > That even with SASL both the authentication and subsequent memcache traffic is sent over plaintext. Unfortunately for some reason neither the Memcachier, memcached, pylibmc nor python-binary-memcached docs mention one crucial fact: These both make use of the relatively new memcache binary protocol's SASL support: On Heroku there are two memcache add-ons:
0 kommentar(er)
