逆向工程 Drobo 5N 网络协议
一位 Drobo 5N 所有者使用 REA 对该设备的远程控制网络协议进行逆向工程,并发布了一个 Python 脚本,用于执行握手并打印状态、系统、网络和驱动器信息。
关于这个案例
这篇 Reddit 帖子描述了如何使用 reverse engineer anything(REA)来分析用于远程控制作者自己的 Drobo 5N 的协议。在抓取数据包并工作数小时后,作者发布了一个 Gist,其中包含一个标准库 Python 脚本,该脚本执行网络握手并收集 Drobo 的状态、系统、网络和驱动器信息。目标是实现与所有者老旧硬件的互操作性,包括最终实现远程关机,并且作者邀请在其他 Drobo 5N 和 5N2 设备上进行测试。
安装配置
安装方法请查看原始来源。
原文 / README
Long-time Drobo owner, first time poster! My Drobo 5N, bought more than a decade ago, on a different continent, is still going strong to this day (I had to replace its fan a couple of years ago). It is occasionally controlled by an equally aging MacBook Pro, leaving me wondering what I would do if the Mac gave up. So for a while I had this itch to throw Claude into the mix to try reverse engineering the protocol that is used to remotely control a networked Drobo. The most recent Opus 5.5 flat out refuses to go deep on this; luckily Opus 4.8 doesn't have these safeguards. So I spent my lazy Saturday morning using reverse engineer anything (a reverse engineering toolbox for agents) attempting to crack open that black box. A few hours, many packet captures and a lot of tokens later, here's the result: https://gist.github.com/tsak/6ecdab10def5731824411bd9b84a7a52 This Gist contains a Python script to execute the network handshake between my laptop and the Drobo, gathering my 5N's status, system, network and drive information, all printed neatly to the terminal. I have tested this with Python 3.11 and 3.15 on Linux. My hunch is that it might work on Windows/macOS and with anything from Python 3.10 onwards. It only uses the standard library. My ultimate goal is to be able to remotely shut the unit down, but for now being able to see how it's doing is quite neat. Because I only have that single unit, it would be cool if anybody could test this. I would be curious whether this works with a 5N2, and of course with other 5Ns. Anyway, cool to see that there's an active community of Drobo users! submitted by /u/Ok-Priority-Go to r/drobo [link] [comments]



