On Fri, May 25, 2012 at 2:56 PM, Alan Malloy <a...@malloys.org> wrote: > This may be good advice in some cases (eg when all network access to > your server is "trusted"), but on a lot of production servers it > strikes me as very dangerous to apply this suggestion carelessly.
I was assuming that network access is pretty locked down on production servers. For example, the port on which we listen is only open on an internal IP and therefore only within a small, tightly controlled subnet when we have VPN active. There's no external IP access open. > This way the only people who can connect remotely are those who have > permission to get a local application (usually sshd) to forward the > traffic to the localhost interface on their behalf. I agree that's a nice, secure alternative. -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
