Wireshark-bugs: [Wireshark-bugs] [Bug 2302] Base64 decoder returns incorrect length
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 26 Feb 2008 12:51:22 +0000 (GMT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2302





--- Comment #6 from Peter Kjellerstedt <pkj@xxxxxxxx>  2008-02-26 12:51:12 GMT ---
Actually, according to RFC 4648 section 3.3, one should reject the encoded data
if it contains anything but the alphabet characters and =. The referencing
document can make exceptions to this. In case of MIME (RFC 2045 section 6.8) it
allows for CR and LF, but recommends that other characters give a
warning/error. For RFC 3984 no exceptions are made. So I think it is better to
leave the while () statement as is, i.e., breaking the loop on the first
character outside the base64 alphabet plus CR and LF. This means we try to
decode as much as possible, but at the same time do not open up for strange
effects on weird data.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.