Hmm, what's that? 🤔

The radio codeplug password feature was deprecated in M2021.01. This allowed the configuration in the radio to be protected by means of a password which meant that anyone attempting to read the radio would need to enter the password. It also allowed the codeplug to be stored locally on a disk.

This has been replaced in M2025.01 with a new means of securing configuration data called CPS 2.0 Codeplug Archive Protection.

CPS version 2.153.167.0 (and later) offers enhanced codeplug archive protection to secure your saved radio configurations during transfer and storage. You can now encrypt .xctb codeplugs with a password and, as a result, they no longer require the old codeplug password, even if it was previously set.  Archives protected only with the legacy codeplug password will remain unchanged.

For this, a new button has been introduced on the upper right hand side of the CPS main view. The button allows you to set up, change or remove the Archive Password, as well as determine whether the opened codeplug is protected or not. The above video shows how to use this feature.

In addition, there is a tick box in Settings ▶ Security, that when selected will remind the user to provide a password when saving an unprotected codeplug. They can of course, click on the Proceed button, in which case the codeplug will be saved without a codeplug.

The chosen password must be at least 8 characters long (maximum 64) and must include a number and one special character.

This password only protects a saved .xctb codeplug file. It does not protect the configuration data in a radio - for this you should rather use TLS-PSK. Both of these should also form part of other common-sense security measures.