You might find this incredibly stupid, but I just wanted to see if this could be done. I give you...(drumroll) the file that deletes itself:

delete.php

PHP Code:

<?php

echo 'Click <a href="delete.php?act=delete">here</a> to delete this file.'

if ($_GET['act'] == 'delete') {

    unlink('delete.php');
    
}

?>

How on earth might that be useful and why did you test that you may ask? You could create an install script that deletes itself when it is done making a configuration file and has checked that it was successful. I'm sure it's been done before and this is nothing earth-shattering, but there you go, it can be done and that's how you do it.

I've never tried to do that! I'll try now!

*Test one, I got a syntax error. The code should be:

PHP Code:

<?php

echo 'Click <a href="delete.php?act=delete">here</a> to delete this file.';

if ($_GET['act'] == 'delete') {

    unlink('delete.php');
    
}

?>

*Second test, file deleted itself!

I might use this in the future Thanks!

unlink(__FILE__);

Originally Posted by rogem002

*Test one, I got a syntax error. The code should be:

Oops...I don't know how I missed that semicolon. Sorry.

lol i always knew it was possible...

my only guess why this isnt used in production install scripts is that they might want the user to be able to ensure it all works and then make them make the consious decsion to delete.

but still a thought to remember...

Dan

Originally Posted by dansgalaxy

my only guess why this isnt used in production install scripts is that they might want the user to be able to ensure it all works and then make them make the consious decsion to delete.

I don't know if I'll actually use it for that exact reason, but it is nice to know that it can be done...

I know

haha thats quality, i will make it my life's purpose to use it somehow!

Originally Posted by Tropica

haha thats quality, i will make it my life's purpose to use it somehow!

*shakes head* what has the world come to? hehe

Oh, I know why this works if your interested.

When the file is being processed, it's running the the RAM (thus it just loads that file) so you can delete and mess with the file as you wish

Isnt that obvious? well i gues not to some people

Lol... Hence why huge programs lag your ram so much and you cant run a 25mb program on a 64k system

Originally Posted by dansgalaxy

Isnt that obvious? well i gues not to some people

Lol... Hence why huge programs lag your ram so much and you cant run a 25mb program on a 64k system

You would think so, but some people really are tech-t**ds. Anyway folkies, the above is why server's need a lot of RAM

If your script has access to delete files, so does any other script running on your website. Better make sure all your places to upload files or accept user input are protected from code injection.

i think in 99% of cases your scripts can execute unlink (and other stuff)

and you should always make sure ur upload folder has restricted rights or just dont allow upload of server executable files..

I tend to CHMOD to file to 0000 as well as not allowing certain file types. Another good move (security wise) is to have the file below the public html, so it cannot be easily executed.

only trouble with that is on systems you want the files to be avalible.

anyway i think we have completely gone off topic...

Dan