Upstream software project

sshexport

Install your SSH keys on remote sites

About sshexport

Install your SSH keys on remote sites

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.sshexport: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
sshexport
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
LicenseRef-Callaway-BSD AND ISC
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This script tries to export SSH public keys to specified sites. It will walk the user through generating key pairs if it doesn't find any to export. It handles all the fiddly details, like remembering the SSH key file names, updating the authorized_keys and making sure local and remote permissions are correct. It tells you what it's doing if it has to change anything.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package sshexport

    43 (Fedora 43) (Unspecified): Install your SSH keys on remote sites

    2.4-15.fc43: noarch

    Source: sshexport

Fedora 44

  1. Package sshexport

    44 (Fedora 44) (Unspecified): Install your SSH keys on remote sites

    2.4-16.fc44: noarch

    Source: sshexport

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.