Help! Making Application Configuration File Immutable

[Argentavis]

Hi everyone,

I hope you're doing well! I recently encountered a challenge in my application and would appreciate your insights.

I'm working on an application that utilizes local storage to store user points configuration. I noticed that even though I can manually change the points to 9999999, the value reverts back when I refresh the application page. I suspect this might be due to integration with the server side, causing the constant value I've defined to reset.

I've tried making the application "immune" by changing permissions to read-only for all users and using the chattr command to prevent modifications. Unfortunately, it didn't work.

Has anyone faced a similar issue, or does anyone have suggestions on how to make the file truly immutable and prevent the application from altering its contents?

Thanks in advance for your help!

 

[fedesito]

It's most likely that the server handles currency server-side.

 

[Argentavis]

It's most likely that the server handles currency server-side.

Yes, it is! but if I immunize the file, server will not have access rights to change it.

 

[jimmywilliams]

Making an application configuration file immutable can be a great security and stability measure, especially in production environments. It helps prevent accidental changes, unauthorized modifications, and configuration drift over time. However, it's also important to have a clear update process in place, since immutable files can make maintenance and deployment updates more challenging if not properly managed. A balanced approach is to combine immutability with version control and automated deployment workflows to ensure both security and flexibility.