I am sure there are better ways to fix the security issue but I just dreamt of this just now, but this way the user doesn't know the name of the file they generated, and even if they did, they can't modify it or overwrite it because they have write only access, not modify access.
Or, always set the local timestamp to the remote one on uploads. You could even use windows search to query a particular event. So maybe give the user the option to make FileZilla try to set the remote timestamp to the local timestamp on upload, and if it fails, set the local timestamp to the one of the remote file. Then run a clean up script periodically to clean up the files. Then you could sort the files in the folder by date to see the last login or name to see the last time and which computer was used for a particular person logged in (or out) without having to even open the files. Here is an example of the changes to the file names createdĮcho Log In %Date% %TIME% %USERNAME% > \\servername\Logs\Computer\%COMPUTERNAME%+%USERNAME%+%DATE%+%TIME%+%RANDOM%.log It may not be the best fix, but better security could be achieved by giving users write only permission to the folder and using the %random% + %date% + %time% variable along with the %username% variable with the included %computername% variable to have different logs for each user for each login without them being able to list the contents of the file or be able to read any file that is generated. If someone can modify the log then that means they can edit the log, covering their tracks or even deleting all of the contents of the log. Although this method is very clever, it is important to discuss the security implifications of giving modify access to a share.
0 kommentar(er)
