- 10 2月, 2014 5 次提交
-
-
由 Noel Power 提交于
Signed-off-by: NNoel Power <noel.power@suse.com>
-
由 Noel Power 提交于
Signed-off-by: NNoel Power <noel.power@suse.com>
-
由 Noel Power 提交于
Signed-off-by: NNoel Power <noel.power@suse.com>
-
由 Noel Power 提交于
Signed-off-by: NNoel Power <noel.power@suse.com>
-
由 Noel Power 提交于
Instead of a size limit of ASCIILINESZ for multi-line input now there is no limit, a multi-line can be *any* size (and hence the key and value now also have a dynamic size) * there is a limit still on input line size (since multi lines are built from multiple lines where each line part is limited to ASCIILINESZ) Note: there is no limit to the size of the multi-line itself (it's only limited by available memory) * all stack & static fixed string usage has been removed with the exception of parsing line (or a multi-line portion) input, fgets still reads into a fixed string buffer of size ASCIILINESZ. Signed-off-by: NNoel Power <noel.power@suse.com>
-
- 23 1月, 2014 1 次提交
-
-
由 Noel Power 提交于
Instead of a size limit of ASCIILINESZ for multi-line input now there is no limit, a multi-line can be *any* size (and hence the key and value now also have a dynamic size) * there is a limit still on input line size (since multi lines are built from multiple lines where each line part is limited to ASCIILINESZ) Note: there is no limit to the size of the multi-line itself (it's only limited by available memory) * all stack & static fixed string usage has been removed with the exception of parsing line (or a multi-line portion) input, fgets still reads into a fixed string buffer of size ASCIILINESZ. Signed-off-by: NNoel Power <noel.power@suse.com>
-
- 10 1月, 2014 1 次提交
-
-
由 Andreas Schneider 提交于
If the key or value is bigger than 1024 we will end up in a buffer overflow. The overflow is caught by _FORTIFY_SOURCE, so it's definitely DoS-only. Curiously, because of ample space in the stack frame, it does not result in a crash without _FORTIFY_SOURCE in all cases. Signed-off-by: NAndreas Schneider <asn@samba.org>
-
- 22 8月, 2013 1 次提交
-
-
由 Christophe Tournery 提交于
Use the size_t data type where appropriate instead of casting.
-
- 21 8月, 2013 1 次提交
-
-
由 Christophe Tournery 提交于
-
- 24 5月, 2012 3 次提交
-
-
由 Robin Martinjak 提交于
using "foo = malloc(sizeof *foo)" is more change-friendly than "foo = malloc(sizeof (type*)"
-
由 Robin Martinjak 提交于
-
由 Robin Martinjak 提交于
-
- 22 5月, 2012 1 次提交
-
-
由 Christian Semmler 提交于
-
- 28 4月, 2012 1 次提交
-
-
由 Kevin Pyle 提交于
The documentation disclaims support for building with a C++ compiler, so it is reasonable to assume that the library will be built with a plain C compiler, so the functions will all have plain C linkage. By default, a C++ application that wished to use libiniparser would need to wrap the inclusion of libiniparser headers in 'extern "C" { ... }' to reflect the C linkage of libiniparser. Instead, place that marker directly in the libiniparser headers, so that client applications do not need to care. This has no effect on normal compilation of libiniparser, since the new markers are inside a '#ifdef __cplusplus' guard, and straight C compilers do not define __cplusplus.
-
- 08 4月, 2012 1 次提交
-
-
由 Nicolas D 提交于
-
- 04 4月, 2012 2 次提交
-
-
由 Andrey Mazo 提交于
-
由 Andrey Mazo 提交于
-
- 10 7月, 2011 1 次提交
-
-
由 James Spencer 提交于
-
- 09 7月, 2011 2 次提交
-
-
由 James Spencer 提交于
-
由 James Spencer 提交于
-
- 03 7月, 2011 1 次提交
-
-
由 James Spencer 提交于
g++ returns an error when a non-void pointer is set to be the return value from malloc.
-
- 04 4月, 2011 1 次提交
-
-
由 ndevilla 提交于
-
- 03 4月, 2011 1 次提交
-
-
由 Mathias Brossard 提交于
-
- 29 3月, 2011 1 次提交
-
-
由 ndevilla 提交于
-
- 03 3月, 2011 1 次提交
-
-
由 ndevilla 提交于
-
- 20 8月, 2010 1 次提交
-
-
由 Nicolas Devillard 提交于
-