Hi Gustaf,
You're right. The kernel hardening features are set, including:
xdcpmer@harvesp-agah:~$ sudo dmesg | grep "Execute Disable"
[0.00] NX (Execute Disable) protection: active
This particular one appears to be at the BIOS level instead of sysctl.
And yet apache2 works.
There
Dear Ben
Not sure, what is going on these Google Cloud platforms.
With Ubuntu 18.04.4 LTS + Linux 5.3.0, i see no problems.
Maybe, some of the Kernel hardening parameters [1] are set?
-gn
$ uname -a
Linux cigoos 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 UTC
2020 x86_64
Hi,
With vTPM and monitoring turned off (and server rebooted), nsd still
doesn't boot due to same error for both ports and either a specific ip
number or 0.0.0.0.
I suspect this is some overzealous latent TPM/monitoring or related
permissions as I had a similar issue earlier this year
Hi,
Also, GCP says that vTPM and integrity monitoring options are enabled by
default, but that Secure Boot is not.[1]
1.
https://cloud.google.com/compute/docs/instances/modifying-shielded-vm#modify-shielded-vm-instance
I'm going to turn off vTPM, and see if that's enough to get nsd to
Hi,
NaviServer fails to bind on start up to port 8000 or 80 and a specific
ip number or as 0.0.0.0.
The errors are identical. See log snip below.
For diagnostic purposes, I tried apache2 on 80. It works with:
# systemctl start apache2
# systemctl start oacs-5-9-1
Job for oacs-5-9-1.service
