Re: [Mutt] #2033: buffer overflow in attachment decoding function

To: pvalchev@xxxxxxxxxxx, paul@xxxxxxxxxxxxxxxxxxxxx, brendan@xxxxxxxxxx, paul@xxxxxxxxxxxxxxx, pdmef@xxxxxxx
Subject: Re: [Mutt] #2033: buffer overflow in attachment decoding function
From: Mutt <fleas@xxxxxxxx>
Date: Mon, 21 Jul 2008 11:20:43 -0000
Cc: mutt-dev@xxxxxxxx
In-reply-to: <052.7aba4973f2a31f639131e91b3d70296f@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <052.7aba4973f2a31f639131e91b3d70296f@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#2033: buffer overflow in attachment decoding function

Comment (by pdmef):

 I can't reproduce a crash on debian and OS X with tip. Can you retry with
 tip? I get the above valgrind errors, too but to me they seem to originate
 in glibc and not from mutt.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2033#comment:6>

Prev by Date: Re: [Mutt] #3095: Alias command has no defined charset
Next by Date: [PATCH] noop cleanup: move mutt_copy_header flags to copy.h
Previous by thread: Re: [Mutt] #2033: buffer overflow in attachment decoding function
Next by thread: Re: [Mutt] #2033: buffer overflow in attachment decoding function
Index(es):
- Date
- Thread