Backslash interpreter error after major upgrade

[Johnybe]

Steps to reproduce

1. Upgrade Teampass 2.1.26 to 3.0.8

Expected behaviour

Database migration doesn't break backslash encoding in passwords

Actual behaviour

After this major upgrade backslash characters are interpreted like ISO : & # 9 2 ; and not like this : \

Server configuration

RHEL7.9

Web server: apache 2.4.6 Database: MySQL Ver 15.1 Distrib 5.5.68-MariaDB PHP version: 8.0.29 Teampass version: 3.0.8 Teampass configuration file:

Updated from an older Teampass or fresh install: PLEASE attach to this issue the file /includes/config/tp.config.php.

Client configuration

Browser: Chrome Operating system: Windows

Logs

Web server error log

Insert your webserver log here
[tp_config.txt](https://github.com/nilsteampassnet/TeamPass/files/11915710/tp_config.txt)

Log from the web-browser developer console (CTRL + SHIFT + i)

Insert the log here and especially the answer of the query that failed.

[Johnybe]

Old and new database are encoding with utf8 :

+--------------------------+----------------------+ | @@character_set_database | @@collation_database | +--------------------------+----------------------+ | utf8 | utf8_general_ci | +--------------------------+----------------------+

[Johnybe]

Nota : & # 9 2 ; is the HTML code of \

[whismers]

Hello, I have the same problem. I went from version 2.1.27.36 to version 3.1.2. Does anyone have a fix? (without having to start from scratch) Regards,

[Johnybe]

Hi

Teampass upgrade v2 to v3 is a real nightmare.

We leave Teampass for Bitwarden/Passbolt etc..

For personnal use or small company it's ok but for entreprise and teams use , it's not enough robust

[nilsteampassnet]

Closed automatically due to inactivity (no response for over 1 year).