[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #17868 [Core Tor/Tor]: base64_decode_nopad() destination buffer length problem
#17868: base64_decode_nopad() destination buffer length problem
--------------------------+------------------------------------
Reporter: dgoulet | Owner: nikkolasg
Type: defect | Status: needs_revision
Priority: Medium | Milestone: Tor: 0.3.0.x-final
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: #19531 | Points: 2
Reviewer: dgoulet | Sponsor: SponsorR-can
--------------------------+------------------------------------
Comment (by nikkolasg):
I don't know what is your schedule for 030 but if possible I'd like to
continue working on it. As you say, I also think it's a good idea to make
the whole baseXX api uniform and I got ideas for it (uniform return type,
uniform argument types, etc).
Would that be more reasonable to create one big issue for the
uniformization of the baseXX api and then one sub-issue for each
base{16,32,64} ?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/17868#comment:32>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs