Hey,
I have a script and I want to allow an administrator log on to it. Once
logged in they can change things... etc. Basically stuff I don't want other
people to be able to do. I have decided that cookies is the best way to go.
I've been looking and looking on the internet for a way to add a "
> many ways to solve the problem. Amongst the real issues that
> the person will ultimately need to work out is whether it is
> really SANE to be writing temp files to begin with I mean
Yes! That is the other thing. If you write a script that writes temp
files you should consider it LOCAL ON
On Wednesday, Sep 17, 2003, at 18:02 US/Pacific, Dan Anderson wrote:
[..]
It is possible to use .htaccess files, apache config directives, and
burying 777 directories in 700 directories to add to the security of
having a 777 directory.
dan,
my complements! on the XML.document - and yes, there ar
> less acceptable on more and more web-sites. Prudence
> generally dictates 755 where other members of your group
> and the rest of the world can read and execute.
It is possible to use .htaccess files, apache config directives, and
burying 777 directories in 700 directories to add to the securi
On Wednesday, Sep 17, 2003, at 14:15 US/Pacific, John Park wrote:
[..]
Although I don't understand why I can't write to the same directory
my CGI scripts are located in. I've done this before on Free Webhosts
like tripod and netfirms.
[..]
while we are all deeply and emotionally committed
to our
On Wednesday, Sep 17, 2003, at 18:50 US/Pacific, ram Osuri wrote:
I agree with your assesment .. to solve this problem you might want to
do a
chmod 777 newfile.txt and then run the program it will work then
Actually there are two problems with this.
a. there is no reason to set the execute bits
Kit-Wing Li wrote:
>
> Does anybody know of a quick method in perl to turn a date string into its
> equivalent in seconds, include milliseconds if possible? Ex: 20030910
> 13:50:25.6 to 1063202644. Thanks much!
The Date::Manip module will do it for you easily, as long as you're
not worried abou
On Wednesday, September 17, 2003, at 03:56 PM, drieux wrote:
Remember that most web servers are running as the
web-server uid - www or apache - and so can only 'write'
where that uid has 'write permission'. It can of course
read/execute anything that is 'world readable/executable'
but as a genera
On Wednesday, Sep 17, 2003, at 11:59 US/Pacific, John Park wrote:
[..]
This is what my script looks like:
#!/usr/bin/perl
use CGI;
...
...
open(FILE,">newfile.txt") || die("newfile.txt: $!"); #script stops
here due to permissions
[..]
that is the correct syntax - although you might
not want to '
John,
I may be a little old fashioned, however, the code below seems to work
OK.
>open(INFILE, "@info = ;
>close(INFILE);
Sincerely in Christ,
Mark-Nathaniel Weisman
President / Owner
Outland Domain Group Consulting
Anchorage / Washington DC / Bellevue
[EMAIL PROTECTED]
-Original Message
Hi everyone,
I have a script where I am trying to write information to a file but
could not do so.
This is what my script looks like:
#!/usr/bin/perl
use CGI;
...
...
open(FILE,">newfile.txt") || die("newfile.txt: $!"); #script stops here
due to permissions
I can open files, and output its conte
Zedgar,
You are chasing the yourself into circles. Security is dictated by
circumstances and resources available. In our case, we had plenty of
both and developed for our needs the "best" solution. Insofar as the
storing of the password for the login that is used to get the password,
we too
essential quint wrote:
Awhile back I downloaded a script that was "protected" before purchase.
When I opened it to look at the code the script was in binary format,
not perl's pre-interpreted language, so I think they must have captured
it at compile time. Can anyone tell me how this is done?
On Wednesday, Sep 17, 2003, at 08:00 US/Pacific, Dan Anderson wrote:
The book I am reading describes exactly what you are talking about --
compiling a script into bytecode (like java). I have heard it
described
as experimental by some people though.
it is experimental, and it is perchance far mo
Hello,
Many thanks to R. Joseph Newton, Motherofperls, essential quint and Chuck Fox for
answering my questions, however it is still not what I was asking about. My previous
posts were long and maybe unclear so I'll try to get straight to the point this time,
adding more details at the bottom o
The book I am reading describes exactly what you are talking about --
compiling a script into bytecode (like java). I have heard it described
as experimental by some people though.
-Dan
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
there is also a program called Perl2Exe from
http://www.indigostar.com/perl2exe.htm
I have it, but haven't used it yet, seems simple.
some google-n will help in finding q/a's about it.
james
-Original Message-
From: Octavian Rasnita
To: essential quint; [EMAIL PROTECTED]
Sent: 9/17/2003 8
Are you sure it is a binary file?
But anyway, a perl program can be made to be an executable that doesn't need
perl to run it.
Download Active State Perl Developer Kit from www.activestate.com for this.
The file is not compiled, but the perl interpreter is included in the
executable file with the p
Greets,
Awhile back I downloaded a script that was "protected" before purchase.
When I opened it to look at the code the script was in binary format, not
perl's pre-interpreted language, so I think they must have captured it at
compile time. Can anyone tell me how this is done? It seemed a n
19 matches
Mail list logo
