Tag Info

New answers tagged

0

Are there any blazing "Oh, don't do that!" security flaws in the setup summarized above? The basic protocol you are proposing is: client identifies themselves, server checks the public key and verifies that they are a valid user, server encrypts a challenge using the public key, client decrypts to get the challenge back and returns it as proof of ...


0

Facebook ended up working on encrypting all data within their own private owned datacenters. Encrypting traffic provide an overhead... somewhat small in CPU performance if done right, but somewhat non-trivial in administrative time to figure out how to configure it smoothly. I'd recommend an option you haven't listed: SSL with connection pooling and Perfect ...


1

If the machines were on your own network (home, your company's datacenter, etc), simple IP-based restriction and/or putting the Redis-related machines on a separate VLAN should be enough. However, in case of a hosting provider, I recommend considering their networks as hostile and equivalent to the open Internet, in which case you should create your own ...


1

I'd say an explicit ACL in the Firewall permitting the traffic to and from the devices in question shuold be fine in this instance. It sounds like the information being exchanged is just user IDs? If this is the case and the information isn't necessarily sensitive, I don't see an issue with just ensuring the rules are in place to allow the traffic.



Top 50 recent answers are included