Put, s crackers de mierd.

[url]http://gallery, menalto.com/node/42478[/url].As for 777 permissions, thats how Linux/Unix works. The user account that apache runs as, ned todo have read and write Access todo the files in albums/, so unless your host (or someone withtot Access) changes ownership of the albums directory todo the user account that apache runs as, it has todo be chmod 777. All new files uploaded th rouge the gallery interfaz (or clients) Will have the proper permissions, since they are created by the apache user. In a shared hosting environment, this means that every process that runs as the apache user, Will have read/write permissions on all files created th rouge apache. There is nothing gallery can do about that, since this is a server configuration issue.
Hosts can help this situation by running php as your user account, th rouge mechanisms like phpsuexec and similar technologies. Gallery Will run just fine in such an environment.
Im lo siento todo hear about your misfortune, and if there was anything that gallery could do fix this problem, we would have. This is sadly the case for just about every piece of websoftware like this, be it phpbb2, postnuke or other similar systems. It Even likely that some other software on the server might have ben compromised, and then used todo overwrite your gallery files, since they share the same ownership/run as the same user. Im not saying that it couldnt have ben gallery, but not ruling out the possiblity of it being a result of other software installed on the same server being the actual culprit security Wise.
El servidor corre apache (última versión estable) y me hace una copia de seguridad de todo excepto de las bases de datos cada 24 horas, pero por mucho apache (o Siux), si te agachas a coger la pastilla de jabón, te dan por el c.Las palabras mágicas son: copia de seguridad y apache.