Small width layout Medium width layout Maximum width layout Small text Medium text Large text
     Search
Downloads Downloads Directory Directory Forums Forums Forge Forge Blogs Blogs        Marketplace Marketplace Careers Program Careers
Community › Forums Register  |  

DotNetNuke Marketplace
  Ads  
r2i.ntegrated
 


  Sponsors  

Meet Our Sponsors

Red-Gate Software
MaximumASP
SourceGear - Tools for Developers
.: CounterSoft :.
telerik
ExactTarget email software solutions
 


DotNetNuke Forums
 
  Forum  General DotNetN...  Make it Hot! ( ...  Continued discussion from Gemini DNN-7134
Previous Previous
 
Next Next
New Post 3/16/2008 3:11 AM
User is offline Sebastian Leupold
15045 posts
www.deutschnetnuke.de
1st Ranked












Re: Continued discussion from Gemini DNN-7134 

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.


Sebastian Leupold

DeutschNetNuke dnnWerk - The DotNetNuke Experts German DotNetNuke User-Group

DotNetNuke Project UserDefinedTable
DotNetNuke Project Release Tracker
 
New Post 3/17/2008 1:10 AM
User is offline abecedarian
74 posts
10th Ranked


ARe: Continued discussion from Gemini DNN-7134 
Modified By abecedarian  on 3/17/2008 3:11:39 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 3:19 AM
User is offline Sebastian Leupold
15045 posts
www.deutschnetnuke.de
1st Ranked












Re: ARe: Continued discussion from Gemini DNN-7134 

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.


Sebastian Leupold

DeutschNetNuke dnnWerk - The DotNetNuke Experts German DotNetNuke User-Group

DotNetNuke Project UserDefinedTable
DotNetNuke Project Release Tracker
 
New Post 3/17/2008 5:25 AM
User is offline Timo Breumelhof
1733 posts
5th Ranked




Re: ARe: Continued discussion from Gemini DNN-7134 
Modified By Timo Breumelhof  on 3/17/2008 8:32:04 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


Timo Breumelhof -- www.searchdotnetnuke.com -- Extended DNN (forum) search
 
New Post 3/17/2008 6:33 AM
User is offline keeperofstars
252 posts
9th Ranked


Re: ARe: Continued discussion from Gemini DNN-7134 

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 Previous
 
Next Next
  Forum  General DotNetN...  Make it Hot! ( ...  Continued discussion from Gemini DNN-7134
 


Forum Policy

These Discussion Forums are dedicated to the discussion of the DotNetNuke Web Application Framework.

For the benefit of the community and to protect the integrity of the project, 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 DotNetNuke.
2. Discussion or promotion of DotNetNuke product releases under a different brand name are strictly prohibited.
3. No Flaming or Trolling.
4. No Profanity, Racism, or Prejudice.
5. Site Moderators have the final word on approving/removing a thread or post or comment.
6. English language posting only, please.

 


Active Modules, Inc.
Creators of Active Forums, the best forum module for DotNetNuke
www.activemodules.com
DNNCovered.com - Your Offshore Dotnetnuke Partner
Dnncovered.com is the only Dotnetnuke offshore outsourcing center specializes in DNN skinning and module development with lowest pricing and quality service. Our staff is dedicated to websites based on DNN and our graphic designers are creative and imaginative well enough to provide customers the complete set of skinning solutions and packages
www.dnncovered.com
PointClick.Net DNN Solutions
DotNetNuke Hosting Platform for Business and personal use.
PointClick.Net Hosted Solutions

DotNetNuke Corporation   Terms Of Use  Privacy Statement
DotNetNuke®, DNN®, and the DotNetNuke logo are trademarks of DotNetNuke Corporation
Hosted by MaximumASP