* [9fans] encode(2)
@ 2012-02-03 2:33 erik quanstrom
0 siblings, 0 replies; only message in thread
From: erik quanstrom @ 2012-02-03 2:33 UTC (permalink / raw)
To: 9fans
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-02-03 2:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-02-03 2:33 [9fans] encode(2) erik quanstrom
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).