You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You mentioned this as a solution on AWS S3. How could we ensure no search engines indexed the new folder or anyone was able to get the folder name another way? For example listing the directory.
I want to ensure no one had access to that new folder.
Thanks
The text was updated successfully, but these errors were encountered:
I can't seem to list and directories so that is good news and I added a robots.txt to prevent search indexing. I was just afraid there was another way a person could list the directories with another tool (excluding browsers). I will keep and eye on the logs during the next weeks to see if there is any activity in that folder. Thanks
I wouldn't rely on this approach for critical data, as brute force attack are hard to block.
It was meant as a client-side only protection for the client-side only blogging platform https://github.com/matteobrusa/Tumbless
Hi Matteo,
You mentioned this as a solution on AWS S3. How could we ensure no search engines indexed the new folder or anyone was able to get the folder name another way? For example listing the directory.
I want to ensure no one had access to that new folder.
Thanks
The text was updated successfully, but these errors were encountered: