On 2014-06-26 19:49, James Knott wrote:
On 06/26/2014 01:29 PM, Carlos E. R. wrote:
Even on newly bought machines, like routers: only telnet and http, not https. So /they/ are using telnet servers, and force us to use them...
Then you need a regular telnet client, not a server to talk to those boxes.
Absolutely. My intent was to comment that many manufacturers only implement telnet servers on their (new) machines.
Also, many of them, such as Cisco gear also support ssh. In fact, Cisco recommends allowing ssh only. HTTPS is also supported. A ssh client is built in with Linux and, if you're forced to use Windows, you can use PuTTY, which supports ssh, telnet and serial ports.
But that is a serious, expensive, router. My home TP-Link has no "https:" nor "ssh", nor do I see it in the config. cer@Telcontar:~> nmap router.valinor Starting Nmap 6.40 ( http://nmap.org ) at 2014-06-26 20:04 CEST Nmap scan report for router.valinor (192.168.1.1) Host is up (0.019s latency). rDNS record for 192.168.1.1: router Not shown: 997 closed ports PORT STATE SERVICE 23/tcp open telnet 80/tcp open http 1900/tcp open upnp Nmap done: 1 IP address (1 host up) scanned in 0.32 seconds cer@Telcontar:~> Most home routers I have seen are similar. And those same routers are used at small business, not even that small. Those that make do with an ADSL or smallish fiber. My multimedia center, doesn't have natively ssh either, although it has ssh with alternative software from the community. My HP printer has http, not https - and HP surely is a serious manufacturer. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)