-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Read-only mode #3
Comments
First thing I thought of when looking at this. I would go a step further and make the read-only mode the default. Considering that this is going to be used in a pentester context, it seems reasonable to assume that at some point someone might find a path traversal issue or similar exploit and in that case you don't want people to have upload capabilities when they might not even be using them. Personally I would feel much more comfortable with a default read only that I can quickly kill, add a flag and restart as a read/write for my work. |
Will look into this for next major release. Thanks for your input! |
I would like to see this as well. Temp work around I am using is to comment out upload functions in "/usr/local/lib/python3.6/dist-packages/updog/templates/home.html" |
is there a way to run this like SimpleHTTPServer, basically open a port and report any HTTP calls, but not share any directories? |
I think that might be a job for netcat. Maybe you can tell me more about your use case? |
would be awesome a --no-upload , waiting for next release, anyway it's a fantastic tool |
This one can do it: https://github.com/patrickhener/goshs |
Hi! As name suggests, I think it would be nice to have a
--read-only
/--no-upload
/... switch that disables the upload functionality. What do you think?The text was updated successfully, but these errors were encountered: