Files
tekton/wiki/SSH-Setup-Windows.md
T
adtpdn 625ff5ec69
CI / Run Tests (push) Failing after 2s
CI / Export Windows (push) Has been skipped
CI / Export Linux (push) Has been skipped
CI / Export Android (push) Has been skipped
Test Suite / Unit Tests (GUT) (push) Failing after 2s
Test Suite / Integration Tests (push) Failing after 3s
Test Suite / Code Style Check (push) Failing after 2s
Test Suite / Security Scan (push) Failing after 1m1s
CI / Create Release (push) Has been skipped
Replace SSH tutorial in README with wiki pages by OS
Linux, macOS, Windows SSH setup guides moved to wiki. README becomes index with wiki links and breadcrumb to existing docs.
2026-07-02 01:35:51 +08:00

43 lines
1.6 KiB
Markdown

# SSH Setup — Windows
## Install Git for Windows
Download from https://git-scm.com/download/win and install with default options.
This installs `git`, `ssh`, and `git-bash`.
## Generate an SSH key
Open **Git Bash** and run:
```bash
ssh-keygen -t ed25519 -C "your-name@example.com"
```
Press Enter to accept the default path `C:\Users\<you>\.ssh\id_ed25519`. Set a passphrase, or leave it empty.
## Add the public key to Gitea
```bash
cat ~/.ssh/id_ed25519.pub
```
Copy the full output, then open `http://git.klud.top/user/settings/keys` in your browser and paste it. Title: `windows-<yourname>`.
## Accept the server fingerprint and test
```bash
ssh -T git@thunderobot -p 222
```
- If asked `Are you sure you want to continue connecting (yes/no/[fingerprint])?`, type `yes`.
- Expected output: `Hi there, <yourname>! You've successfully authenticated with the key named windows-<yourname>, but Gitea does not provide shell access.`
If you get this message, the key is recognized.
## Clone a repo
```bash
git clone git@thunderobot:222/danchie/tekton.git
```
Or with tea:
```bash
tea repos clone --git-protocol ssh danchie/tekton
```
## Troubleshooting
- **`Permission denied (publickey)`** — Your key wasn't added in the Gitea UI, or `~/.ssh/id_ed25519` isn't being offered. Run `ssh-add ~/.ssh/id_ed25519` in Git Bash.
- **`Host key verification failed`** — Run the `ssh -T` command above interactively at least once.
- **`ssh: connect to host thunderobot port 222: Connection refused`** — Ensure you can reach the tailnet host: `ping 100.93.226.13`. If ping fails, your machine isn't on the tailnet.