View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006036||OXID eShop (all versions)||2.2. Shop settings||public||2015-02-04 16:10||2022-01-28 14:47|
|Target Version||7.0.0-rc.2||Fixed in Version||7.0.0-rc1|
|Summary||0006036: Config values are stored as encoded, which is simply annoying.|
|Description||The config values are mostly stored with usage of the MySQL function ENCODE.|
I do not see any reason to do so, since the code is practically open source. Anyone can change and modify whatever one wants. But the encoding is totally annoying for anyone doing serious development with your shop software. I am not the only one who is annoyed:
|Tags||No tags attached.|
|PHP Version||Not defined|
|Database Version||Not defined|
Store config data encrypted in the database?
DECODE() and ENCODE() is used with a public known key to store data in the OXCONFIG table. The key is actually the same for each installation and shop version.
Additionally, some contents of the OXCONFIG table are stored as temporary, unencrypted data in the tmp folder anyways.
|This will be removed in OXID eShop 7 as MySQL 8 does not even support ENCODE anymore.|