summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Randomly resolve incidentsRobby Zambito6 days
|
* Cleanup api implRobby Zambito6 days
|
* Add random incidentsRobby Zambito6 days
|
* Rename logChan to toLogParserRobby Zambito6 days
| | | | Better description
* Adding incident stuffRobby Zambito6 days
|
* Refactor status APIRobby Zambito6 days
| | | | This lets me easily continuously update the state of the status
* Implement subscribe status and contact form handlersRobby Zambito6 days
|
* Add standard API endpoint for logsRobby Zambito6 days
| | | | Keeping the old one for convenience
* Respond to subscribe with empty objectRobby Zambito6 days
|
* Remove logsRobby Zambito6 days
|
* Add valid responses for status endpointsRobby Zambito6 days
|
* Add CIRobby Zambito6 days
|
* Add copyright noticeRobby Zambito6 days
|
* Rename snorvik to taskflow everywhereRobby Zambito6 days
|
* Add API constants and initial overall status handlerRobby Zambito6 days
|
* Remove privacy policy in favor of termsRobby Zambito6 days
|
* Update press and privacy policy linksRobby Zambito6 days
|
* CareersRobby Zambito6 days
|
* Stub out status and contact API handlersRobby Zambito6 days
|
* Use single log length constRobby Zambito7 days
|
* Add dockerfileRobby Zambito7 days
|
* Properly send unauthorized response for loginRobby Zambito7 days
|
* Fix linksRobby Zambito7 days
|
* Added API DocsRobby Zambito7 days
| | | | | Prompt: Generate a simple API docs page for the current public API. Include the endpoints that are used in the previously defined pages.
* Move handlers to handlers fileRobby Zambito7 days
|
* Update social media linksRobby Zambito7 days
|
* Created status pageRobby Zambito7 days
| | | | | Prompt: Create a status page with live updating data that polls API endpoints for data
* Use /api/v1 for the API prefixRobby Zambito7 days
|
* Added contact pageRobby Zambito7 days
| | | | | Prompt: Create a contact page
* Remove blog from navbarRobby Zambito7 days
|
* Add blog pageRobby Zambito7 days
| | | | | Prompt: Add a blog page
* Added basic about pageRobby Zambito7 days
| | | | | Prompt: Make a basic about page
* Fix invisible buttonRobby Zambito7 days
|
* Add scoring utility functionRobby Zambito7 days
|
* Add exploitable log parsingRobby Zambito7 days
|
* CleanupRobby Zambito7 days
|
* Wrap auth requests in authRequest objectRobby Zambito7 days
| | | | Remove debug prints
* it works ??Robby Zambito7 days
|
* uhh did stuff to make logging better i thinkRobby Zambito7 days
|
* Allow any inputs in login formRobby Zambito8 days
|
* Log login attemptsRobby Zambito8 days
|
* go fmtRobby Zambito8 days
|
* Log access as jsonRobby Zambito8 days
| | | | Redact client IPs
* Added support for newlinesRobby Zambito8 days
| | | | | | logs added with newlines in the value will be added as seperate values in the log array Testing with \\n for inserting \n in the output, that works fine.
* Use log_length constantRobby Zambito8 days
| | | | Fix bug when appending at filled logs
* Add logs endpoint with dynamic valuesRobby Zambito9 days
|
* start endpoint handlersRobby Zambito10 days
|
* Link to login pageRobby Zambito11 days
|
* Create login pageRobby Zambito11 days
| | | | | | | This is where the exploit will happen. Prompt: Create a login page. The login form should make a POST request with the form body to an appropriate API endpoint.
* Replaced index with generated landingRobby Zambito11 days
| | | | | | | The generated index had a fake logged in interface. The generated landing page is more appropriate. We don't need a logged in page, because the entire exploit should work without needing to be logged in.