"goes to brother.com and prints brick_my_printer.pdf" is really quite a silly place to arrive, starting from "printers can be updated via print job". An update

"goes to brother.com and prints brick_my_printer.pdf" is really quite a silly place to arrive, starting from "printers can be updated via print job". An update print job is just a blob of data that anything can squirt at the printer. A person doesn't need to press "print" anywhere, or do anything at all, or even know that it happened. Any driver or application software that was written by the same people as the printers own firmware can do it all by itself any time it wants, for the same reasons that the printers own firmware does in fact already do it all by itself any time it wants. I don't know why you find this so unbelievable. Two seconds on kagi yields http://h10032.www1.hp.com/ctg/Manual/c06530233.pdf http://h10032.www1.hp.com/ctg/Manual/c06530233.pdf "HP printing devices have the ability to accept firmware upgrades, solutions software and custom color table “bundles sent as a print job. The “Allow firmware updates sent as print jobs (Port 9100)” setting controls the ability for the printing device to accept firmware over the standard printing port, and also applies to firmware sent over all print-path methods including FTP, LDP, IPP(s), EWS Print page or Copy command." (meaning that although the label on the setting in this particular printer's ui mentions "port 9100", it's not actually limited to jetdirect, the special print job is recognized no matter what path or protocol it took to arrive at the printer)