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, PDF-format documents are becoming quite popular and are used a lot more often. Therefore, there are quite a lot of software to support reading and converting this format (such as Foxit PDF Editor, Adobe Reader , Convert Word to Pdf ...). Even on Firefox and Chrome, there is a built-in automatic reading of this text.
Download the latest Firefox here
Download Firefox for iOS for free
Download Firefox for Android for free
However, it is not always good and helpful, depending on the purpose of each user, whether this is necessary or not. Therefore, in this article, Download.com.vn will guide you how to disable the automatic reading of PDF documents on popular browsers today.
Download Chrome for iOS for free
Download Chrome for Android for free
From the main interface of Chrome, you enter Chrome: // plugins / in the address bar and then Enter . In the list that appears below, find the Chrome PDF Viewer section and Disable it.

After disabling this plugin, Chrome's auto-reading of PDF files will be removed until we restart it.
Step 1: Also from the main interface of the browser, enter about: config in the address bar and then Enter . A warning appears, but there is no need to be too concerned about it, click I'll be careful, i promise - I'll be careful, I promise!
Step 2: A list of results appears as follows:
You continue to enter the keyword " pdfjs.disabled" in the Search box and Enter . There is only one result left, you can right- click on the row containing this value and then select Toggle to change the Value column from Fal to True.
Or you can double-click on the line to do so.
Do the opposite to enable this mode on Firefox. It is done!
From now on you can optionally adjust this automatic reading mode for your browser to get the best results when working.
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.