Proposal: removeDirectoryRecursive should not follow symlinks

Brandon Allbery allbery.b at gmail.com
Tue Jan 6 01:25:51 UTC 2015


On Mon, Jan 5, 2015 at 8:16 PM, Johan Tibell <johan.tibell at gmail.com> wrote:

> Let me make a wider comment about backwards compatibility.


The community has already messed up backward compatibility in far more
obvious and wide-reaching ways, for far worse reasons, many times. Suddenly
deciding to stand on principle, in a case where the current behavior is
*clearly* wrong and dangerous, seems "off" to me.

Of course, you're welcome to do it... I'll just have to make sure it's
understood that the decision was made to enshrine actively dangerous
behavior.

(I could make an argument for this being CVE-worthy. In fact, Austin Seipp
has already made most of it. Should a major security hole also be protected
and propagated by a sudden need to stand on backward compatibility
principles that have never been given much more than lip service in the
past?)

-- 
brandon s allbery kf8nh                               sine nomine associates
allbery.b at gmail.com                                  ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20150105/6c2c7c21/attachment.html>


More information about the Libraries mailing list