There were several places in the repository pattern that gave me pause, and whilst there was only a limited number of ExecuteCommand invocations wrapped in a helper function, that is not to say there isn't a way to ExecuteCommand or perform other attacks. The code is immature and not particularly well hardended, many error messages just spew out to Console and catch clauses are empty/non-logging and don't handle the error. I did a quick look through of the code on github and I would strongly advocate against exposing this server to the internet at this time even if it were situated behind a reverse proxy with an encrypted connection. Setting up a reverse proxy is a good way to access the server or container but I would recommend that nobody do this. Great effort, but your execution lands as wide of the mark as every other solution out there. I'll stick with the sucky broken system I have right now than a shiny new broken system that still sucks but also messes with my directory structure. Messes with the directory contents and formats. The 1990's web called asking for its UI back but I didn't pick up because we text these days. Paging through the library 30 books at a time rather than scrolling. Why do I have to be on-guard against what tracking and additional cruft is included in my own server?!?
Why do I need Twitter javascript and Twitter cookies included in my e-reader? No, just no. It simply sits there dumbly and doesn't let you register.Īnalytics (opt-out rather than opt-in) sent back to server with a pinky promise not to send any other data. How I set my passwords on my network is up to me.ĭoesn't let you know of this password format requirement in an older Chrome browser.
0 kommentar(er)
