Mastodawn

@ogogon @m17_project it’s actually reverse engineering in almost all cases.

@ogogon @m17_project no particular reason, besides the fact that we only support ASCII characters right now, so we would need to add the correct glyphs and still fit within each target memory.

OpenRTX Jan 13

@ogogon yes, also Brandmeister suffered from callsign spoofing, so finding a way to authenticate ham radio operators can be beneficial.

OpenRTX Jan 13

@ogogon this is currently an open problem. M17 has some spare bandwidth that is being used to transmit metadata during transmission, e.g. GPS data. However that channel has a very low bitrate so we need to pick a lightweight cipher that can fit in there. I would focus on achieving practical security, e.g. forging the signature of a single frame can be done but doing so on a whole transmission in real time becomes impractical. We also need to take into account that frames can be lost.

OpenRTX Jan 9

@ogogon without the modification M17 will not work at all. The analog functionality should work also without mod.
You can find the binary here:

https://github.com/OpenRTX/OpenRTX/releases/download/v0.4.3/openrtx_dm1701_v0.4.3.bin

OpenRTX Jan 9

@ogogon Baofeng 1701 is indeed supported by OpenRTX and M17, it will be listed soon on our website.
M17 on this radio requires a hardware modification, you can find a guide here:
https://github.com/M17-Project/DM-1701_mod

OpenRTX Dec 28

For those of you who are at 39C3, tomorrow there will be an OpenRTX meetup!
Come chat with Silvano IU2KWO and other OpenRTX devs and users.

https://events.ccc.de/congress/2025/hub/en/event/detail/openrtx-meetup