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

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Continued discussion from Gemini DNN-7134Continued discussion from Gemini DNN-7134
Previous
 
Next
New Post
3/16/2008 5:11 AM
 

One more annotation: Due the fact that FTP in general is not a secure protocol, WebDAV is preferable and AFAIK used by most hosting control panels. On a shared portal,granting FTP access is not advisable, for uploads shall only be possible into the portal directory, which is easily accessible via Admin File Manager in DotNetNuke.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/17/2008 3:10 AM
 

What is the "portal directory"? Would that be the equivalent of ~dnn / portals / ( portal # here ) ? 
Access from the File Manager is NOT the same as FTP or WebDAV access. The File Manager will keep people from accessing the 'skins' and 'containers' folers withing the portal, but that is about all it will do.
Every portal gets something along the lines of "portals/0", "portals/1", etc... ... if there is FTP access to a portal root (portal 0,1,2,3,etc), there will be a folder called 'skins' and another called 'containers' which the FTP user would have write priveledges for, since those folders are sub-folders of the portal. If the user then creates a folder, within the 'skins' or 'containers' folders that includes a malicious script, that content 'could' be used as a skin regardless of host settings for uploads.

So, maybe skins need to be moved from the file-system to the database. That would give DNN absolute control over which users can upload skins, no?

 
New Post
3/17/2008 5:19 AM
 

yes, portal directory is ~dnn / portals /[portalID].

AFAIK both, Skins and Containers folder show up after a recursive sync, though this may change in the future, but the new installer in DNN5 will handle Skin packages as will and provide install and uninstall.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/17/2008 7:25 AM
 

@abecedarian

The admin can still upload an aspx with which you have almost free access, so moving the skin does not make a lot of difference.
FTP is the problem here, not DNN IMO

 
New Post
3/17/2008 8:33 AM
 

If your allowing ftp then your opening a security issue. Regardless of the type of site its a security issue. The only file access my admin's get is limited folder access to a select non-important folders. All controlled via DNN's file manager. I had way to many issues with people altering my config files or adding non-DNN pages without telling me. Now with DNN 5.0 at some point the admin menu will be broken apart, so you can control who has what access. Might help with the skin security piece, cause you could give portal admins rights to add pages etc, but no access to upload skins. This should make skin security a decision of the Host. Once the Host has control over skin uploads then its even less of a security issue, cause the host can then force admins to contact them for skin upload. Most admins I have tend to be barely smart enough to manage a few pages on their sites, moreless know how to scan a html file for possible malicous code. If and only if I could block the skin upload would I consider it. Yes I know its very insecure right now, but that doesn't mean we should make things even less secure. Now once the new security model is in place I say why not? I would like to see the parser warn the the user when it finds a html with scripts in the skin. There has been a bunch of late nights for me and if I have an admin wanting a skin I might miss the script when scanning through the html. If the parser would outline in red any scripts it found though it would save me time and trouble having to scan every html skin I want to upload. I already have to scan ascx files and its a pain as it is. On a typical week I upload around 20 different skins for my various admins. Right now 99% of them are all html based skins, so its not too bad.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Continued discussion from Gemini DNN-7134Continued discussion from Gemini DNN-7134


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