Just tried to upgrade the RAM on my server with a shiny new 8GB stick....
Looks like it's DOA. Now I have to send it back to amazon and wait for a new one. My poor ESX server. Looks like another 4 days wait (at least).
So, when attempting to use git to manage my Mastodon instance......
I managed to pull the branch that had none of my custom changes, and a completely different docker-compose file.
I then proceeded to bring up my mastodon, screwing with all of my containers.
For whatever reason, it refused to revert container names and volumes, however much I tried.
After eventually switching to the correct branch, and judicious use of 'docker-compose down', everything came back up!
But no luck, as my reverse proxy couldn't see the server.
One nginx restart, and logs started flowing!
We're all back online now, but I blame @mike for giving me well written instructions that I dutifully ignored.
Today I created a test word document with a macro that tries to reverse connect out to a C2 server controlled by me. The idea was to use it to test our firewall's capability to inspect protocols on certain ports.
I was positive that this would fail, but provide us good data for designing alerts.
It did not fail. Full reverse shell with very little indication on our firewalls.
Guess what I'm doing tomorrow? 😓
Whitespashe is now running Mastodon 3.0.0rc2!
Friendly Neighbourhood Sysadmin.
This is a mastodon instance that allows users to share ideas and participate in discussions.
We have a hidden service frontend running at: https://whtspshcehqg4nj4wqyiopjcfxradop7ujflycxum7wkfivewqt36zyd.onion
Our code of conduct and extended information can be found after the 'Learn More' link below!