Day 35 Testing and Mutations

What I did: Testing, Mutations and Health

Time spent: 79.783

Comments:

1) Check that sapphirepack.org is on HSTS preload list.

There were several ways but ended up settling on the hstspreload.com api which is called once per run. This ensures high level of security in the event that certificates fail.

2) Setup intermediary project management system YouTrack. I'm now having alot of issues and project components that need prioritization along with tracking. Within a week move to Gitlab self hosted on a secure internal network.
- Had to update brew
- brew cask not valid need to do brew install --cask
- Went with Docker since it's easier to throw away.
- Good news I can use docker for free since I'm making less than 10Million and/or have less than 250 employees!!! :)

• Continuing to setup container, massive command to start. Gonna see if I can start docker manually from the GUI in future so I don't have to memorize the 4 mounting points that have to be typed in absolutely path notation.
  • Poor computer I'm running docker on a 1.6 Ghz processor and Docker is only using 2 of the processors so it's timing out really badly right now. I can't restart for risk of hurting Youtrack.
  • Okay now able to add in the correct amount of processors and restart safely. YAY
  • Now porting over the tasks that I need.
  • Had to reset youtrack messed up permissions system.

3) Updated and removed old terms from 2SSL documentation.
- Harder than expected since alot of the documentation is still mixing the transport with the session with the data. All of these are separate and shouldn't be mixed up like this.
The transport has session built ontop which in turn has the data. This seems odd thing to do right now but will make alot of sense later on once you see how the data and data center level structuring and organization. Designed for sideways expansion instead of vertical growth

4) Reviewing OWASP Access token and refresh tokens to understand size requirements.

5) Have fuzzing test work. Currently 30 minutes into a 4 hour and a bit test. Manually set the timeout to 30 seconds. Using Stryker. What it does is flip logic, comparisons and functions around and seeing if the tests capture the error.