summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* regression.c: Added tests for UNTIL + COUNTrrule_until+countKen Murchison2019-06-061-0/+21
|
* icalrecur.c: Return a NULL string if RRULE contains both UNTIL and COUNTKen Murchison2019-06-061-0/+4
|
* Don't allow both COUNT and UNTIL in RRULEKen Murchison2019-05-262-1/+8
|
* Fix for issue #376Ken Murchison2019-05-183-0/+25
|
* Include invalid parameters in the maximum number of allowed parameters Fixes ↵Kent Sutherland2019-05-171-0/+1
| | | | hangs when iterating lots of invalid parameters (valid parameters already have a cap from f6c64896988644a7c6d4d5060f6ab574c2a62fbf) oss-fuzz issue 14809
* Change the icalarray wrapper and update the array.py testMilan Crha2019-05-162-47/+52
| | | | | | | | | | The libical's icalarray is not suitable for introspection much, because it operates on bare structures, thus rather not allow to add/get raw objects to/from it and let it be used for the timezone arrays only. The test itself could fail under libasan or a memory issue could be reported when it had been run under valgrind.
* Fix the implementation of the i_cal_value_decode_ical_string() wrapperMilan Crha2019-05-161-4/+4
| | | | | | The function should pass the buffer length including the nul-terminating character. Change also the 'encode' wrapper similarly.
* scripts/buildtests.sh - test more build option combinationsAllen Winter2019-05-151-0/+5
|
* ReleaseNotes.txt - final for release 3.0.5Allen Winter2019-05-141-10/+10
|
* src/libical/icalvalue.c,src/test/regression.c - fix an overrunMilan Crha2019-05-142-3/+49
| | | | in icalvalue_decode_ical_string(), with associated test
* Fix a use after freeKent Sutherland2019-05-131-0/+1
|
* Cap the number of parameters and properties to prevent unbounded memory ↵Kent Sutherland2019-05-131-2/+6
| | | | usage or hanging Alternate fix to #381.
* Revert "Set a maximum length per line before calling icalparser_add_line ↵Kent Sutherland2019-05-131-10/+1
| | | | | | This provides a hard limit on parsing to prevent unbounded memory usage or hanging when expanding parameters or properties. RFC 5545 says lines should not exceed 75 octets, so this still provides a pretty large buffer for files to be non-conformant and still parse successfully. oss-fuzz issue 14180, 14171, and 14591." This reverts commit 981f3dc6cdef0f140c048cb5de15c61a60a0cc6e.
* Revert "src/libical/icalparser.c - include <string.h>"Kent Sutherland2019-05-132-4/+2
| | | | This reverts commit 81554e81f2422b6d7902c15d9deff49fb6fe787b.
* Revert "libical/icalparser.c - another attempt to make Coverity happy"Allen Winter2019-05-121-0/+4
| | | | This reverts commit 562cce0fdc17fd68f2dd7711f2b737ecadf00892.
* ReleaseNotes.txt - mention defuzzAllen Winter2019-05-121-1/+2
|
* src/libical/icalparser.c - include <string.h>Allen Winter2019-05-122-2/+4
| | | | for strnlen()
* Set a maximum length per line before calling icalparser_add_line This ↵Kent Sutherland2019-05-121-1/+10
| | | | provides a hard limit on parsing to prevent unbounded memory usage or hanging when expanding parameters or properties. RFC 5545 says lines should not exceed 75 octets, so this still provides a pretty large buffer for files to be non-conformant and still parse successfully. oss-fuzz issue 14180, 14171, and 14591.
* Reset the parser level to 0 when encountering a line with END before BEGIN ↵Kent Sutherland2019-05-121-2/+9
| | | | Fixes memory leaks caused by the parser behaving incorrectly when the level is negative. oss-fuzz issue 14480, 14151, 14152, 14153, 14155.
* ReleaseNotes.txt - add dates for all the Version sectionsAllen Winter2019-05-111-17/+21
|
* .travis.yml - add a dist for xenialAllen Winter2019-05-111-0/+1
|
* set travis to use a more modern ubuntu (xenial)Allen Winter2019-05-112-5/+1
| | | | trusty is getting too old
* more travis changes trying to get it to find cmake 3.11Allen Winter2019-05-112-8/+4
|
* scripts/setup-travis.sh - install cmake 3.11.0Allen Winter2019-05-111-0/+4
|
* CMakeLists.txt - bump minimum cmake version to 3.11.0Allen Winter2019-05-113-2/+3
|
* ReleaseNotes.txt - updateAllen Winter2019-05-111-1/+2
|
* update zoneinfo to tzdata2019aAllen Winter2019-05-11593-1492/+1486
|
* improve testing for icalproperty_get_datetime_with_compoment()Milan Crha2019-05-114-11/+40
| | | | when using BUILTIN_TZDATA (and encountering the location fallback)
* Merge branch 'tintou/libical-glib-fixes'Allen Winter2019-05-0134-339/+330
|\
| * [libical-glib] Use libical-glib enums in the code and developer comments of ↵tintou/libical-glib-fixesMilan Crha2019-04-301-60/+60
| | | | | | | | i-cal-recurrence.xml
| * [libical-glib] Remove langbind as it is already covered by the introspection ↵Corentin Noël2019-04-303-84/+0
| | | | | | | | | | | | itself All the langbind methods are helpers for the bindings in libical, here the GObject Introspection already covers all the features.
| * [libical-glib] Respect the gobject naming conventionsCorentin Noël2019-04-3027-167/+203
| | | | | | | | | | | | | | Make sure that ICalFoo methods are prefixed i_cal_foo. Always start method name with `new' when it is a creation method. Clone method are not creation methods, remove the `new' prefix. Remove _r suffix of methods returning ical strings as it is already clear.
| * [libical-glib] Add annotations and delegates to the mime parserCorentin Noël2019-04-301-6/+15
| | | | | | | | Add documentation to the delegate and provide the right annotations.
| * [libical-glib] Add annotations and delegates to the parserCorentin Noël2019-04-301-15/+16
| | | | | | | | | | | | This allows bindings to fully use the method with user_data. i_cal_parser_string_line_generator is removed as it relies on internal structures. i_cal_parser_set_gen_data is removed as it is directly called by the wrappers.
| * [libical-glib] Add annotations for i_cal_memory_ functionsCorentin Noël2019-04-301-7/+7
| | | | | | | | Add array and array length annotations
| * [libical-glib] Allow to create ICalAttach from GBytesCorentin Noël2019-04-301-0/+18
| |
| * [libical-glib] Use metadata file for Vala bindingsCorentin Noël2019-04-302-0/+11
|/ | | | Covers the things that the introspection fails to cover
* icalproperty.c - use location as TZID fallback in ↵Allen Winter2019-04-283-0/+47
| | | | icalproperty_get_datetime_with_component
* cmake/modules/FindICU.cmake - fix a minor CMake warningAllen Winter2019-04-261-1/+1
|
* vcomponent_cxx.cpp - no need to check for NULL before 'delete'Allen Winter2019-04-261-3/+1
|
* Address some issues reported by static analyzers (Coverity Scan, clang)Milan Crha2019-04-263-16/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Error: REVERSE_INULL: src/libical-glib/i-cal-object.c:355: deref_ptr: Directly dereferencing pointer "iobject". src/libical-glib/i-cal-object.c:365: check_after_deref: Null-checking "iobject" suggests that it may be null, but it has already been dereferenced on all paths leading to the check. 363| 364| if (is_global_memory) { 365|-> if (iobject) { 366| GlobalData *gd; 367| ------------------------------------------------------------------ Error: ALLOC_FREE_MISMATCH: src/libical/vcomponent_cxx.cpp:922: alloc: Allocation of memory which must be freed using "operator delete". src/libical/vcomponent_cxx.cpp:922: assign: Assigning: "related_param" = "trigger_prop->get_first_parameter(icalparameter_kind const(ICAL_RELATED_PARAMETER))". src/libical/vcomponent_cxx.cpp:979: free: Calling "free" frees "related_param" using "free" but it should have been freed using "operator delete". 977| 978| if (related_param != NULL) { 979|-> free(related_param); 980| } 981| ------------------------------------------------------------------ Error: IDENTIFIER_TYPO: libical-3.0.5/src/python/Component.py:796: identifier_typo: Using "properites" appears to be a typo: * Identifier "properites" is only known to be referenced here, or in copies of this code. * Identifier "properties" is referenced elsewhere at least 18 times. src/python/Component.py:796: remediation: Should identifier "properites" be replaced by "properties"? src/python/Component.py:138: identifier_use: Example 2: Using identifier "properties". src/python/Component.py:674: identifier_use: Example 3: Using identifier "properties". src/python/test.py:274: identifier_use: Example 4: Using identifier "properties" (9 total uses in this function). src/python/test.py:393: identifier_use: Example 5: Using identifier "properties". 794| def duration(self, value=None): 795| if value != None: 796|-> due = self.properites('DUE') 797| for d in due: 798| self.remove_property(d) # Clear DUE properties Signed-off-by: Allen Winter <allen.winter@kdab.com>
* Mark ICalTimezone arguments in ICalTime as nullableMilan Crha2019-04-231-9/+9
| | | | | | | The ICalTime functions which use ICalTimezone can have the zone set to NULL, thus mark it as such in libical-glib as well. Signed-off-by: Allen Winter <allen.winter@kdab.com>
* various - doc for icalproperty_get_datetime_with_component()Allen Winter2019-04-204-3/+33
|
* no longer use or discuss LIBICAL_GLIB_UNSTABLE_APIAllen Winter2019-04-132-9/+0
| | | | the plan is for libical-glib to be stable in the 3.1 release
* [libical-glib] Add icalrecur_iterator_set_end() wrapper definitionMilan Crha2019-04-101-0/+6
|
* Merge branch 'tapkey-iterator-performance-next_year'Allen Winter2019-04-081-5/+4
|\
| * icalrecur.c - minor compile warning and coding styleAllen Winter2019-04-081-5/+4
| |
| * Merge branch 'iterator-performance-next_year' of ↵Allen Winter2019-04-081-2/+65
| |\ | | | | | | | | | https://github.com/tapkey/libical into tapkey-iterator-performance-next_year
* | | ReleaseNotes.txt - mention improved recurrence iterator performanceAllen Winter2019-04-081-0/+1
| | |
* | | Merge pull request #336 from tapkey/iterator-performance-next_yearAllen Winter2019-04-081-2/+65
|\ \ \ | |/ / |/| / | |/ Improve iterator performance by avoiding linear search