At 18:16 01.12.99 +0000, you wrote:
>On 30 Nov 1999 [EMAIL PROTECTED] wrote:
>
>> Geoff Thorpe <[EMAIL PROTECTED]> wrote:
>> > great. BIO_nprintf?
>
>The whole point had been that snprintf (and vsnprintf) don't exist on all
>platforms, they're GNU extensions. BIO_printf currently has a fixed 2k
>buffer (see crypto/bio/b_print.c) ... if we can obtain portable snprintf
>code then a buffer-safe BIO_??printf?? function could be introduced.
>Mallocing, freeing and remallocing is something many aren't happy to do -
>so I think an snprintf-style function (where you provide the buffer and
>buffer-size as arguments) would be preferable to an all-singing
>all-dancing dynamic BIO_printf that handles anything.
>
>But this would require a new function as the argument list would differ
>from BIO_printf.
At least we should fix BIO_printf() to truncate the data at the
end of the buffer...
By
Goetz
--
Goetz Babin-Ebell, TC TrustCenter GmbH, http://www.trustcenter.de
Sonninstr. 24-28, 20097 Hamburg, Germany
Tel.: +49-(0)40 80 80 26 -0, Fax: +49-(0)40 80 80 26 -126
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
