Enable FIPS Mode on SLES 15 and Verify the Boot State
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Currently, Zalo is a free texting and calling application used by many people. Recently this application has launched the Data and Memory Management feature , this function Zalo will manage cache data and chat data, especially helping users to delete Conversations take up large amounts of data .
If you want to view and delete conversations with large cache data, but don't know how? Therefore, today Download.vn will introduce an article on how to delete conversations that take up large space on Zalo , please refer to it.
Instructions for deleting conversations that take up large space on Zalo
Step 1: To do this, first we will open the Zalo application on our phone.
Step 2: In the Messages section of the application, click Add in the lower right corner of the screen.
Step 3: Then, in the upper right corner of the screen, tap the settings icon.

Step 4: In the application's Settings section, click Data & memory management.
Step 5: Next, click the Manage chat data button at the bottom of the screen.
Step 6: The screen will now display the amount of cache occupied by each chat. To delete a large conversation, touch and hold the conversation you want to delete.
Step 7: After selecting the conversations you want to delete, click the Delete button in the lower right corner of the screen.
Step 8: A message window "Delete conversation " will appear on the screen, click the Delete button.
Step 9: Once the conversation has been deleted, the screen displays the message " Chat data successfully deleted ".
Video instructions on deleting conversations that take up large space on Zalo
Wishing you success!
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.