![rotmg hacked client 27.7x14 rotmg hacked client 27.7x14](https://i.imgur.com/oYdeSGj.png)
#Rotmg hacked client 27.7x14 update#
I started by inserting a reverse bash tunnel into the update script and discovered, much to my surprise, that BirdDog encoders run Linux, an Ubuntu 16.04 variant of Linux. “HOLY CRAP BATMAN 1” is something I stuck into birddog-update.sh. Untarring, modifying and retarring the firmware package and then applying said update file works just fine. The answer is BirdDog encoder firmware updates are not signed. I’m not willing to break these devices, as they are ultimately for business use and under warranty.Īnd then I had a thought: what if the BirdDog firmware update files, which are just tarred-gzipped archives weren’t signed? or perhaps the encoders didn’t validate the signature? I attached a multi-channel logic analyser to the BOT_CT port… nothing useful.Ī portscan revealed that the encoders run an Ubuntu (!) ssh server on port 9031… but none of the standard passwords gave me access.
#Rotmg hacked client 27.7x14 serial#
I took the hardware apart too, to look for a debug serial port, a tty, I didn’t find an accessible one. So I took the firmware apart to look for software backdoors, I didn’t find any. I asked if they could detail their build process or firmware packaging process for firmware so I could make my own changes, that was a no. I asked if they could let me beta test firmware, that was a no. I asked BirdDog to include an NTP daemon, they said it had been added to the wish list. It’s clear that BirdDog encoders are using a system time reference though, so if they (1) ran Linux and (2) ran a time synchronisation daemon on said Linux instance, it’d solve the OBS sync issue. I discovered that BirdDog encoders do timestamp the video streams they emit, but those streams get their time from a clock that isn’t set (it starts from the Unix epoch, which is the encoder’s boot time). Libndi’s SDK docs specifically refer to timestamping of video payloads and synchronisation of video source clocks (whether it be the encoder’s clock or the camera’s clock). Low latency mode is an edge case (read “hack”/”workaround”) mode for libndi, normally you’d want to run libndi feed ingestion with this setting turned off, which allows for some buffering, albeit minor. Part of the reason for this was curiosity, but the other reason was because NDI video streams from BirdDog NDI encoders don’t sync in OBS, unless OBS uses libndi’s low latency mode. You can find the pared-down 4K Flex In version of this page here, which is still being built (I’ve just rooted the device).Īround two months back I took a dive into BirdDog NDI encoder firmware, specifically Minis and 4K Flex unit firmware. This guide has some specific detail related to the BirdDog Mini as, after backdooring into the 4K Flex In, I’ve found that there are some differences.