It breaks any string that contains special characters like an Umlaut for example (äöü) and shows some funny UTF-8 characters in the table after hitting "Save". This probably only needs to be consistently encoded when read and written to file.
Created attachment 909 [details] Screenshot OpenVPN The same happens for OpenVPN as well. The attached screenshot is after multiple attempts to create a connection with invalid name, hence multiple wrongly encoded UTF-8 bytes, and after successfully creating a new connection. In the latter case the web-UI as well as the input to change the remark show individual UTF-8 bytes instead of the correct character "ö".
Can confirm this, just had the same issue when writing "Büro" into any remark of a dhcp lease. This results e.g. in Echo Dot (Büro)
*** This bug has been marked as a duplicate of bug 12395 ***