Likely because carp passwords are only there to protect from
misconfiguration, not to actually protect your network. The password
is used to create a (replayable) hash that all systems in the carp
cluster agree on. We'll consider the patch all the same as it's a
good idea :)
--Bill
On Nov 19, 2007 5:21 PM, RB <[EMAIL PROTECTED]> wrote:
> Yet again responding to myself. After having to quote my real
> passwords during the manual configuration (ones like
> 'HZHs8{-u5o_gnwE".k*o'), I suspected insufficient quoting in the
> automation. I read through interfaces.inc and found that the only
> sanitizing/quoting done is to remove spaces. Knowing that, using
> simple alphanumeric values resulted in the carpX interfaces being
> properly configured.
>
> I would call this a bug, but since it's been around since at least
> August 2006, it seems I might be the only person trying to configure
> strong CARP passwords. Attached is my [thoroughly untested] patch to
> induce a little better behavior.
>
>
> RB
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
