Date: Fri, 17 Apr 2009 13:34:17 +0300 From: xdsgrrr <xdsgrrr@consultcommerce.com> To: =?koi8-r?Q?=E1=CC=C5=CB=D3=C5=CA_?= =?koi8-r?Q?=E2=CC=C9=CE=CB=CF=D7?= <alexey.blinkov@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: MD5 authentication in quagga Message-ID: <1239964457.46223.2.camel@so1-ay279.globul.bg> In-Reply-To: <2d934d80904160052u70980215v1a32b07d4b1168f@mail.gmail.com> References: <2d934d80904150642r585049b4wadfdfc82a3d8c7fc@mail.gmail.com> <20090415144956.T15361@maildrop.int.zabbadoz.net> <2d934d80904150807p732bce43gc110fe6ae042507d@mail.gmail.com> <49E678E6.102@incunabulum.net> <2d934d80904160052u70980215v1a32b07d4b1168f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Its depends on what protocol you talking i use md5 auth for quagga ospfd for more than 5-6 years without problems you maybe talk about bgpd ? md5 peer auth ? On Thu, 2009-04-16 at 10:52 +0300, Алексей Блинков wrote: > 16 апреля 2009 г. 3:16 пользователь Bruce Simpson <bms@incunabulum.net> написал: > > Алексей Блинков wrote: > >> > >> If modelling ideal situation, then: > >> > >> md5 password doesn`t match or empty, then peering must be closed... > >> > >> Now md5 working only for outgoing packets, not for input. And peering > >> not closed if password miss or not match. because bsd not check > >> incoming packets, i think... > >> > > > > I thought someone had fixed this ages ago? > > I seem to remember someone had merged some changes to what I'd originally > > done for Sentex from NetBSD... but I could be wrong. > > > > cheers, > > BMS > > > > I don`t know about how kernel works with md5 hashing, because i`m > newly in bsd... > > > -- br, Atanas Yankov Network Engineer, IT Division CCIE # 21756 mobile: (+359 89) 8400734 e-mail: ayankov@globul.bg www.globul.bg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239964457.46223.2.camel>