> As I said: Magento Enterprise tar ball, supplied at considerable expense straight from Magento. Is this a download from the partner portal? I've asked suppor

> As I said: Magento Enterprise tar ball, supplied at considerable expense straight from Magento. Is this a download from the partner portal? I've asked support to check, but you can probably point out the source much more quickly than I can track it down. > Only someone working for Magento could claim 777 is ever not a hideously terrible idea to have in the webroot of a PHP application I did not make this claim. I stated that I wish it were not there. It's not necessary, as the kinds of environments in which 777 are necessary are a problem unto themselves. These instances are borne of legacy concerns which pre-date my arrival to Magento by 6 or 7 years. Pity they were not patched before now Have you ever filed a bug report for this issue? I can imagine you might say, "I shouldn't have to," (and I agree), but it's remarkable what even a single ticket can do. In general, it's unfortunate that Magento 1.x development and bug tracking are so... internal. In contrast to the visibility and interaction present at https://github.com/magento/magento2/issues https://github.com/magento/magento2/issues it's clear that everyone is better off. Of course, we have to consider how to have the same kind of open dialogue for Enterprise Edition, and we're working out how to do that. Would you care to participate in a private GitHub repo, or can you suggest some other medium? Really, neither you nor I should have to spend time writing about the 777 issue - an open dialogue would likely have led this to be fixed years ago, so we could spend time bemoaning & fixing other issues!