#3804: HUGE_STRING is too short
--------------------------+----------------------
  Reporter:  richardp345  |      Owner:  mutt-dev
      Type:  defect       |     Status:  new
  Priority:  minor        |  Milestone:
 Component:  mutt         |    Version:  1.5.24
Resolution:               |   Keywords:
--------------------------+----------------------

Comment (by kevin8t8):

 Thanks for the bug report.  The header parsing code
 (mutt_read_rfc822_line) dynamically increases its buffer, but you should
 note that RFC 5321 and 5322 put limits on line length (1000) as well as
 email address sizes.

 The address parsing code is using fixed length buffers of LONG_STRING
 (1024), but this is well over the limits set by the RFCs.  Your sample msg
 file has both an illegal line length and an illegal email address.  So as
 long as we don't have a buffer overflow, I don't believe there is a bug
 for the msg part of this ticket.

 Now, the SASL authentication is definitely something we should fix.  I
 think rather than just bumping the size of HUGE_STRING we may want to
 dynamically allocate the buffer, since we basically know the size of what
 we need to return back (accounting for BASE64 encoding).

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3804#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent

Reply via email to