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.
umurmur port progress
A few days ago I got umurmur up and running on OpenBSD. I sent the build patches in to the project developer and they were committed with minor edits. I've continued working on umurmur and I am closing in on submitting a port to OpenBSD.
I submitted three additional patches today to the umurmur project dev. The patches were to remove linker warnings (no, not all ports do that, but I will =) and now I've moved on to the finicky topic of security auditing. The baseline that I'm aiming for (for now, at least) is "no obvious security flaws" (this is, afterall, my first port and my first attempt at auditing C code (I have much more experience auditing php!)). Since the umurmur project is developed primarily with Linux in mind (isn't that quite often the case in OSS projects?), I have to be exceptionally careful to not break the build for Linux.
As I work my way through the security recommendations in the OpenBSD porting guide, I'm starting to see exactly how difficult security auditing C code can be. Sure, I'm getting a very minor taste of it right now (umurmur weighs in at a very tiny 78.3 KB)...but it's enough to put the OpenBSD project in perspective for me. These guys do some amazingly difficult work, and the track record shows exactly how much effort they put into this project. It blows my mind.
Anyways, I should be done with this port and have it submitted within the next few days (barring any overwhelming holiday festivities, of course).
I'm putting the murmur port on hold until David has a chance to go through my work and we can discuss where to pick up from there (submit a murmur port now and get mumble in later, or wait on both?)
Edit - As of today the umurmur port is "functional". It builds and creates an installable package of umurmur, but unfortunately the umurmur project doesn't include a built-in man page (and you can't get away with no man page on OpenBSD heh). Looks like I'll be learning how to write man pages before this gets submitted =)
I submitted three additional patches today to the umurmur project dev. The patches were to remove linker warnings (no, not all ports do that, but I will =) and now I've moved on to the finicky topic of security auditing. The baseline that I'm aiming for (for now, at least) is "no obvious security flaws" (this is, afterall, my first port and my first attempt at auditing C code (I have much more experience auditing php!)). Since the umurmur project is developed primarily with Linux in mind (isn't that quite often the case in OSS projects?), I have to be exceptionally careful to not break the build for Linux.
As I work my way through the security recommendations in the OpenBSD porting guide, I'm starting to see exactly how difficult security auditing C code can be. Sure, I'm getting a very minor taste of it right now (umurmur weighs in at a very tiny 78.3 KB)...but it's enough to put the OpenBSD project in perspective for me. These guys do some amazingly difficult work, and the track record shows exactly how much effort they put into this project. It blows my mind.
Anyways, I should be done with this port and have it submitted within the next few days (barring any overwhelming holiday festivities, of course).
I'm putting the murmur port on hold until David has a chance to go through my work and we can discuss where to pick up from there (submit a murmur port now and get mumble in later, or wait on both?)
Edit - As of today the umurmur port is "functional". It builds and creates an installable package of umurmur, but unfortunately the umurmur project doesn't include a built-in man page (and you can't get away with no man page on OpenBSD heh). Looks like I'll be learning how to write man pages before this gets submitted =)
Total Comments 0