Petar Popara wrote:
I'm looking in base64.h file and I have a doubt. Other crypto libraries
( like OpenSSL ) usually have decode() ( or encode() ) func which allows
data to be added by calling this func several times and adding small peaces
of data and at the finish() should be called to retrive the result, but NSS
doesn't seem to work this way?
(Caveat: I don't know either library, but this
sounds like a general api style question!)
IMO, it makes sense for the caller to do
own buffering, as the feature of buffering
complicates both caller and callee without
any real advantage. So NSS looks like it
has it right. In security code there is a big
emphasis on reducing complexity. In my
book, the OpenSSL encode/decode method
would get labelled with "clean this up one
day."
--
News and views on what matters in finance+crypto:
http://financialcryptography.com/
_______________________________________________
mozilla-crypto mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-crypto
