Security

[Lox]

Hello,

I am looking at beanstalkd to manage my SMS server queues for outgoing
and incoming SMS. I will manage those using a PHP daemon.

I have a security concern in the fact that any program on the server
can connect to it and add/retrieve/delete jobs from my queues.

I mean my current way of handling this is using mysql which is
protected with credential. An other way I looked to is using plain
text files that can be protected by file system permissions.

What security menanism mya I use to be sure that only my PHP Daemon
can access beanstalkd queues ?

Regards.

[Chad Kouse]

I think the main way of securing access to beanstalkd is to use
something like iptables to only allow access to the beanstalkd port
from specific ip addresses on your network.

--chad

> --
> You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
> To post to this group, send email to beansta...@googlegroups.com.
> To unsubscribe from this group, send email to beanstalk-tal...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
>

[Linan Wang]

we use it through ssh tunnel:
.. setup beanstalkd only listens to 127.0.0.1 port
.. setup a ssh tunnel from the caller's machine to beanstalkd server
.. from the perspective of caller's machine, it talks to a local port,
from beanstalkd's perspective, it also talks to socket originated from
local machine. the two are bridged through ssh tunnel.
we use this approach on lots of services, mysql, redis, neo4j... for a
long time.

--
Best wishes,

Linan Wang
Architect, Programmer, PhD

[Ahmad Altwaijiry]

Hi

You could send some special key (password) with the data to the workers, if the worker found the password correct it should process the job



{ Requester (data+MD5key) } ---> beanstalk ----> {worker get data + get MD5Key}


BTW: I'm working in something similar to your SMS work (using also PHP), if you are interested we can work together and share our work.


Thanks