Re: Error: Permision deny.
This WebDNA talk-list message is from 2005
It keeps the original formatting.
numero = 62978
interpreted = N
texte = You can modify /etc/group as root. Bill On Sep 9, 2005, at 10:35 AM, Kenneth Grome wrote: > I forgot to mention that this problem is on the development server on > my desktop, not on a live server. > > One of the "pain in the ass" problems with webdna on MacOS X that's > running as a desktop development server is that webdna changes the db > files I create manually. It resets the permissions on these files so > the owner and group are both "www". This prevents me from manually > editing my db files (and it pisses me off because I always edit my > webdna db files manually during development). > > I figure that if I could add myself to the "www" group this would not > be a problem any more, because the "www" group can read and write to > these files, which means I can too -- after I'm in that group. Too > bad I don't know how to make myself a member of the "www" group ... :( > > Anyone know how I can do this? > > Sincerely, > Kenneth Grome > www.kengrome.com > > > > > > > > On Sep 9, 2005, at 21:20, William DeVaul wrote: > >> 660 is probably ideal for you. The general idea is the least amount >> of permissions needed to operate is the most secure you can be. >> >> Apache and WebDNA need to operate as the user www or httpd (depending >> on your distribution of Linux). Then, just to make things confusing, >> there is also a group called httpd or www. Your user needs to be a >> part of that group to r/w to those files. >> >> Here are some useful commands that one should read about and >> understand before using: >> >> ls -al (this will show the current directory with permissions and >> owners) >> chown (this will allow one to change the ownership) >> chmod (this will modify the permissions) >> chgrp (this will allow one to add a user to a group) >> >> Try man ls or man chown to read more about the commands before using >> them. I also recommend having a few good books on unix or linux. >> >> Bill >> >> >> On Sep 9, 2005, at 1:59 AM, Frank Nordberg wrote: >> >>> William DeVaul wrote: >>>> 666 is textbook insecure. >>> >>> Yes, but I think the general idea is to allow visitors to both >>> access and add to/modify the data through WebDNA so there's gotta be >>> a 6 there somewhere. Question is where does WebDNA fit in? owner? >>> group? world? >>> >>> Who is this group anyway? I thought that parameter wasn't really >>> relevant at all for a reguar public web site. >>> >>>> The bits are given for read(4)/write(2)/execute(1). >>> >>> Thanks, I'll try to remember it now. I think the reason why I have >>> to look it up every time is that the system seems to be the opposite >>> of what one would intuively expect: "read" (the least intrusive >>> action) for the lowest bit and "execute" (the riskiest one) for the >>> highest. >>> >>> >>> Frank Nordberg >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list
. >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
You can modify /etc/group as root. Bill On Sep 9, 2005, at 10:35 AM, Kenneth Grome wrote: > I forgot to mention that this problem is on the development server on > my desktop, not on a live server. > > One of the "pain in the ass" problems with webdna on MacOS X that's > running as a desktop development server is that webdna changes the db > files I create manually. It resets the permissions on these files so > the owner and group are both "www". This prevents me from manually > editing my db files (and it pisses me off because I always edit my > webdna db files manually during development). > > I figure that if I could add myself to the "www" group this would not > be a problem any more, because the "www" group can read and write to > these files, which means I can too -- after I'm in that group. Too > bad I don't know how to make myself a member of the "www" group ... :( > > Anyone know how I can do this? > > Sincerely, > Kenneth Grome > www.kengrome.com > > > > > > > > On Sep 9, 2005, at 21:20, William DeVaul wrote: > >> 660 is probably ideal for you. The general idea is the least amount >> of permissions needed to operate is the most secure you can be. >> >> Apache and WebDNA need to operate as the user www or httpd (depending >> on your distribution of Linux). Then, just to make things confusing, >> there is also a group called httpd or www. Your user needs to be a >> part of that group to r/w to those files. >> >> Here are some useful commands that one should read about and >> understand before using: >> >> ls -al (this will show the current directory with permissions and >> owners) >> chown (this will allow one to change the ownership) >> chmod (this will modify the permissions) >> chgrp (this will allow one to add a user to a group) >> >> Try man ls or man chown to read more about the commands before using >> them. I also recommend having a few good books on unix or linux. >> >> Bill >> >> >> On Sep 9, 2005, at 1:59 AM, Frank Nordberg wrote: >> >>> William DeVaul wrote: >>>> 666 is textbook insecure. >>> >>> Yes, but I think the general idea is to allow visitors to both >>> access and add to/modify the data through WebDNA so there's gotta be >>> a 6 there somewhere. Question is where does WebDNA fit in? owner? >>> group? world? >>> >>> Who is this group anyway? I thought that parameter wasn't really >>> relevant at all for a reguar public web site. >>> >>>> The bits are given for read(4)/write(2)/execute(1). >>> >>> Thanks, I'll try to remember it now. I think the reason why I have >>> to look it up every time is that the system seems to be the opposite >>> of what one would intuively expect: "read" (the least intrusive >>> action) for the lowest bit and "execute" (the riskiest one) for the >>> highest. >>> >>> >>> Frank Nordberg >> >> >> ------------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> To switch to the DIGEST mode, E-mail to >> >> Web Archive of this list is at: http://webdna.smithmicro.com/ >> >> > > > ------------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > To switch to the DIGEST mode, E-mail to > > Web Archive of this list is at: http://webdna.smithmicro.com/ > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
William DeVaul
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:
[WebDNA] Permission Settings (2009)
Web Catalog vs. ICAT (1997)
FYI: virus alert (1996)
Substitutes for [text]? (2000)
Re:Call For Entry: Third Annual Business on The Internet (BOTI) Awards (1999)
'does not contain' operator needed ... (1997)
OT - quiet on the list today - here's something (2004)
calculate age (2003)
Part 2 - [showif] if variable exists (1998)
Running _every_ page through WebCat-error.html (1997)
Help name our technology! I found it (1997)
Submitting ampersands in forms... (1998)
Bug in 4.5 - Needs to be fixed ASAP. (2002)
SiteBuilder and reportin on page hits (awstats) (2006)
[WebDNA] OT: undeliverable messages? (2009)
WebCat2 - Getting to the browser's username/password data (1997)
Browser frames and URLs in the Location field (2004)
WebStar5 and realm authentication (2003)
DBServer.exe (2003)
Forms Search Questions (1997)