Where to start ?
(1) I 100% agree with DRM, and the encoding of the valuable IP of the developers.
But some of the basic .cfg file, really do not have to be encrypted, to protect the plane from being pirated.
(2) You cannot just move an encrypted plane from Official, and put it in Community, and share it with others. The DRM works here, so it that will not work.
Full disclosure- I have not tried it, but I must assume the DRM system prevents that !!
(3) The planes you purchase through the Ms_Store, being encrypted, can obviously be copied and shared, but will not run on the copied to PC - so there is no point, They are DRM protected.
(4) Many of the plane you buy from 3rd party developers, get installed and locked to your system, and will not work correctly (or at all) if moved to another PC.
The 3rd party developers are NOT stupid !!
The main reason for wanting to NOT have some of the .cfg files encrypted, is NOT to enable Piracy – but to allow corrections to those files to help make their planes fly in a more realistic manner, because, unfortunately, the developers do not always get it right, or if they do, a MSFS update “Can” cause those setting to need modification.
The bottom line is, that NOT including all the .cfg files in the .fsarchive encrypted files, will make NO DIFFERENCE to the DRM protection of those planes.
However,
One valid argument can be made for keeping them form being edited by the user.
If the user edits them and has an issue, and then tries to get the DEV’s Tech support to help sort out the issue they have caused by the edit… it is a major issue for the developer, and a drain on their resource, to try to help fix, something that the user has been able to edit.and mess up.
NOTE:
FBI Anti-Piracy Warning: The unauthorized reproduction or distribution of a copyrighted work is illegal. Criminal copyright infringement, including infringement without monetary gain, is investigated by the FBI and is punishable by up to five years in federal prison and a fine of $250,000.