Template:PCN read only system files: Difference between revisions

From Teltonika Networks Wiki
No edit summary
No edit summary
 
Line 1: Line 1:
=={{{date}}}: Implementation of Read-Only System Files in RutOS {{{RutOS}}}==
=={{{date}}}: Implementation of Read-Only System Files in RutOS {{{RutOS}}}==


With the release of RutOS version {{{RutOS}}} in {{{quarter}}}, in {{{name}}} devices will implement read-only permissions for critical system files by default. Previously, customers could modify any system file, potentially causing corruption (e.g., damaging flash memory) due to unintended writes or reads in sensitive areas. The new read-only configuration ensures a more secure and stable environment, though it may affect those who perform non-standard operations. Custom firmware options are expected to allow reverting to a more flexible configuration if required.
With the release of RutOS version {{{RutOS}}} in {{{quarter}}}, in {{{name}}} devices will implement read-only permissions for critical system files by default. The new read-only configuration ensures a more secure and stable environment, though it may affect those who perform non-standard operations.  


{| class="wikitable"
{| class="wikitable"
Line 17: Line 17:
|-
|-
| style="width: 221px; text-align: left; background: white;" | Detailed description
| style="width: 221px; text-align: left; background: white;" | Detailed description
| style="width: 908px; text-align: left; background: white;" | With the release of RutOS version {{{RutOS}}}, the device’s critical system files will become read-only by default. This prevents unauthorized or accidental modifications that could damage the system’s integrity. Standard users operating within typical parameters should not be affected, while those who rely on direct file alterations will need to adjust their workflows. Custom firmware builds can still remove or modify this restriction if necessary.
| style="width: 908px; text-align: left; background: white;" | With the release of RutOS version {{{RutOS}}}, the device’s critical system files will become read-only by default. This prevents unauthorized or accidental modifications that could damage the system’s integrity. Standard users operating within typical parameters should not be affected, while those who rely on direct file alterations will need to adjust their workflows. Custom firmware options are expected to allow reverting to a more flexible configuration if required.
|-
|-
| style="text-align: left; background: white;" | Change reasons
| style="text-align: left; background: white;" | Change reasons

Latest revision as of 09:32, 11 December 2024

{{{date}}}: Implementation of Read-Only System Files in RutOS {{{RutOS}}}

With the release of RutOS version {{{RutOS}}} in {{{quarter}}}, in {{{name}}} devices will implement read-only permissions for critical system files by default. The new read-only configuration ensures a more secure and stable environment, though it may affect those who perform non-standard operations.

PCN Number: {{{PCN_number}}}
Change description
Change type RutOS System Integrity Enhancement
Detailed description With the release of RutOS version {{{RutOS}}}, the device’s critical system files will become read-only by default. This prevents unauthorized or accidental modifications that could damage the system’s integrity. Standard users operating within typical parameters should not be affected, while those who rely on direct file alterations will need to adjust their workflows. Custom firmware options are expected to allow reverting to a more flexible configuration if required.
Change reasons To maintain system integrity, enhance reliability, and prevent unintended damage to core files.
Affected products information
Model Affected order codes Order code changes
{{{name}}} {{{code_name}}} {{{order_code}}} {{{order_code_changes_data}}}
Upcoming change date {{{quarter}}}
Change impact
Risk assessment
  • Customers performing direct system-level modifications may need to adjust their procedures.
  • Standard end-users, who do not rely on altering critical system files, are unlikely to be affected.
  • Custom firmware solutions can restore file-level flexibility if required.
Suggested implementation plan
  • Information included in this PCN will help adapt to the upcoming changes. For more detailed information, please contact your sales representative.
  • Review current workflows and identify any reliance on direct system file modifications. Consider using custom firmware builds if continued system-level customization is necessary.
Acknowledgement of PCN receipt
If no feedback is received within two weeks after the issue date of this notification, Teltonika may accept that this change has been tacitly accepted and can implement the change as indicated above.

To download the PDF version of this notification, [[Media:{{{PCN_number}}}_EN.pdf|click here]].