For users of Google Drive in particular or other online storage services , the protection of their data is extremely important. The following article will introduce you to an extremely effective tip to do this without the need for software or settings that are too sublime.
Disguised as Google Drive data can be understood that we will use the image, the format of another file to cover the original file to be protected. However, this way can cause a lot of trouble if you "disguise" too much and do not remember which file is the file to use.
Google Drive for iOS Google Drive for Android
Step 1: You access the homepage of Google Drive and then log into your Drive account.
Step 2 : At the main interface of this online storage service, navigate to the location or file that needs to be hidden. Then right-click on the file and select Manage versions - Manage versions .
Step 3 : New interface appears, left click on Upload new version - Upload the new version .
Step 4 : This is when we will select a new file to hide, hide the true image of the original file, select then click Open.
After the new file has been uploaded successfully, the Manage versions interface will automatically change, specifically:
Back to the main interface of your Google Drive account, you will see the file we selected first has now been replaced with a new image.
We can do this with many different file formats, from videos, photos, music to text files ...
Another interesting thing about this approach is that the original file and the file used as the cover are not required to have the same format or size.
You can even use the same image for different types of files. As in this example, the writer uses an image file ( * .jpg format ) to replace the default display image of the video file ( * .mp4 format ) and text file in PDF format .
Normally, Google will only support us to keep the original file hidden for about 30 days or 100 times to replace the disguised file. But we can change this by opening the Manage versions dialog, selecting the 3-dot icon corresponding to the original file and ticking the box Keep forever - Keep it permanent .
Using another file to hide the original file on Google Drive is an interesting and extremely handy feature that we need to know if we want to use Google Drive more effectively.
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.
