\

Getting debug access on a Brother printer over Telnet

40 points - last Monday at 1:54 PM

Source
  • ciex

    today at 9:48 AM

    But what are the things you would want from a printer that is already quite reliable, not DRM'd, and presumably compatible with all the devices you want to use it with?

    • amstan

      today at 8:34 AM

      I can't tell if any of this gives you more access than the normal http admin interface.

        • cheschire

          today at 9:43 AM

          Well now you can point an LLM at it. I’m not sure that gives you anything either, but I’m not sure the hacker ethos makes that a priority.

          Sometimes a hack is just cool because it’s a hack.

      • devy

        today at 8:16 AM

        Great write up and reverse engineering of firmware! I hope to see Epson MFC inkjet printers to have similar discovery too (perhaps it literally a prompt away with a link to this article).

          • gregoryl

            today at 9:00 AM

            I was digging around an epson receipt printers firmware recently; got as far as discovering http endpoints (hardcoded auth) to remotely enable ssh (but not login), and some other diagnostic access. They seem fairly well put together.

        • greyface-

          today at 8:42 AM

          The same SET USER 640184.571119 command works on my 2012 Brother MFC-9460CDN.

          • nubinetwork

            today at 9:16 AM

            But what do those numbers mean?

            • cellsstudio

              today at 8:49 AM

              This is a really cool little project. Also, the title gave me a strong hit of like mid 2000's internet "hacking" content that I tore through when I was in high school.

                • NitpickLawyer

                  today at 9:07 AM

                  The e-zines can make a comeback, there's probably enough content now. phreak2030s: "put the local load in the bearing firmwares". Or something :)

              • josteink

                today at 9:50 AM

                This piece had potential but IMO was a bit disappointing. The entire thing could be summarized as:

                1. "I used AI to download and analyze a firmware image, and found a way to unlock DEBUG mode."

                2. "I didn't actually explore the DEBUG mode at all, but here are the commands the AI found for me (link)"

                I'd love for the author to at least put in a little real effort, explore some of these debug commands, and tell us why they are interesting.

                As this is - I find it to be very minimum-effort, AI-assisted blog-slop. Sorry!

                (Now for the link[1] to the actual (unexplored) debug-commands... It has really weird casing of the descriptions in the "behaviour"-column. Does anyone know why that is?)

                [1] https://inventor7777.github.io/brother-mfc-commands-list.htm...