data.coop
/
ansible
8
3
Fork 7
Code Issues 44 Pull Requests 7 Projects 1 Releases Wiki Activity

Forgejo: Publish ssh public key somewhere #138

New Issue
Open
opened 2022-12-07 10:55:05 +00:00 by reynir · 3 comments
reynir commented 2022-12-07 10:55:05 +00:00
Owner
Copy Link
No description provided.
samsapti commented 2022-12-07 16:52:07 +00:00
Owner
Copy Link

@reynir could you elaborate a bit more on this?

@reynir could you elaborate a bit more on this?
samsapti added the
Existing Service
 label 2022-12-07 17:06:29 +00:00
reynir commented 2022-12-09 10:49:38 +00:00
Author
Owner
Copy Link

When you connect with ssh to git@data.coop the host has a public key that you are asked to verify / whether to trust it. It would be nice to have the public key (and fingerprint) published somewhere on the website for example.

When you connect with ssh to git@data.coop the host has a public key that you are asked to verify / whether to trust it. It would be nice to have the public key (and fingerprint) published somewhere on the website for example.
👍 1
samsapti commented 2023-12-28 19:50:29 +00:00
Owner
Copy Link

As an alternative, I just stumbled upon SSHFP records, which are a type of DNS records used to validate SSH host key fingerprints.

As an alternative, I just stumbled upon [SSHFP records](https://unix.stackexchange.com/questions/121880/how-do-i-generate-sshfp-records/121881#121881), which are a type of DNS records used to validate SSH host key fingerprints.
samsapti changed title from Gitea: Publish ssh public key somewhere to Forgejo: Publish ssh public key somewhere 2023-12-28 19:53:25 +00:00
valberg added this to the Devops work project 2024-02-09 07:52:18 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
proxmox
diun
use_sudo
woodpeckerci
linting
mailman
listmonk
sshd-password
Labels
Clear labels   
Blocked

Something is blocking progress

  
Existing Service

Issues/improvements regarding existing services

  
Infrastructure Issue

Infrastructure issue that needs investigation or time to fix

  
Refactor

Refactoring of files / file structure or other improvements

  
Security Hardening

Non-verified / non-critical security improvements

  
Security Issue

Urgent security issue that needs to be fixed ASAP

  
Service Idea

Ideas for new services

  
Service Removal

Removal of services for one reason or another

  
Upgrade service
No Label
Blocked
Existing Service
Infrastructure Issue
Refactor
Security Hardening
Security Issue
Service Idea
Service Removal
Upgrade service
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Devops work
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: data.coop/ansible#138
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?