101–110 of 314 posts
Anyone here using OpenBSD? If so, for what purpose? I’ve always wanted to use NetBSD for an application for an embedded system / IoT device but never had the pleasure (yet!).
Anyone here using OpenBSD? If so, for what purpose? I’ve always wanted to use NetBSD for an application for an embedded system / IoT device but never had the pleasure (yet!).
I’ve been using it on an old PC Engines router (great hardware, by the way! I wish they were still around.) It ran for over 8 years without downtime, but I’ve had repeated problems in the last year or so. I used the default partitioning scheme, which makes /usr tiny, and /var huge, and since it is a router, did not install X11. At some point, they made x11 mandatory for auto updates. This is dumb, because all the upg…
My one complaint about OpenBSD would probably be lack of resizable partitions. You can expand them, but only if you have free contiguous space and most of the time one partition starts where the prior one ends. It's rarely a problem in practice, as only /home and /var and maybe /usr/local tend to be subject to any guesswork, but it can bite you from time to time as in your case.
Anyone here using OpenBSD? If so, for what purpose? I’ve always wanted to use NetBSD for an application for an embedded system / IoT device but never had the pleasure (yet!).
ang benchmarks against state of the art?
Anyone here using OpenBSD? If so, for what purpose? I’ve always wanted to use NetBSD for an application for an embedded system / IoT device but never had the pleasure (yet!).
We use OpenBSD for our VPSes on Hetzner, bare metal (for security focussed clients) and older (but still good) hardware in our Home Lab. OpenBSD is excellent on older (no longer supported by Cupertino) Apple hardware. We have an Intel Mac Mini Cluster with near-perfect uptime. If you need to run any kind of server (Web, Mail, DNS, NFS, Database) where you need stability & security, look no further. Some learning curv…
How do the various BSDs run on framework laptops?
Earlier quoted context omitted.
Your "evidence" for him to reconsider is a sandbox "bypass" that requires you to be root to set up the environment? For my next trick I will demonstrate how to break into my own house to open the blinds by using my keys. Security researcher theatrics will never not be funny.
Maybe I'm misunderstanding the video, but it looks to me as if the situation is: You are root inside a sandbox . As root-in-the-sandbox, you create a symlink and this gives you the ability to escape the sandbox. (Whether this is interesting or not depends on whether anyone actually tries to use the sandbox facility in such a way as to give root-in-the-sandbox privileges to untrusted people or code. I don't know enoug…
BSDs are interesting projects. As I understand it there's a broad difference of them all doing things reasonably well but a) Free is general-purpose, b) Net is especially portable/many architecture and Open is security focused
OpenBSD's primary purpose is to create artwork ( https://www.openbsd.org/artwork.html ), releasing an OS is a side project.
Earlier quoted context omitted.
We use OpenBSD for our VPSes on Hetzner, bare metal (for security focussed clients) and older (but still good) hardware in our Home Lab. OpenBSD is excellent on older (no longer supported by Cupertino) Apple hardware. We have an Intel Mac Mini Cluster with near-perfect uptime. If you need to run any kind of server (Web, Mail, DNS, NFS, Database) where you need stability & security, look no further. Some learning curv…
Have you tried such Openbsd installations vs FreeBSD? I forget the differences between OpenBSD and FreeBSD, so forgive the naivety. (I think NetBSD is more for embedded stuff, and Ghost and Dragonfly are more for conventional desktop use-cases if i recall correctly.) I'm asking because i have not touched any BSD for over 2 decades...and I'm getting the itch to try some out...and was wondering if for server-type use c…
NetBSD is small and simple. It's a lot like an old-school UNIX. It makes a decent platform for small services. I run bind and dhcpd on a NetBSD machine. The source code is very pleasant to read. It uses the pkgsrc software repository. It's my preferred platform for writing POSIX code.
OpenBSD still carries much of the general feel of NetBSD and can fill a similar niche on a network, but the security focus stands out in their documentation, subprojects (OpenSSH, LibreSSL, OpenNTPD, etc.), APIs (see pledge(8)), and policies. It makes for a great firewall. I'd say it also requires the most know-how.
All of them have excellent documentation (especially compared to Linux distros) and the base system is developed alongside the kernel, giving you a very consistent experience compared to Linux distros where everything is developed in isolation. If you write C, it's worth keeping a BSD system around just for the manpages and to make sure you're not letting Linuxisms creep into your codebase.
With all the security issues constantly being uncovered in other Operating Systems - which will only accelerate with Ai - it’s time everyone considers OpenBSD. Their decades-long security-focus is second to none. We have fully converted from Ubuntu/Debian to OpenBSD. No looking back.
Is OpenBSD actually more secure than Linux? I have not been able to find any data to support this—only some vague opinions.