Bug 2087076

Summary: rubygem-net-ssh: support the ed25519 cipher
Product: [Fedora] Fedora Reporter: Jarek Prokop <jprokop>
Component: rubygem-net-sshAssignee: Jarek Prokop <jprokop>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ruby-packagers-sig, shreyankg, tdawson, vondruch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-net-ssh-6.1.0-6.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-01 13:53:19 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1984466    
Bug Blocks: 1962869    

Description Jarek Prokop 2022-05-17 09:16:42 UTC 
Description of problem:
The review for rubygem-ed25519 was approved, so rubygem-net-ssh should test it and have it in the package's requires.

Version-Release number of selected component (if applicable):
rubygem-net-ssh-6.1.0-4.fc37

Expected results:
rubygem-net-ssh builds with rubygem-ed25519 and the tests for ed25519 pass.

Additional info:
the gem x25519 might be required for full support of ed25519 judging by the preliminary testing of the net-ssh + ed25519.
Comment 1 Ben Cotton 2022-08-09 13:38:44 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle.
Changing version to 37.
Comment 2 Jarek Prokop 2022-12-01 10:01:02 UTC 
It is going to be fixed in current rawhide.
Comment 3 Fedora Update System 2022-12-01 13:51:52 UTC 
FEDORA-2022-17ca586da6 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-17ca586da6
Comment 4 Fedora Update System 2022-12-01 13:53:19 UTC 
FEDORA-2022-17ca586da6 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.