7%
03.01.2017
not to encrypt the running kernel. However, Tom replied that, absent being explicitly turned on, the encryption simply would not occur. He was fine with documenting a mem_encrypt=off option, though, if that would
7%
03.01.2017
who compromised your servers could simply fake the OSSEC agent to make the master think that everything was fine. OSSEC ensures security by generating keys on the master server that are then installed
7%
27.04.2018
a deranged Sherlock Holmes. Sometimes it will hear you and work fine for the first few commands and then suddenly give up on you. It's very frustrating, but it's likely that as usage of the assistant increases
7%
30.08.2018
that if part of his code turned out to be reusable for a yet-deeper subsystem in the future, he'd be fine with that. But for the moment, he said, his code met the needs of the situation.
Johan also added
7%
02.08.2017
to be useful on ARM, but may still be fine on other architectures.
On the other hand, there is a noticeable difference in compile speed, as a 5% slowdown compared to the previous release apparently
7%
13.09.2019
, the components, including the display, do not require more than 1A, so the 3A power supply I am using is fine (Figure 10).
Figure 10 - You do not have permission to view this object.
Outsmarting Standby
7%
31.05.2019
-kernel low memory killer had recently been removed from the kernel source tree in favor of a userspace low memory killer that he felt worked just fine.
But Sultan replied that in his opinion, the userspace
7%
26.11.2019
of the implementation is quite random. In many cases keeping things secret is fine from my point of view, given that it is a RoT [Root of Trust] after all. The secrecy is the core business here. So, this is why I opted
7%
11.06.2020
they couldn't change at runtime.
Kees Cook was fine with the patch, and Al Viro had some suggestions to regularize the calling conventions across all supported CPU architectures. The patch was originally
7%
05.03.2021
5.10 failed to boot on her organization's Intel Xeon CPU E7-8870 v4 @ 2.10GHz server. She added that Linux v5.9 and earlier worked fine. She posted some backtrace data to help diagnose the problem
