Hi,
As i know machine allowed 10 messages in 5 seconds as configured in the
/proc/sys/kernel/printk_ratelimit and
/proc/sys/kernel/printk_ratelimit_burst files.
But my question is why this logging crosses 10 messages in 5 seconds and in
which case it will happen.
And why normally kernel will
Thanks for the answers,
I am going to change BIO_write to BIO_printf in my product for openssl.
And finally one question, NULL terminator is surely within the 128 bytes of
buffer?
regards,
Gopi.
--
View this message in context:
And a small understanding.
We are supplying buffer is about to 128 bytes to fill the converted message,
So, if the obj(ASN1_OBJECT) size is more than that(supplied buffer) size
OBJ_obj2txt will do truncate and will return the obj(ASN1_OBJECT) message
length. It results in more than 128(returned
is
returned*.
Matthias Apitz-4 wrote
> El día Thursday, September 15, 2016 a las 09:00:07PM -0700, sivagopiraju
> escribió:
>
>> - int len = OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
>> -BIO_write(bio, obj_txt, len);
>> -BIO_write(bio, "\n", 1);
>&g
- int len = OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
-BIO_write(bio, obj_txt, len);
-BIO_write(bio, "\n", 1);
+OBJ_obj2txt(obj_txt, sizeof(obj_txt), obj, 0);
+BIO_printf(bio, "%s\n", obj_txt);
Here, used BIO_printf instead of BIO_write, is it solve the issue?
Can you
I can't upgrade at this stage for my product, So can you give me the fix if
you have.
--
View this message in context:
http://openssl.6102.n7.nabble.com/CVE-2016-2180-tp67815p68371.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
--
openssl-users mailing list
To
I am using openssl-1.0.0e in my product. Here i want to know that OpenSSL is
CVE-2016-2180 vulnerable or not.
https://github.com/openssl/openssl/commit/0ed26acce328ec16a3aa635f1ca37365e8c7403a?diff=unified
In this page showing some information about CVE-2016-2180 vulnerability.
Actually i read
