Date: Tue, 9 Oct 2001 01:03:07 -0700 (PDT) From: "jon r. luini" <falcon@chime.com> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/31156: uuencode should pad with nulls instead of random garbage Message-ID: <200110090803.f99837F39888@abovenet.chime.com>
next in thread | raw e-mail | index | archive | help
>Number: 31156 >Category: bin >Synopsis: uuencode should pad with nulls instead of random garbage >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Oct 09 01:10:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: jon r. luini >Release: FreeBSD 4.4-RELEASE i386 >Organization: chime interactive >Environment: System: FreeBSD abovenet.chime.com 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Fri Sep 21 01:25:55 PDT 2001 falcon@newbie.chime.com:/usr/obj/usr/src/sys/CHIME i386 >Description: when uuencode's input is not a multiple of 4, garbage is used to pad it out, according to the doc. it's much more useful to pad with nulls since it provides consistent output when compared against another implementation. >How-To-Repeat: write your own version of uuencode which doesn't use un-initialized data and compare the output of both on an input data which isn't a multiple of 4 bytes in length. >Fix: clear the buffer before reading into it each iteration of the loop, or if you prefer, manually assign nulls only when necessary. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110090803.f99837F39888>