> On Tue, 2006-03-28 at 10:23 -0500, [EMAIL PROTECTED] wrote:
> > Well, that might be enough (though I can certainly write my own hex
> > encode/decode function) but why did I think they used part of
> > OpenSSL to accomplish base64 or md5 or something?
>
> There is code to handle MD5 checksums included within the Net-SNMP
> distribution. All other security-related processing (SHA checksums
> and assorted encryption) relies on OpenSSL.
>
> But the "encryption" of usernames can't rely on that library, since
> it needs to be available even when OpenSSL isn't installed.
Yeah, OK. But I know I'll have OpenSSL in my installation. And I can
see that OpenSSL includes an implentation of base64 (there's a
command-line tool to encode/decode files) but I can't find the likes of:
char* base64encode(char* dest, const char* src, size_t n)
which would be oh so useful. ;-)
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
