LaurentBonnaud
LaurentBonnaud
Version 1.6.0 of zerotier regressed: ``` $ hardening-check /usr/sbin/zerotier-one /usr/sbin/zerotier-one: Position Independent Executable: no, normal executable! Stack protected: no, not found! Fortify Source functions: unknown, no protectable libc functions used...
Version 1.6.1 is back where version 1.4.x was: ``` $ hardening-check /usr/sbin/zerotier-one /usr/sbin/zerotier-one: Position Independent Executable: yes Stack protected: yes Fortify Source functions: no, only unprotected functions found! Read-only relocations:...
Here is for version 1.8.4: ``` $ hardening-check /usr/sbin/zerotier-one /usr/sbin/zerotier-one: Position Independent Executable: yes Stack protected: yes Fortify Source functions: no, only unprotected functions found! Read-only relocations: yes Immediate binding:...
The situation improved a lot with the latest package version for Ubuntu 22.04/jammy: ``` $ hardening-check /usr/sbin/zerotier-one /usr/sbin/zerotier-one: Position Independent Executable: yes Stack protected: yes Fortify Source functions: yes (some...
The problem still exists in version 1.6.0 of zerotier.
Yes it does. I get the same result on my systems. And restarting the service no longer causes the kernel to log this message: ``` # dmesg | grep zerotier...
Hi, this execstack problem still exists with the latest package version for Ubuntu 22.04/jammy: ``` Package: zerotier-one Version: 1.8.9 ```
Indeed, thanks for the tip! I now see this in about:support: `WebGL 1 Renderer Intel Open Source Technology Center -- Mesa DRI Intel(R) Sandybridge Mobile ` However I still see...
I tried to change the `layers.acceleration.force-enabled` setting to true, but I cannot. Changing some preferences in the UI does not work either.