Baofeng DM32 DM-32 256 bit Encryption Channel Setting.

[pb3400]

The bug will surely be fixed in future updates.
On the other hand you are aware that it is not a real AES256 that you have? it looks like AES256, it tastes like AES256 but it's not AES256 and it's decryptable in a few minutes if you intercept about thirty conversations of a few seconds.

This is false.

 

[Appnut]

DM32 DM-32 256 bit Encryption Channel Setting.

After setting up the 256 bit Encryption details, I tried to use Encryption in a channel setting. When I checked the box for Encryption and entered the Encryption ID, as soon as I left that channel... it reverted to Blank. SOLUTION - Export the Channel Info to a CSV file and manually put in your Encryption ID info. Import that Channel CVS back into the CPS and it will stay.

CPS 1.28
Firmware DM32.01.01.040

Thank you so much, this was the answer, but let me expand some more for others Who might be as dumb as me. IT WILL BE LONG LOL

First I have the same CPS and firmware as the original poster (N0OVC) and I was able to TX between my anytone 878+ and the Baofeng DM-32 using AES 256 encryption.
In the DM-32 CPS first on the left side of the CPS click the tab DIGIT then digital encrypt systems.
Now double click where it says digital encrypt 1 and a box will pop up.
under type" use the drop down menu and choose AES 256, just leave the encryption number as 1.
now in the bottom box click with your mouse and erase the one zero.
now copy and paste using your code in this box, an example E9EC44E8859573EEA8FFDA2330D0AF98CB6562AAF7219322B7D8030F6A565D66
Using your mouse only (DO NOT USE THE SHORTCUT CTRL-V) that's what drove me crazy- er.
Now on the left side menu click on channel and your channels menu will pop up.
Choose the channel your going to use and double click on it.
I wont go into detail here as i'm advising on the encryption
Look on the right side of this open channel box and click in the small box that say's encryption.
Just below that will be another drop down menu, choose encrypt 1
underneath that will be another drop down menu, choose the DMR ID you want to TX with.
now click ok and exit that box.
Now look towards the middle of your screen slightly to the right for the export button and click on that.
Now a "save as" box will pop up, just name it encrypt and save it to your desktop for Convenience.
Now using excel or whatever spreadsheet program you have open the file.
look for the channel or channels your going to use the encryption on and scroll to the right and look for the second column
that says encryption (YEA Theres two) (on my excel it was the AA column) double click in that box and type Encrypt 1
now look a few columns to the right DMR ID (on my excel it was column AF) and make sure it has your radio name like the rest in the same column, if not type it in.

Now in excel just click save and then you must exit that program.
go back to your Baofeng CPS and make sure your in the channel view if not click from the left menu.
Look to the middle menu which says IMPORT and click on that and a box will pop up,
navigate to where you saved that Excel (*csv) file and then click OPEN on that box.

It should say import successful, click ok
now click top left menu file and SAVE your codeplug
NOW click WRITE to radio. and you should be home free.

Thanks again N0oVC for guiding me in the right direction

 

[therealkf]

Ok, there is no backdoor with fixed PI Header in your DM32. Can you give the firmware number?

If other people are doing the same tests, we may be able to check if it's a backdoor, or if the firmware of all Chinese radios was produced by a single manufacturer and the same bug was copied everywhere.

Did you all ever shake out the firmware version on this? I've only been able to look at Baofeng_DM_32UV_Firmware_046_20250327.zip

I was able to confirm DM-32UV Firmware "046" seemingly does not exhibit the behavior through disassembly. So does anyone have firmware that is pre .46 they can give me, so we can chase down where it was confirmed to occur? Someone have v39 or v32 zip files?

 

[doriboni]

Did you all ever shake out the firmware version on this? I've only been able to look at Baofeng_DM_32UV_Firmware_046_20250327.zip

I was able to confirm DM-32UV Firmware "046" seemingly does not exhibit the behavior through disassembly. So does anyone have firmware that is pre .46 they can give me, so we can chase down where it was confirmed to occur? Someone have v39 or v32 zip files?

Unfortunately I didn't think to note the firmware version. and the friend I had done the tests with, sent the DM32 back to where he had bought it and sent an email of complaint to Baofeng.

 

[therealkf]

I did find 039... still working on 032. Updated findings here:

Chinese backdoor

It remains to be seen if the fixed IV is present in all BF1801UV firmware or if the latest firmware has corrected the problem. Trying to find a confirmed vulnerabilities copy of the firmware. 046 seems not to have the behavior... I just found 039, so looking at it next. I need 032 and earlier...

forums.radioreference.com

Sorry for the cross posting. I'm now also looking for UV32.01.01.029 firmware bundle zip or rar as well as the previously mentioned DM32.01.01.032

 

[therealkf]

Confirmed vulnerable on DM32.01.01.032
Noted here: Chinese backdoor