Recently a friend had an issue with DDoS attacks on his gaming server. The first step to handling problems was collecting data because what gets measured gets managed.
I used Sysmon as an ingress filter by writing a config file to log TCP and UDP connections on some selected ports.
After a disruptive attack that lasted several hours, we checked the logs and found out the origin of the attack and its type. It was a UDP flood attack from multiple sources.
We made many assumptions for possible solutions and a testing plan to handle this situation. We came up with different solutions a test plans, but that is a story for another day.
There are better tools and methodologies such as Tcpdump and Wireshark. However, Sysmon is a great tool to tailor your logs to achieve different tasks.
I own multiple steam accounts, and switching between daily is a chore.
There have been many solutions to this. Some suggest using a sandbox, others suggest creating multiple windows accounts, and some developed a program for this task.
Everyone solution has its pros and cons. Albeit, this task is so easy to tackle with a CI/CD mindset, and this is my solution to this problem:
First, sign in and turn on the remember password (repeat for all accounts), then run the script to switch between your accounts seamlessly.
Simplicity wins. Enjoy!
Help Your Future Self
Recently, I was looking at my commit messages. I wasn’t able to comprehend some of them. I thought to myself, “there must be a better way.”
Lucky, there is a research paper that addresses this question. “What Makes a Good Commit Message?”
It is the consolidation of:
- 46 research papers
- 50 secondary sources
- 30 expert opinions
A good message must answer these two questions:
- Why was the change required?
- What was changed?
Moreover, the researchers followed an empirical approach. They constructed a data set from popular open-source repositories and created a machine-learning algorithm to classify good messages based on these two criteria.
Check the results from the link below:
