Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104439
interpreted = N
texte = > With sandboxes, an admin has the ability to limit how a user can = interact with the rest of the server, particularly with = DOS,SHELL,Applescript, file paths et al. Has this sort of thing been = addressed with the fastCGI app that will most likely run in virtual host = situation? I don't know of anyone that will want to install an app in a = shared host enviro that will have the ability to fish around the entire = server. Knowing Jaz though, I'm guessing he has already thought of this = and addressed this.?? It seems like the only solution there is relative = paths only, as not all domains will have different user and groups. The fastCGI has shell access if the administrator provides shell access = to the user. On the contrary to the module version which needs the same = permissions as apache (to be able to interact with apache files), a CGI = runs with a single website permissions. This allows a webmaster to limit = the range of the application, which will not be allowed to interact with = other websites files. This greatly improves the security compared to the = module. > Contrary to what was said, there *are* many who still use commands.. = mostly because there are many who run SiteBuilder stores (which use = commands). Now, I personally think SiteBuilder is outdated and needs an = upgrade, particularly replacing the commands with contexts... However, = the fact remains that it is functional, people use it, people make money = with it, and yes, if done right, it can be secure. I know people use = commands because I have worked on some of those sites. If commands are = to be taken out of all the versions of WebDNA, those sites are dead in = the water without reworks and the SiteBuilder product becomes a dead = product without a rework. > (Fine with me if that is the case, but significant none the less to = quite a few, and something people may want a heads up on) this is why we will deliver a 6.2.1 module version. We are also working = on the SiteBuilder. > Also, I personally utilize a lot of the (extended) features of the = module based app.. globals and sandboxes in particular.. so I personally = don't want to see those go away in the module-based app. Because of the very core of the fastCGI, there will be no need for = globals or sandboxes: every single website owner will have full control = over his WebDNA fastCGI copy, license included. No need for a "part" = administration, or a central repository of functions. - chris=
Associated Messages, from the most recent to the oldest:
> With sandboxes, an admin has the ability to limit how a user can = interact with the rest of the server, particularly with = DOS,SHELL,Applescript, file paths et al. Has this sort of thing been = addressed with the fastCGI app that will most likely run in virtual host = situation? I don't know of anyone that will want to install an app in a = shared host enviro that will have the ability to fish around the entire = server. Knowing Jaz though, I'm guessing he has already thought of this = and addressed this.?? It seems like the only solution there is relative = paths only, as not all domains will have different user and groups. The fastCGI has shell access if the administrator provides shell access = to the user. On the contrary to the module version which needs the same = permissions as apache (to be able to interact with apache files), a CGI = runs with a single website permissions. This allows a webmaster to limit = the range of the application, which will not be allowed to interact with = other websites files. This greatly improves the security compared to the = module. > Contrary to what was said, there *are* many who still use commands.. = mostly because there are many who run SiteBuilder stores (which use = commands). Now, I personally think SiteBuilder is outdated and needs an = upgrade, particularly replacing the commands with contexts... However, = the fact remains that it is functional, people use it, people make money = with it, and yes, if done right, it can be secure. I know people use = commands because I have worked on some of those sites. If commands are = to be taken out of all the versions of WebDNA, those sites are dead in = the water without reworks and the SiteBuilder product becomes a dead = product without a rework. > (Fine with me if that is the case, but significant none the less to = quite a few, and something people may want a heads up on) this is why we will deliver a 6.2.1 module version. We are also working = on the SiteBuilder. > Also, I personally utilize a lot of the (extended) features of the = module based app.. globals and sandboxes in particular.. so I personally = don't want to see those go away in the module-based app. Because of the very core of the fastCGI, there will be no need for = globals or sandboxes: every single website owner will have full control = over his WebDNA fastCGI copy, license included. No need for a "part" = administration, or a central repository of functions. - chris=
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
in header include files? (1998)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
requiredfields (2002)
Secure server question (1997)
Removing [showif] makes a big difference in speed (1997)
unable to launch acgi in WebCat (1997)
How to search for fields with 10 or more characters? (2004)
problem with NT beta (1997)
Cookies (1999)
how to check for no value while using [URL] to prevent cr (1999)
WebCat2b13MacPlugIn - [include] (1997)
Nesting format tags (1997)
bug in [SendMail] (1997)
Upgrading old WebCat Database Files (1997)
Paths change questions ... (2004)
Using WC for Bulk Emailings (1997)
Timestamp/cart replacement was RE: Robust WebDNA Job Manager / (2006)
WebCat2 - many [carts] on one template page? (1997)
Multiple catalog databases and showcart (1997)
url value (2002)