Two things Rory
a. You only replied to me, instead of the list. You have to probably
click on reply to all in your mail client. I have included the lists
address for this reply, so that it will appear there.
Yeah sorry about that mailing you only thing. All the other lists I'm
PLEASE lets not start on the.
2. Because it reads out of order.
Why?
Top posting is bad.
III. Trimming is good, because it gets right to the point.
.top posting / bottom posting thing again.
-Ryan
--
No virus found in this outgoing message.
Checked by AVG
Because now it's out of order.
On 4/18/05, Ryan A [EMAIL PROTECTED] wrote:
PLEASE lets not start on the.
Only Joking.
2. Because it reads out of order.
Why?
Why?
Top posting is bad.
III. Trimming is good, because it gets right to the point.
.top posting
[snip]
The problem is that, in order for PHP to be able to access *.php
files, the files must in a directory with execute permission, and
files themselves must have read permission. This makes my files open
to reading by anyone, that is, anyone can look at my PHP source
code, which I do not
Kresimir Cosic wrote:
snip
Additional information (if that helps):
The website is located in directory home/vriho/public_html/
The mysql database is in home/vriho/db/mysql/ (not shared to other users)
The local socket file for mysql is at home/vriho/db/socket/
The parts of website that are hidden,
[snip]
I think you have to face facts. There is no way you're going to have
your code secure against other users so long as it has to be readable
by apache.
One _PARTIAL_ solution: If like most linux distros, you have a group
called users, which contains every human user on the system, but
6 matches
Mail list logo
