Bugfix
Detail
#27895
Obfuscated configuration values: Prefix 'unencrypted:' sometimes does not work
Since ticket #20304 it is possible to store encrypted configuration settings(@Encrypted) in plain text. To do this, unencrypted: must be written in front of the value.
Problem
This does not always work. In rare cases, the application "decrypts" the entire value to non-sense.
Analysis
The code does not detect plain text values by checking whether the string begins with unencrypted:. Instead, it always tries to decrypt the value. If the value starts with unencrypted:, this almost always fails. This exception is caught. Only then is a check made for unencrypted:. If the value begins with it, the part after this prefix is used. Otherwise an exception is thrown.
Sometimes, however, a value that begins with unencrypted: can be "decrypted". However, the result is technical nonsense.
Test
No test, not worthwhile.