HP Shutting Down Default FTP, Telnet Access To Network Printers (pcworld.com)
Security experts consider the aging FTP and Telnet protocols unsafe, and HP has decided to clamp down on access to networked printers through the remote-access tools. From a report on PCWorld: Some of HP's new business printers will, by default, be closed to remote access via protocols like FTP and Telnet. However, customers can activate remote printing access through those protocols if needed. "HP has started the process of closing older, less-maintained interfaces including ports, protocols and cipher suites" identified by the U.S. National Institute of Standards and Technology as less than secure, the company said in a statement. In addition, HP also announced firmware updates to existing business printers with improved password and encryption settings, so hackers can't easily break into the devices.
Oh no HP, after you disabled my compatible cartridges, I am not getting your dirty firmware ever again in my printer.
You don't need to be an expert to know that FTP/TELNET is unsafe. So is SSH in some configurations.
Interesting! Modders, please mod up HP for a very interesting application!
Sent as ripples into the electromagnetic field. No single photon has been harmed in the process.
worse than HTTP because the latter is a transport layer only. All auth is accomplished through HTTPS.
Strictly speaking, he did say HTTP, which without TLS isn't any better. Of course there's nothing suggesting that HTTP without TLS would be open so it's a bit of a weird leap to make.
I will say in practice HTTPS on embedded IT equipment is only a little useful in most cases, since they have unverified certificates to kick things off. There are rare areas that bother to do proper certificates and/or rare software that gives self signed certs the appropriate treatment, but overwhelmingly people click on https and click through the warning which reduces https to http level security (anyone who can sniff is almost always in a position to inject themselves).
XML is like violence. If it doesn't solve the problem, use more.
A possible use case would be an enterprise with a very specialized, expensive printer- like a super-high speed or large format printer- that's kept in a centralized location. Jobs would be submitted remotely and then the output would be shipped to the submitter. HP makes some very high-end printing products where that kind of workflow makes sense.
There's no point in questioning authority if you aren't going to listen to the answers.