Apt retweeted
study math.
not for grades.
not for exams.
but because math rewires how you think.
it teaches you precision in chaos.
how to see structure where others see noise.
how to break a giant, messy problem into clean, solvable chunks.
every great engineer, physicist, and builder; whether they admit it or not; stands on mathematical intuition.
math sharpens your reasoning.
it builds pattern recognition.
it gives you the language of reality.
if you can think mathematically,
you can think about anything.
Apt retweeted
Driver Reverse Engineering 101: how to approach reverse engineering of Windows WDM drivers.
eversinc33.com/posts/driver-…
Apt retweeted
HTTP Request Smuggling Lab Walkthrough: Confirming a CL.TE vulnerability via differential responses.
How to identify CLTE Vulnerabilities:
1. Send request to repeater
2. Downgrade protocol to HTTP/1.1
3. Disable "Update Content-Length"
4. Set Content-Length to 6
5. Add "Transfer-Encoding: chunked" heading
6. Send a chunk with an invalid chunk size
If the backend times out, this indicates a potential CLTE vulnerability.
Confirm the vulnerability with differential responses:
7. Create and send the attack request:
- Replace previous chunk with a terminating chunk.
- Add a smuggled request after the chunked body.
- Append X-ignore: X (without a newline) and send.
8. Send a normal request to repeater, downgrade to HTTP/1.1 and send immediately after the attack request.
If the response to the normal request is 404 instead of 200, the backend was poisoned! 🤮 Well done!
To learn more about HTTP Request Smuggling and take on this lab yourself, head over the the Web Security Academy now portswigger.net/web-security…
#requestsmuggling #pentesting #bugbounty #hacking #cybersecurity
Apt retweeted
you can read the full report here docsend.com/view/s/rmdi832mp…
Apt retweeted
Windows audit policies, some common events they enable, and the volume of events they produce.
#ThreatHunting #DFIR #Cybersecurity
Apt retweeted
GitHub - b30wulf/Malware-collection: 🔬Collection of malware, ransomware, RATs, botnets, stealers, etc. github.com/b30wulf/Malware-c…
Apt retweeted
Load Balancer vs Reverse Proxy — What's the Difference?
Modern applications and websites handle large amounts of traffic. Two of the main instruments to ensure the smooth operation of large-scale systems are load balancers and reverse proxies.
However, they approach traffic management in slightly different ways:
Load balancers are concerned with routing client requests across multiple servers to distribute load and prevent bottlenecks. This helps maximize throughput, reduce response time, and optimize resource use.
Load balancer in action:
1) Client requests are sent to the load balancer instead of directly to the server(s) hosting the application.
2) A server is chosen from the load balancer's list using a predetermined algorithm.
3) The request is forwarded to the selected server.
4) The server processes the requests and sends the response back to the load balancer.
5) The load balancer forwards the response to the client.
A reverse proxy is a server that sits between external clients and internal applications. While reverse proxies can distribute load as a load balancer would, they provide advanced features like SSL termination, caching, and security. Reverse proxies are more concerned with limiting and safeguarding server access.
Whilst load balancers and reverse proxies possess distinct functionalities, in practice the lines can blur, as many tools act as both a load balancer and reverse proxy. For example, tools like Nginx can perform both roles depending on their configuration.
~~
Thanks to our partner Depot who keeps our content free to the community.
Are long build times slowing down you or your team? Depot Cache saves so much time by making your builds up to 20x faster! It's super simple as well.
Depot is free to try. Our link will give you a month for free.
Check it out: lucode.co/depot-cache-z7tt
Apt retweeted
Complete free Splunk Course
Watch here: youtube.com/@digitalearn_off…
Don't forget to subscribe ❤
Apt retweeted
How Relational Databases Work. This post talks about how indexes and transactions work on the inside of relational databases. architecturenotes.co/things-…
Apt retweeted
𝗚𝗶𝘁 𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗲𝘀
When managing code in software development, choosing the right branching strategy can significantly impact collaboration, integration, and deployment.
Here are the main Git branching strategies:
𝟭. 𝗙𝗲𝗮𝘁𝘂𝗿𝗲 𝗯𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴
It involves creating a new branch for each feature or bug fix. Developers work on these branches independently, merging them into the main codebase (usually the main or develop branch) once the work is completed and reviewed.
It is best suited for teams that require strict code reviews and where features are developed independently.
𝟮. 𝗚𝗶𝘁𝗳𝗹𝗼𝘄
It is a branching model that defines a strict workflow for managing releases. To organize work, it introduces the concept of develop, release, hotfix, and feature branches.
It is best to use it with large projects with scheduled release cycles.
𝟯. 𝗚𝗶𝘁𝗟𝗮𝗯 𝗙𝗹𝗼𝘄
It combines ideas from Feature Branching and Gitflow but simplifies the process. It emphasizes deployment and integrates with issue tracking and continuous deployment. This strategy includes a main branch representing a production-ready code and optional branches per environment (staging, production, etc.).
It is best to use it for teams using GitLab integrated tools and if we want to benefit from CD practices.
𝟰. 𝗚𝗶𝘁𝗛𝘂𝗯 𝗙𝗹𝗼𝘄
It is a lightweight, branch-based workflow that is simple and effective for continuous deployment. It focuses on keeping the main branch always in a deployable state. Feature branches are created from the main branch, and we use pull requests to review and merge changes into the main branch.
It is best suited for small teams or projects with continuous deployments.
𝟱. 𝗧𝗿𝘂𝗻𝗸-𝗕𝗮𝘀𝗲𝗱 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁
With this strategy, all developers commit their changes directly to the main branch (the "trunk"). Feature branches are short-lived or avoided altogether.
It is best suited for teams that practice continuous integration and delivery and for projects where rapid development is a priority.
If you're new to Git workflows, start with a simpler strategy like GitHub Flow and evolve as your team and project grow. For larger teams or more complex projects, consider more structured approaches like Gitflow or GitLab Flow.
👉 Also, regardless of the branching strategy, proper automated testing should be implemented to catch issues earlier and establish team agreements on commit messages, branch naming, and merge procedures.
#softwareengineering #programming #coding
Apt retweeted
PayPal is updating their ToS to let themselves give your data to merchants starting Nov & they're banking on people not knowing to opt out, SO to opt out before they start: go to Settings >Data & Privacy > Manage shared info >Personalized shopping, & toggle that shit off
Apt retweeted
Google dropped NotebookLM recently.
AI tool that can generate podcasts of two speakers talking about the contents from various sources like research papers, articles, and more.
Absolutely bonkers.
100% AI 🤯
10 examples (and how to try):
1. AI Podcast about OpenAI o1 drop
