Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

Create a GitHub Repo and Clone It Locally Using SSH and TortoiseGit (Windows)

Cover photo by Roman Synkevych on Unsplash The basics Before we talk about ssh authentication and cloning, let's build the foundation for using git. Git Setup for Windows First download Git (…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

Cover photo by Roman Synkevych on Unsplash







The basics



Before we talk about ssh authentication and cloning, let's build the foundation for using git.






Git Setup for Windows



First download Git ( https://git-scm.com/download/win ) and install it. You can use all the default settings that the installation wizard offers you but remember to select the options for git bash:



Git Installation Wizard for Windows






TortoiseGit Installation



TortoiseGit is a tool that assists you with git operations (clone, commit, push, branch, …) through a simple and intuitive UI.



You can install TortoiseGit by downloading it from the official website https://tortoisegit.org/download/.



During the installation steps make sure to select “OpenSSH” as the default ssh client:



TortoiseGit — OpenSSH



At the end of the installation you will be asked if you want to run the setup wizard (absolutely yes!), check the “First Start Wizard” checkbox and click “Close”.



This will launch the wizard to help you configure the basic settings of TortoiseGit. Make sure that TortoiseGit recognizes the Git we installed in the “ Setting up Git for Windows” section:



Check git path



The wizard will also ask you if you want to set “Name” and “Email” for your commits. You decide whether to do this at this stage (I did 😉) or once you have finished the wizard in the TortoiseGit settings.



Git and TortoiseGit setup done! 🎉



Now let's move on to the SSH configuration to commit and push (and all other git operations) using public and private keys.









SSH



Now we will create a public key and a private key to use as an authentication method for working with our github repositories instead of the usual user credentials and password.






Public and private key generation



To generate your public and private key pair, open the prompt (Win+re, type cmd, then enter) and run the following command:




ssh-keygen -t ed25519 -C "[email protected]""[email protected]"






When asked to enter the file where to save the key, leave it blank and press Enter. You can choose a passphrase to make key generation even more secure (I didn't 😭):




C:\Users\user>ssh-keygen -t ed25519 -C "[email protected]")"[email protected]" ) 
Generating public/private ed25519 key pair.
Enter file in which to save the key (C:\Users\user/.ssh/id_ed25519):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in C:\Users\user/. ssh/id_ed25519
Your public key has been saved in C:\Users\user/.ssh/id_ed25519.pub






In your user folder (C:\Users<user with which you logged into Windows>) you will find a folder called “.ssh” (if you don’t find it immediately, refresh the user folder) inside which there will be:





  1. public key — file“id_ed25519.pub”


  2. private key — file “id_ed25519” (⚠️ NEVER give to anyone!)






Using the public key



The public key will need to be configured in your GitHub account. To do this, log in to github.com, click on your user avatar icon in the top right and select “Settings” from the menu:



How to access Settings



On the Settings page, select “SSH and GPG keys” from the side menu, and click on “New SSH key”:



GitHub — Adding a new public key



A screen will open where you can enter your key information:



Adding a new key in GitHub



In the “Title” field, enter something that will help you remember what you are using the key for.



Open the .pub file from your C:\Users\user.ssh folder, copy the contents of the file and paste it into the “Key” field. Click “Add SSH key” to finally add your key to GitHub (GitHub may ask you to enter your password — don’t worry, it’s normal 😉)






Using the private key



To set up the private key we will need to use ssh-agent provided with the git installation (see “ Setting up Git for Windows ”). This tool is responsible for retrieving our private key in order to authenticate during commits and pushes (and other git operations).



Open Git Bashby searching for it from the Windows menu search:



Open Git Bash



Create a new file ~/.profile with the following command:




you ~/.profile






A blank file will open, press “i” on your keyboard to enable editing in the vi editor.



Paste the script below (trust me, it's an official github script ). This script will automatically run ssh-agent every time you open git bash:




env =~/.ssh/agent.env 

agent_load_env () { test -f " $env " && . " $env " >| /dev/null ; }

agent_start () {
( umask 077; ssh-agent >| " $env " )
. " $env " >| /dev/null ; }

agent_load_env

# agent_run_state: 0=agent running w/ key; 1=agent w/o key; 2= ​​agent not running
agent_run_state=$(ssh-add -l >| /dev/null 2>&1; echo $?)

if [ ! " $SSH_AUTH_SOCK " ] || [ $agent_run_state = 2 ]; then
agent_start
ssh-add
elif [ " $SSH_AUTH_SOCK " ] && [ $agent_run_state = 1 ]; then
ssh-add
fi

unset env






Editor vi



To save and exit the editor you have to type in sequence Esc : wq (the w stands for write and the q for quit ) and enter:



vi — save and exit



Now let's check if our key is present in ssh-agent. Open a new git bash (so that our previous script can run) and run the following command.




ssh-add -l






If everything is ok, the command will print this message to the screen:



output ssh-add -l



Now a test before we move on to creating our repo in GitHub and trying a clone! 🙂



To test if the connection with GitHub has been configured correctly, just run this command (exactly as shown below):







If everything worked correctly, after the various logs you will find a message similar to the one below which will confirm that everything is ok ✅:




Hi your_email! You've successfully authenticated












Creating a GitHub repo and clone



Log in to GitHub and from your dashboard click on “New” under “Top repositories”:



GitHub — new repo



A page will open to configure the new repo. Give a name to your repo in the “Repository name” field, choose whether the repository should be public or private, check “Add a README file” (because every self-respecting repo has its README 😎) and click on “Create repository”:



GitHub — new repository setup



To clone the repository:




  1. click on “Code” at the top right

  2. Click on the “SSH” tab

  3. Click on the 📑 icon to copy your repo link



ssh key github



Now that you have copied the cloning link you are ready (finally) to use TortoiseGit and clone your local repo.



Open the folder where you want to clone, right click and select “Git Clone…”



TortoiseGit — Git Clone



TortoiseGit will already offer you the link you have in memory (the one copied from GitHub) so you just have to press “OK” and wait for git to do the rest.



TortoiseGit — clone settings



That's all! Enjoy your git 😊









Follow me #techelopment



Medium: @techelopment

Dev.to: Techelopment

facebook: Techelopment

instagram: @techelopment

X: techelopment

telegram: techelopment_channel

youtube: @techelopment

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Vulnerability Remediation & Verification
Syntax validiert (0 Fehler)
title: Detect Exploitation - Create a GitHub Repo and Clone It Locally Using SSH and TortoiseGit (Windows)
id: 7097b095-6d02-45ce-b264-e996140b8b85
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      DestinationHostname:
        - 'dev.to'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "Create a GitHub Repo and Clone" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
(dest_host="dev.to")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
destination.domain: ("dev.to") and event.category: "network"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where DestinationHostName in ("dev.to")
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

IoC Intelligence (1 Indikatoren)
dev[.]to
CTI Threat Relationship Graph2 Knoten / 1 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Create a GitHub Repo and Clone It Locall.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Create a GitHub Repo and Clone It Locally Using SSH and TortoiseGit (Windows)

Thematisch verwandte Begriffe: Create, GitHub, Repo, Clone · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-88003 | InvoicePlane is a self-hosted open source application for managing invoi…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag