| Summary: | [ebuild] New package: net-misc/netkit-telnet-ssl | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daniel Lin <ephemient> |
| Component: | New packages | Assignee: | Default Assignee for New Packages <maintainer-wanted> |
| Status: | CONFIRMED --- | ||
| Severity: | enhancement | Keywords: | EBUILD |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://packages.debian.org/unstable/source/netkit-telnet-ssl | ||
| Whiteboard: | sunrise suggested | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
net-misc/netkit-telnet-ssl-0.17.24.ebuild
files/netkit-telnet-ssl-0.17-cflags-gnu_source.patch |
||
Created attachment 201892 [details]
net-misc/netkit-telnet-ssl-0.17.24.ebuild
Needs files/net.issue.sample and files/telnetd.xinetd from net-misc/netkit-telnetd; it's a copy of that ebuild, with minor changes.
Created attachment 201893 [details]
files/netkit-telnet-ssl-0.17-cflags-gnu_source.patch
files/netkit-telnetd-0.17-cflags-gnu_source.patch is necessary but doesn't apply cleanly to netkit-telnet-ssl, so I had to modify it a bit.
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. |
At the moment, the only way to connect to or run a SSL-enabled telnet server is to use the non-SSL-capable variants (net-misc/netkit-telnetd, net-misc/telnet-bsd) through stunnel or similar. ("openssl s_server/s_client" and "socat ssl-l:/ssl:" are unable to handle telnet authentication, environment, etc.) Reproducible: Always Steps to Reproduce: $ telnet -z ssl some-host 992 # in.telnetd -z ssl Actual Results: Both fail. Expected Results: Both should negotiate SSL.