Andy Fingerhut writes: > It isn't just clojure.core/read executing code that can consume CPU > cycles that is the issue, it is clojure.core/read executing code that > can wreak havoc with your system and allow attackers to gain remote > control of it.
Are there specific known problems with binding *read-eval* to false? Relying on read-edn makes it difficult to write libraries that are backwards-compatible. -Phil -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
