Other people can completely find your Zalo, if you know the phone number. So, if you do not want to reveal personal information, you can hide your phone number easily.
First, type your phone number into the search box, check if you find your Zalo. If you have not hidden your phone number, the name and phone number will be displayed as shown below:
At this time, follow the article below to hide your Zalo phone number, protect personal information from "prying eyes ":
Step 1: At the main interface of Zalo, click the 3 horizontal dots icon in the bottom right corner. Then click the Gear settings icon , then select Privacy.
Step 2: Next, click on Get friend requests from sources, then slide the slider in the Phone number to the left to turn off this feature is done.
Thus, from now on no one can search for you by phone number anymore. The implementation is quite simple, isn't it?
I wish you successful implementation!
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.
