[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
carping about CARP
- Subject: carping about CARP
- From: davidianwalker at gmail.com (David Walker)
- Date: Fri, 30 Nov 2012 19:29:50 +1030
- In-reply-to: <[email protected]>
- References: <[email protected]>
On 30/11/2012, Robert E. Seastrom <rs at seastrom.com> wrote:
> [*] The OpenBSD side of the story can be read at
> Seems that there is a lesson to be learned here:
> "o hai, we wrote this software but can not be bothered to follow your
> process or formally write up the protocol, plz to be giving us a
> protocol number" ain't gonna fly.
This tells me pretty much everything I need to know about this:
Theo's comments in context here:
The article in question:
I recommend reading the comments.
>From where I stand, the OpenBSD project has been consistent on
insulating itself against future legal issues, no matter how remote,
with the idea that your security should not be restrained by anyone
other than you.
I believe that idea has legs regardless of practical considerations
and stands on it's own.
Besides, I won't discount OpenBSD out of hand for forging ahead,
withstanding practical issues, considering the runs they've got on the
board and the many facepalm fails we see in the diametrically opposed
It might be a very good thing they've bothered to take the time on this.