Bug 1955668 - spectool -g refuses to download from FTP
Summary: spectool -g refuses to download from FTP
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rpmdevtools
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-30 15:58 UTC by Jaroslav Škarvada
Modified: 2021-04-30 16:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-30 16:15:11 UTC
Type: Bug


Attachments (Terms of Use)

Description Jaroslav Škarvada 2021-04-30 15:58:45 UTC
Description of problem:
It seems FTP transport stopped working.

Version-Release number of selected component (if applicable):
rpmdevtools-9.3-3.fc33.noarch

How reproducible:
Always

Steps to Reproduce:
1. spectool -g postfix.spec 
2. 
3.

Actual results:
Downloading: ftp://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.6.0.tar.gz
Download failed:
No connection adapters were found for 'ftp://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.6.0.tar.gz'

Expected results:
File downloaded

Additional info:
wget works as expected:
wget ftp://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.6.0.tar.gz
--2021-04-30 17:53:54--  ftp://ftp.porcupine.org/mirrors/postfix-release/official/postfix-3.6.0.tar.gz
           => „postfix-3.6.0.tar.gz“
...
downloaded

Comment 1 Fabio Valentini 2021-04-30 16:15:11 UTC
The python library that is used by spectool for streamed file downloads (requests) does not support FTP.
Adding support for FTP would require porting spectool to a different library (which I won't do) and adding another dependency (which RHEL maintainers do not want). Sorry.

PS: Does postfix only offer downloads via FTP? That seems wildly insecure, I would strongly recommend using HTTPS for downloads, if possible.


Note You need to log in before you can comment on or make changes to this bug.