Re: Permission denied?
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55715
interpreted = N
texte = On Jan 26, 2004, at 2:39 PM, Kalin Mintchev wrote: > On Mon, 26 Jan 2004 dott@thedott.com wrote: > >> The "code" is very fundamental UNIX. File permissions will be one of >> the >> very first items covered in even the most basic of manuals. >> >> Sounds like you should check the owner and group (WWW, apache, etc) >> before >> making any file permission changes, making certain they are correct. >> But here is the code that will change the file perms for you. >> You will need to be logged in as root or SU. cd to the directory >> where the >> .db is located. >> type the following: >> chmod 664 thefileyouwanttochange > > these are bad permissions. this command sets your db files to be > readable > by everybody which means that if somebody types the url to you db > directly s/he will actual get the whole file rendered in the browser > window. use: > > chmod 660 *.db > > and if you want to actually edit the db files manually change the > group on > the files to the group you belong to... > 664 is not necessarily bad... there's more to it than that for someone entering a URL. If someone were to telnet into your server (or some other command line method), then, yes, they could read the file regardless of the user they sign in as. But coming in via HTTP, it is up to the HTTPd and the file extension mappings. As long as .db is mapped to WebDNA, and WebDNA is configured not to directly serve up .db files, then the permissions could be 777 and you'd still get an error if you entered the URL to the db file in your browser. The key here to Ross' problem is that the user that WebDNA is running as (generally "www") must have read and write privileges to the .db file. - brian -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.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:
On Jan 26, 2004, at 2:39 PM, Kalin Mintchev wrote: > On Mon, 26 Jan 2004 dott@thedott.com wrote: > >> The "code" is very fundamental UNIX. File permissions will be one of >> the >> very first items covered in even the most basic of manuals. >> >> Sounds like you should check the owner and group (WWW, apache, etc) >> before >> making any file permission changes, making certain they are correct. >> But here is the code that will change the file perms for you. >> You will need to be logged in as root or SU. cd to the directory >> where the >> .db is located. >> type the following: >> chmod 664 thefileyouwanttochange > > these are bad permissions. this command sets your db files to be > readable > by everybody which means that if somebody types the url to you db > directly s/he will actual get the whole file rendered in the browser > window. use: > > chmod 660 *.db > > and if you want to actually edit the db files manually change the > group on > the files to the group you belong to... > 664 is not necessarily bad... there's more to it than that for someone entering a URL. If someone were to telnet into your server (or some other command line method), then, yes, they could read the file regardless of the user they sign in as. But coming in via HTTP, it is up to the HTTPd and the file extension mappings. As long as .db is mapped to WebDNA, and WebDNA is configured not to directly serve up .db files, then the permissions could be 777 and you'd still get an error if you entered the URL to the db file in your browser. The key here to Ross' problem is that the user that WebDNA is running as (generally "www") must have read and write privileges to the .db file. - brian -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.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/
Brian Fries
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:
[OT] (waaaay OT) (2004)
Weird error message (2002)
Formating found categories (1997)
Setting up WebCatalog with Retail Pro data (1996)
WebCat2b13MacPlugIn - [showif][search][/showif] (1997)
Emailer port change (1997)
EditPlus 2 WebDNA cliptext (2002)
Trouble Searching (1999)
Practice runs ? (1997)
[showif] not working (2003)
Resume Catalog ? (1997)
Using Cookie for client specific info? (1997)
unable to launch acgi in WebCat (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
More on the email templates (1997)
[OT] Simple java help please (2004)
UN-WANTED character conversion (1999)
Pirated WebCat? NOT... (2003)
Not really WebCat (1997)
Sku numbers (1997)