golang-github-skeema-knownhosts 1.2.2-2 source package in Ubuntu

Changelog

golang-github-skeema-knownhosts (1.2.2-2) unstable; urgency=medium

  * Source-only upload.
  * Bump Standards-Version to 4.7.2 (no changes)

 -- Maytham Alsudany <email address hidden>  Tue, 11 Jun 2024 18:43:17 +0800

Upload details

Uploaded by:
Debian Go Packaging Team
Uploaded to:
Sid
Original maintainer:
Debian Go Packaging Team
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Oracular release universe misc

Builds

Oracular: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
golang-github-skeema-knownhosts_1.2.2-2.dsc 2.3 KiB 29101be06b6d0ae68193fc53eb324e11539afd40c3f41b0d450fb32cfa52f52a
golang-github-skeema-knownhosts_1.2.2.orig.tar.gz 13.4 KiB 3b2f3ae6c4fa9f6cdc646985297d2fd5c62d8313ec893af5de42aafe524424a8
golang-github-skeema-knownhosts_1.2.2-2.debian.tar.xz 2.4 KiB f8e0d243824d822a3a2082ef198ae307a19e3fb50ac0da9367ef5c266694c7b0

Available diffs

No changes file available.

Binary packages built by this source

golang-github-skeema-knownhosts-dev: Go SSH known_hosts wrapper with host key lookup (library)

 Go provides excellent functionality for OpenSSH known_hosts files in its
 external package golang.org/x/crypto/ssh/knownhosts. However, that package is
 somewhat low-level, making it difficult to implement full known_hosts
 management similar to command-line ssh's behavior for StrictHostKeyChecking=no
 configuration.
 .
 This repo is a thin wrapper package around golang.org/x/crypto/ssh/knownhosts,
 adding the following functionality:
  * Look up known_hosts public keys for any given host
  * Auto-populate ssh.ClientConfig.HostKeyAlgorithms easily based on
    known_hosts, providing a solution for golang/go#29286
  * Write new known_hosts entries to an io.Writer
  * Properly format/normalize new known_hosts entries containing ipv6
    addresses, providing a solution for golang/go#53463
  * Determine if an ssh.HostKeyCallback's error corresponds to a host whose key
    has changed (indicating potential MitM attack) vs a host that just isn't
    known yet