Live data from Hacker News

Welcome to OpenBSD [pdf]

devio.us

31–40 of 45 posts

Re: Welcome to OpenBSD [pdf]

#31
post #4

Slightly off topic, but does anybody know why the OpenBSD community has started using Comic Sans in all their material? Is it some kind of inside joke? I don't find it neither good nor wrong, but there must be some reason behind it.

All the wannabes on reddit end up getting derailed into long comment chains circlejerking about comic sans; shunts a lot of people who have nothing worthwhile to say into an easy-to-avoid thread.

Re: Welcome to OpenBSD [pdf]

#32
post #20

> Random PIDs > Eliminates race conditions > Say you have a root daemon that forks then the child drops privileges. If you can beat the child you can inherit root privileges Can someone explain this? I don't see what this has to do with the randomness of pids.

Something like after the parent forks, the child opens a file called "/tmp/log.$$" with its PID in the name as root. If you can guess the PID of the child, you could create a link with that name, pointing at a file of your choice that is owned by root, such as "/etc/passwd". Then, you need to make the child do something predictable to that file, such as ensuring that the user supplied data being logged contains text…

Predictable file names in tmp is considered a security issue pretty much everywhere (hence mkstemp), so I would guess that's not what they mean.

Re: Welcome to OpenBSD [pdf]

#34

Theo's opinion notwithstanding, what's the best virtualization platform to run OpenBSD? There's a project to improve AWS/Xen support, http://www.joelroberts.org/openbsd/

Works fine in VMware ESX and HyperV. Need to run NTP though to combat clock drift. Not tried it on Xen but it has drivers for virtual NICs and storage etc.

Re: Welcome to OpenBSD [pdf]

#35

you are my hero, not just for all the awesome OpenBSD contributions and dedication but for the fact that you still maintain a GOPHER protocol'd site! gopher://gopher.anthrobsd.net/

I still love Gopher. Its for people who give a shit about the content and structure, not oodles of CSS and JS cack wrapped around four square inches of content that looks like my teenage daughter fired up Word and set the font size to 18pt so she didn't have to write so much.

Re: Welcome to OpenBSD [pdf]

#36
post #7

Earlier quoted context omitted.

And if they didn't mention it others would be here complaining that NetBSD did it first and OpenBSD is just trying to take credit.

And they will copy UBC, uvm locks, WAPBL, device abstraction layer. Just diff their kernel source to 4.3BSD and compare how close they are still. Their kernel is still stuck in the 80s.

I was born in the 80s. I'm not stuck there...

Re: Welcome to OpenBSD [pdf]

#37
post #25

"OpenBSD's OpenBGPD responsible for 30% of worldwide BGP communication" Ummm. Citation needed?

Yeah, that was my first thought, too.

In all my years in networking, I've ran exactly one instance of OpenBGPD and that's used simply for real-time updates of (anti-spam) blacklists and whitelists [0,1].

[0]: http://bgp-spamd.net/ [1]: http://www.openbsd.org/papers/asiabsdcon2013/phessler-bgp-sp...

Re: Welcome to OpenBSD [pdf]

#39

Theo's opinion notwithstanding, what's the best virtualization platform to run OpenBSD? There's a project to improve AWS/Xen support, http://www.joelroberts.org/openbsd/

If you watch the the ruBSD 2013 interview video with Theo de Raadt[1] at the 6:36, he states that they should take a shot at dealing with modern x86 VMs. That gives me quite a bit of hope along with the work on vmware related drivers in each release.

I use VMware at work, seems to do ok.

1) https://www.youtube.com/watch?v=OXS8ljif9b8

Re: Welcome to OpenBSD [pdf]

#40
> strlcat() and strlcpy() > - Solves the problem of unterminated C strings

Handling truncation correctly with those is just as much work as handling strcat and strcpy correctly. The only difference is that wrong handling of strcat and strcpy have worse effects usually.

Post reply on HN