Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi. I'm jon.404, a Unix/Linux/Database/Openstack/Kubernetes Administrator, AWS/GCP/Azure Engineer, mathematics enthusiast, and amateur philosopher. This is where I rant about that which upsets me, laugh about that which amuses me, and jabber about that which holds my interest most: *nix.
Posted 01-13-2015 at 10:22 PM byrocket357 (Musings on technology, philosophy, and life in the corporate world)
Updated 01-14-2015 at 10:57 AM byrocket357
OpenBSD has had userland "W^X" (Write XOR Execute, a policy in which memory pages can be marked writable OR executable, but never both at the same time. This policy defeats attacks that rely on an executable stack or other write-then-execute arrangements).
Now OpenBSD has applied W^X to the kernel (amd64 thus far) as well, along with ASLR and a few other improvements.
Posted 01-09-2015 at 05:35 PM byrocket357 (Musings on technology, philosophy, and life in the corporate world)
Updated 01-09-2015 at 05:47 PM byrocket357(I can't English)
In a discussion on openbsd's tech@ mailing list, it was determined that ntpd-4.2.8 contained approximately 190k lines of code...a count that came up after the 8 vulnerabilities in ntpd were recently announced.
(DISCLAIMER: lines of code are difficult to count fairly, especially comparing one product to another, but this gives a rough "ballpark" idea of LOC).
Let's see if I can put this in perspective. ntpd checks and sets the time on a machine. In a nutshell,...
Posted 12-22-2014 at 12:13 AM byrocket357 (Musings on technology, philosophy, and life in the corporate world)
Updated 12-22-2014 at 12:42 AM byrocket357
I've run a tor relay over at Digital Ocean for a while now, and I finally decided to pull the plug on it. Digital Ocean announced up coming BSD support, and I waited with anticipation to see exactly how far they were willing to go with the BSDs...and let down that it was only FreeBSD support. (I've been running the tor node on Debian...not exactly ideal in my opinion, but it's been working well enough...I was really looking forward to switching the tor node over to OpenBSD...).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.