Results for "Author: mike stevenson"
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)
My purpose for this was educational. I was trying to learn the Scripting.FileSystemObjects which were not documented well at the time. You can use it for educational purposes, or to test the security and see how well your server's NT user permissions are locked down (for instance, if your anonymous user can browse and download files from your WinNt directory (which is usually the case!), your permissions are probably not quite up to snuff)