From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu,  2 Feb 2012 21:33:51 -0500
To: 9fans@9fans.net
Message-ID: <2f13a8740b55b506144767162e91b946@chula.quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] encode(2)
Topicbox-Message-UUID: 6270a91c-ead7-11e9-9d60-3106f5b1d025

as it turns out, encode(2) inaccurately describes the code.
dec64, enc64, dec16 and enc16 truncate rather than returning
errors.

does anybody have any reasons why truncated encodings should
be allowed?  i think this only allows for interesting attacks based
on truncated encodings, rather than being useful.  but i could
be wrong.

i'm currently testing these changes (there are a few calls to enc/dec64
that need correcting).

- erik