Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Giving FTP access to 1 portal to a clientGiving FTP access to 1 portal to a client
Previous
 
Next
New Post
11/23/2009 2:14 PM
 

Just curious, I have a single installation of Dot Net Nuke on my servers and I currently have many different clients setup with their own portal IDs.

I'm wondering if I gave FTP access to one of my clients to his own portal ID if there are any files in his folders that he could potentially change or update that would bring down all the other portal IDs?  I'm particularly curious about the ASCX files but if there are any others I'd like to know.

 
New Post
11/23/2009 6:24 PM
 

FTP is always dangerous, uncontrolled upload may affect security of the installation - and, if not properly configured, of the whole server.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/23/2009 7:39 PM
 

thanks sebastian, but wouldnt that be true for FTP access for any website for any platform?  I'm talking more specifically about DNN and any files that may effect all the portals setup for that single installation of DNN. 

also, you mentioned that "If not properly configured" which would suggest that there is a proper configuration.... what would a good configuration be for FTP access to a single client to a single portal ID? 

 
New Post
11/24/2009 5:06 AM
 

as long as anyone is able to upload into DNN directory (besides app_data), code will be executed - this is a security risk, AFAIK you cannot control, which file types are uploaded (or renamed) on the server. Executed code may connect to the database and e.g. retrieve host password, i.e. it is a high risk. a better idea might be using a subdomain without execute permission and grant ftp upload for it.

To make ftp as secure as possible, use strong passwords, if possible use secure ftp, and make sure, user has access to selected directories only.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Giving FTP access to 1 portal to a clientGiving FTP access to 1 portal to a client


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out