<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Robert Wilkens wrote:
<blockquote cite="mid:004001c99822$087d4ff0$1977efd0$@com" type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">This
probably _<i>Doesn’t</i>_ give you the answer you were
looking for… But is an option for the development machine to work on
files in
the public_html directory of the users home dir, then access (for
development
purposes) the files as if they were in <a moz-do-not-send="true"
href="http://localhost/%7Eusername">http://localhost/~username</a>
work?</span></p>
</div>
</blockquote>
<br>
Yeah, that's where I've got them, but in order for apache to write
generated files, it still needs full perms. Turns out to be the same
whether they are in ~/public_html or /var/www<br>
<br>
<blockquote cite="mid:004001c99822$087d4ff0$1977efd0$@com" type="cite">
<div class="Section1">
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">I
mean, I think you can still do this with apache, but I haven’t
used it in forever.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);">Rob<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size: 11pt; font-family: "Calibri","sans-serif"; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>
<div
style="border-style: none none none solid; border-color: -moz-use-text-color -moz-use-text-color -moz-use-text-color blue; border-width: medium medium medium 1.5pt; padding: 0in 0in 0in 4pt;">
<div>
<div
style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">From:</span></b><span
style="font-size: 10pt; font-family: "Tahoma","sans-serif"; color: windowtext;">
<a class="moz-txt-link-abbreviated" href="mailto:lilug-bounces@lilug.org">lilug-bounces@lilug.org</a>
[<a class="moz-txt-link-freetext" href="mailto:lilug-bounces@lilug.org">mailto:lilug-bounces@lilug.org</a>] <b>On Behalf Of </b>Kenneth Downs<br>
<b>Sent:</b> Thursday, February 26, 2009 9:47 AM<br>
<b>To:</b> LILUG Mailing List<br>
<b>Subject:</b> [Lilug] Still stuck on file permissions<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I've complained about this before, but I'm still
hoping
somebody can tell me something I don't know.<br>
<br>
I'll skip the details and just say the situation is that a programmer
is
developing a web app, but the web app also does code generation, so the
programmer (a regular linux user) must have full control over the
files, but
the apache process (www-data on ubuntu) must also have full control.<br>
<br>
This is only on a dev workstation, the situation can be avoided on a
production
server but not on a dev workstation.<br>
<br>
Here is the question: It seems to me that everything about Linux is set
up to
prevent this from happening without major interventions that a newer
Linux user
will not understand and a veteran will consider inappropriate. Am I
missing something? Is there a simple way to give two users full
control
over a body of files? Don't just say "groups" automatically,
see below:<br>
<br>
METHOD 1: <br>
<br>
1) Add the programmer's user account to the www-data group (veterans
may
object, newbies may stumble)<br>
2) Put perms to 6770 on the file tree<br>
3) Set ownership to <user>:www-data on the file tree<br>
<br>
This is what I am doing now. Believe it or not this is as simple as I
could figure it, but I'm shooting for simpler.<br>
<br>
METHOD 2:<br>
<br>
This gives the veterans fits, but I figured <i>on a dev workstation</i>
I would
just run apache as my account. This is <i>more invasive</i>, but <i>only
at a single point</i>. At this point the veterans jump in with
"never, never, never" but don't usually address the context of the
situation, so I don't know what to do with their advice. <br>
<br>
<br>
METHOD 3:<br>
<br>
Complex ACL's. There seems to be on-off support for more complex file
permissions in Linux, but I get the sense it is a red-headed
stepchild.
If there were a more powerful permissions system that understood the
idea of
giving two separate users the same permissions, I'd be very happy to
accept a <i>configurable
dependency</i>, but I don't get the idea that's out there.<br>
<br>
So I'm really hoping I missed something in the last 10 years on how
linux
controls file permission :(<br>
<br>
<br>
<br>
<br>
<br>
<br>
<o:p></o:p></p>
<pre>-- <o:p></o:p></pre>
<pre>Kenneth Downs<o:p></o:p></pre>
<pre>Secure Data Software<o:p></o:p></pre>
<pre><a moz-do-not-send="true" href="mailto:ken@secdat.com">ken@secdat.com</a> <a
moz-do-not-send="true" href="http://www.andromeda-project.org">www.andromeda-project.org</a> <a
moz-do-not-send="true" href="http://www.secdat.com">www.secdat.com</a><o:p></o:p></pre>
<pre>Office: 631-689-7200<o:p></o:p></pre>
<pre>Cell: 631-379-0010<o:p></o:p></pre>
<pre>Fax: 631-689-0527<o:p></o:p></pre>
</div>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Lilug mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lilug@lilug.org">Lilug@lilug.org</a>
<a class="moz-txt-link-freetext" href="http://lists.lilug.org/listinfo.cgi/lilug-lilug.org">http://lists.lilug.org/listinfo.cgi/lilug-lilug.org</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Kenneth Downs
Secure Data Software
<a class="moz-txt-link-abbreviated" href="mailto:ken@secdat.com">ken@secdat.com</a> <a class="moz-txt-link-abbreviated" href="http://www.andromeda-project.org">www.andromeda-project.org</a> <a class="moz-txt-link-abbreviated" href="http://www.secdat.com">www.secdat.com</a>
Office: 631-689-7200
Cell: 631-379-0010
Fax: 631-689-0527
</pre>
</body>
</html>