@Skidilliplop: I used to write the software to setup these print servers back in the late 1990s. Epson, Canon, Brother, Oki, Kyocera, NEC, Compaq, Lexmark, etc, etc. Amazing how many companies sourced their printserver from us. Only HP did not. And yes, EVERY ONE of those models could have their firmware replaced via printing without any password required. Though this usually had to be after a power cycle.
Hacked firmware could then be setup to do all kinds of nasties. We often thought of adding packet sniffers to the firmware as it would be so easy to do. Especially funny as we knew our kit was in banks, military, all kinds of places.
This Brother uses a different print server now. And I can get my hands on similar models to experiment with if things get confusing. Though, I think our biggest headache will be that awful BT Router.
With a small two seat company, there is less for the hacker to go for. Easier to take more normal attack vectors than trying to hack the printer.
So, once we have Damien setup and printing on the default port 9100, we will make sure to bump him over to a less common port number.
Oh - and Damien I would make sure that you don't post your IP Address up here, otherwise you will find the odd strange printout appearing on your printer. I remember when we sent print-spam to little places like The White House and Bill Gate's personal printer at Microsoft. 1997 I think it was. We were also writing network discovery software... so we had fun finding places to point it at. (Which would often trigger a few annoyed phone calls from Sys Admins calling us to tell us to stop hacking them. Though it was usually just the Universities who had tech good enough to spot us)
Of course, the funny part of printing out on those printers was the lack of an audit trail. I would have confused the recipients.
Now the question is - the average Port Knocking tool that the usual script kiddie uses, does this test for port 9100?
