• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Edit disk security feature feedback request

O

OlegB

Guest
We have some requests with report about customers with problems with our new security schema. Sometimes customers need to fix our security manually. But this has one unsolved problem when the next time we are setting our security we will have rewritten customer settings… We understand this problem but want to know customers reaction to our suggestion before. We want to give customers ability add custom settings to our security, so at the next time we will take into account customer custom settings and we will have set correct security for our customera. But we don’t want add customers ability to override security settings strongly required by Plesk, usually this is allow permissions. So customers will have ability to add custom allow permissions, for example to override not required by Plesk our deny settings. We could make some UI to add/edit/import/export customer custom settings.
 
One thing that we see frequently is the need to have a single directory for uploaded content for CMS systems. (Images, etc) And we also frequently see .asp sites that need Access DB's placed just outside the webroot (same level as /httpdocs).

It is pretty important that the CMS systems stay working once the permissions are set on their content folders and especially that the Access directory permissions stay working.

We have no problems if you lock down Plesk specific files/folders, but we do need to be able to allow clients to set some permissions (I am willing to restrict that to just under the httpdocs folder, provided we can setup the access db folders above the httpdocs folders).

I know a lot of sites are moving to SQL Server/SQL Express, but it will be a couple of years before all the old Access based sites are gone, and I don't think we will ever get around the CMS upload issue.
 
Back
Top