Bug#459804: heartbeat segfaults when using 65+ char authkey

2008-01-09 Thread Simon Horman
On Wed, Jan 09, 2008 at 11:49:58AM -, Rob Epping wrote: > Hi Simon, > > Due to restrictive SMTP settings on the host running heartbeat > the original sender was invalid. This is changed now in BTS. Thanks. > Simon Horman wrote: > > On Tue, Jan 08, 2008 at 08:05:28PM +, Systeem Beheerder

Bug#459804: heartbeat segfaults when using 65+ char authkey

2008-01-09 Thread Rob Epping
Hi Simon, Due to restrictive SMTP settings on the host running heartbeat the original sender was invalid. This is changed now in BTS. Simon Horman wrote: > On Tue, Jan 08, 2008 at 08:05:28PM +, Systeem Beheerder wrote: [SNIP] >> Marked important as I see some sting defined with length 64 in >

Bug#459804: heartbeat segfaults when using 65+ char authkey

2008-01-08 Thread Simon Horman
On Tue, Jan 08, 2008 at 08:05:28PM +, Systeem Beheerder wrote: > Package: heartbeat > Version: 1.2.5-3 > Severity: important > > from my authekeys > > 1 sha1 1234567890123456789012345678901234567890123456789012345678901234 > 2 sha1 1234567890123456789012345678901234567890123456789012345678901

Bug#459804: heartbeat segfaults when using 65+ char authkey

2008-01-08 Thread Systeem Beheerder
Package: heartbeat Version: 1.2.5-3 Severity: important from my authekeys 1 sha1 1234567890123456789012345678901234567890123456789012345678901234 2 sha1 12345678901234567890123456789012345678901234567890123456789012345 when using auth 2 I see this line in syslog kernel: heartbeat[4032]: