NT Servers - ASPUpload

[Brangwyn]

While I agree that more notice should be given before making these changes, I think that disabling the "Most Risky Features" was done in the best interest of our clients and for the stability and security of our shared servers.

Fully agree Carly, and I commend Dave for being proactive. I think though a few of the others were disabled, for instance my customer noticed that .Save was giving the error message, that indicates to me that DisableSave reg key had been inserted just going by the documentation, thats not list as a "Most Risky" just listed as "Potentially Dangerous"

[Carly]

Yeh, I think most of the things in the list were disabled, but since has been re-enabled (except for the "Most Risky"). Is the Save feature still not working?

[Brangwyn]

Is the Save feature still not working?

Couldn't say for sure, been fixing everyones scripts by changing to the Dundas uploader instead

[bigdave]

OK, What I have done, these are what's been restriced and WHY...

DisableACL so permissions can not be changed to get around quotas

DisableDirectoryListing this allowed anyone to browse anywhere, according to the documentation it went like this "Directory Listing. This feature allows users to browser around the entire web server's hard drive and download any files."

DisableLogonUser Disables user impersonation functionality.

DisableRegisterServer Disables ActiveX registration functionality.

That's it!

Had anyone found out that you could register ActiveX components whew! Makes you wonder which is worse not being able to upload some files or having the webserver compromised then wating for us to reinstall it.

[pablo]

OK, this sounds fair. That means we can still be saving and delete files in the future using aspupload? It seams to be working ok now.

Brangwyn says:Couldn't say for sure, been fixing everyones scripts by changing to the Dundas uploader instead.
Could you give me some information on why dundas is better, and how the syntax is different from aspupload?

[Brangwyn]

It's not neccesarily better, they both do effectively the same thing and the upload syntax is basically the same. Most upload com objects are all based on the same original vb class someone wrote ages ago anyway.

The dundas website has the documentation for their com http://mfc.dundas.com/products/onlin...ods/dunsam.htm