Git Workflow Explained: From Working Directory to Remote Repository

·1 views

Git is a version control system that allows developers to track changes, manage project history, and revert to earlier states of their work. The workflow follows four main stages: the working directory, staging area, commit, and push. In the working directory, users create, edit, or delete files using basic terminal commands such as mkdir, touch, and cd. The staging area temporarily holds selected changes before they are saved, using commands like git add and git status to manage what gets committed. Finally, git push sends the committed changes from a local machine to a remote repository such as GitHub.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

CTF Challenge Shows How HTTP Request Smuggling Bypasses Path-Based Access Controls

A web challenge from BrunnerCTF 2026 demonstrated a classic CL.TE HTTP request smuggling vulnerability in a simulated internal wiki application. The target page, /wiki/internal/flag, was hinted at via robots.txt but returned a 403 Forbidden response to direct access. The exploit worked because the front-end proxy honored the Content-Length header while the backend Kestrel server prioritized Transfer-Encoding: chunked, causing the two layers to disagree on where one request ended and another began. By crafting a single POST request containing a smuggled GET for the restricted path, the attacker bypassed path-based authorization middleware that only applied to externally routed requests. The smuggled request reached Kestrel directly on the same keep-alive connection, returning the internal article and the hidden flag.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Video Streaming Pipelines Work: A System Design Breakdown

A technical explainer on DEV Community walks through the system design behind video streaming, from upload to playback. The piece frames the problem using a relatable scenario: sending a large skydiving video to a friend across the world. It outlines functional requirements for both uploaders and viewers, including resumable uploads, progress tracking, and smooth cross-network playback. The article also highlights non-functional challenges such as handling massive files, connection drops mid-upload, and sudden spikes in concurrent viewers. It argues that naive single-request upload approaches fail at scale, setting the stage for more robust pipeline architectures.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Google Identifies Three Russian Spy Groups Hijacking Auth Flows, Bypassing MFA

Google Threat Intelligence Group published research on August 20, 2026, detailing three suspected Russian espionage clusters — UNC6293, UNC7005, and UNC5976 — that exploit authentication flows rather than stealing passwords directly. The groups target academics, government officials, aerospace and defense personnel, and think tank staff across Europe, Ukraine, and the United States. Their methods include abusing OAuth consent flows, application-specific passwords, device code grants, and WhatsApp device linking, meaning fully deployed multi-factor authentication does not stop the attacks. UNC5976, active since at least March 2026, automated OAuth token harvesting using legitimate cloud infrastructure, redirecting victims through real Google login pages before silently stealing tokens post-authentication. Google disrupted at least 12 related domains, but UNC5976 adapted by migrating its phishing infrastructure to other providers and also deployed a malicious Excel plugin called HEADRUSH targeting Ukrainian organizations.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer's AI bot outperformed GPT-4 rivals, but a dedup bug silently erased training weights

A developer built a capture-the-flag arena where language models compete against each other, using game replays to fine-tune a local Qwen2.5-3B model with MLX LoRA adapters. The custom bot outperformed five larger cloud models on offense, capturing 400 flags across 221 games compared to 275 for the next-best GPT-OSS 120B model. However, the bot's defensive performance remained weak, prompting multiple retraining attempts that all appeared to fail. The root cause was a silent bug: a deduplication step in the data pipeline discarded all repeated examples, completely canceling out the intentional curriculum weighting that relied on repetition for emphasis. As a result, 41.5% of the weighted training corpus — roughly 39,000 lines — was silently dropped before the trainer ever saw the data.

0 comments Read more at DEV Community