Repositories allows you to select any directory on the hard drive. This mean a portal administrator can point directly to the system directory or another portal. It really need to be restricted to directories in the portal.

Great news. But that means all of the portals will share the same repository? Are there any security problems between portals?

Also, do you recommend moving the repository outside the DotNetNuke directory? If the repository is under DotNetNuke then it will have read permissions by specifying the url. It seems that the Security Settings in File Manager do not apply if you bypass the application framework. (Even if you take read permissions off in IIS, you would have to do it for every parent portal which is a management nightmare.)

Maybe the Repository should be outside the portal. I tested and it handles multiple portals and separates the files just fine.

If the Repository is outside the portal, and even outside of the website files, it can be completely hidden from URL searches. Otherwise, you would have to remove Read properties from every web that is defined on the server (that could be hundreds of webs x hundreds of Repositories).

The only problem I see with putting the Repository outside the web is that it would not be included in the portal disk quota. But unless there is a way to automatically secure the folder from url browsing then it may be a better solution. (I think, one way or the other, url security has to be addressed in the core so private folders are truly private.)