On Thu, Mar 10, 2022 at 11:55:39AM +0100, Alex wrote:
Hi.
I have seen in
https://lwn.net/Articles/887313/ that you plan to remove the
"telnet" protocol from curl-minimal.
I use `curl -v telnet://....` almost every day for debugging purpose just
because curl is in the most systems by default installed.
I know that there are some other tools like socat, normal telnet, nmap and so
on but this tools need to be installed which is not always possible when
fedora is used as docker image.
there was also a short presentation about how to use curl telnet for debugging
on a curl up meeting.
https://curl.se/video/curlup-2017/2017-03-18_02_Aleksandar_Lazic_curl_for...
May I suggest to leave at least the telnet protocol in curl-minimal for
debugging purposes.
The problem is that there's many many debugging tools, and everybody
has their own favourites. You like 'curl -v telnet://', I like 'ss' and
'tcpdump',
somebody else likes 'lsfd' and so on. I agree that it *can* be very useful
to have a debugging tool installed, but it is a very weak argument for adding
those tools always by default. In particular, 'bash' is very useful for all
kinds of debugging, but if possible, it is very good *not* to have it in minimal
containers for the usual reasons (size, dependencies, exposure).
The goal of this change is make it possible (ephasize *possible*) to have a
smaller curl that is useful for the *very common* (emphasis again) tasks.
So sorry, if you want to use curl-telnet for debugging, please just install
curl-full. This is status quo, so with the proposed change you'll not be any
worse off.
That said: depending on how the proposal evolves, I think it make sense to add
more virtual provides for each protocol, so that we can handle the cases where
something moves from -minimal to -full more gracefully, so e.g. you'd be able
to do 'dnf install "curl(protocol/telnet)" or something like that.
Zbyszek