summaryrefslogtreecommitdiff
path: root/net/libzrtpcpp/Makefile
AgeCommit message (Collapse)AuthorFilesLines
2022-11-23massive revision bump after textproc/icu updateadam1-2/+2
2022-10-26*: bump PKGREVISION for libunistring shlib major bumpwiz1-1/+2
2022-10-21Update libzrtpcpp to version 4.7.0nros1-13/+11
Pkgsrc changes: Github and pkglint fixes. Changes from NEWS: ## GNU ZRTP 4.6.6 ## Small fix in zrtp/crypto/zrtpDh.cpp to fix a small memory leak. ## GNU ZRTP 4.6.5 ## Cleanup compiler flags, reduce visibility for Android build, check some buffer length. No functional enhancements, no changes in API. ## GNU ZRTP 4.6.4 ## Some fixes to slience Windows C/C++ compiler, fix a few include statements when using openSSL, small fixes to check disclosure flag. Reset valid flags when adding a new cache record to avoid wrong security message. ## GNU ZRTP 4.6.3 ## A small fix inside the ZRTP main module to ignore malformed DH1 packets and avoid an NULL pointer access. ## GNU ZRTP 4.6.2 ## A small fix in the ZrtpCWrapper to fix an issue within 4.6.1 ;-) ## GNU ZRTP 4.6.1 ## A small fix in the ZrtpCWrapper to initialize and use the ZRTP master instance in case of multi-stream usage. Does not affect the main ZRTP usage, only projects that use the wrapper such as PJSIP or Gstreamer projects. These project should re-compile if they use the multi-stream feature. ## GNU ZRTP 4.6.0 ## Only a small add-on to the code to implement handling of the disclosure flag. See RFC6189, chapter 11 for more details about the disclosure flag. Because the API changed, thus it's necessary to recompile applications that use the new library version. ## GNU ZRTP 4.5.0 ## Added a new SAS algorithm 'B32E' that uses 32 Unicode Emoji code points instead of 32 ASCII characters. Application that are able to display Emojis may use this new SAS algorithm to display nice Emojis instead of 'boring' ASCII letters and digits. Some technical details: * the 32 selected emojis are easily distinguishable, known to everyone, not offending etc, and use standard Unicode code points * select colored emojis that look good on white and on black backgrounds (most emojis look good on white only) * select emojis that are available on iOS, Android, Mac OS X (Windows not checked) * the resulting SAS string is UTF-8 encoded, suitable for most platforms except Java. To use the codes for Java the application needs to translate the UTF-8 encoding into UTF-16 encoding. Because most of the emojis are Unicode supplementary characters the UTF-8 to UTF-16 conversion must generate the necessary UTF-16 surrogate pairs. To support the UTF-8 / UTF-16 conversion the common directory contains conversion functions that I extracted from ICU C/C++ library source. Because the API changed, thus it's necessary to recompile applications that use the new library version.
2022-04-18revbump for textproc/icu updateadam1-2/+2
2021-12-08revbump for icu and libffiadam1-2/+2
2021-09-29revbump for boost-libsadam1-2/+2
2021-04-21revbump for boost-libsadam1-2/+2
2021-04-21revbump for textproc/icuadam1-2/+2
2020-11-05*: Recursive revbump from textproc/icu-68.1ryoon1-2/+2
2020-06-02Revbump for icuadam1-2/+2
2020-05-22revbump after updating security/nettleadam1-2/+2
2020-04-12Recursive revision bump after textproc/icu updateadam1-2/+2
2020-03-08*: recursive bump for libffiwiz1-2/+2
2020-01-25*: Remove obsolete BUILDLINK_API_DEPENDS.openssl.jperkin1-3/+1
2020-01-18*: Recursive revision bump for openssl 1.1.1.jperkin1-2/+2
2019-07-20*: recursive bump for nettle 3.5.1wiz1-2/+2
2019-04-03Recursive revbump from textproc/icuryoon1-2/+2
2018-12-09revbump after updating textproc/icuadam1-2/+2
2018-07-20Recursive revbump from textproc/icu-62.1ryoon1-2/+2
2018-04-17Add p11-kit to gnutls/bl3.mk and bump dependencies.wiz1-2/+2
2018-04-14revbump after icu updateadam1-2/+2
2017-11-30Revbump after textproc/icu updateadam1-2/+2
2017-09-18revbump for requiring ICU 59.xmaya1-2/+2
2017-09-16Reset maintainerwiz1-2/+2
2017-08-16Comment out dead sites.wiz1-2/+2
2017-04-22Revbump after icu updateadam1-2/+2
2016-12-04Recursive revbump from textproc/icu 58.1ryoon1-2/+2
2016-09-19Recursive PKGREVISION bump for gnutls shlib major bump.wiz1-2/+2
2016-04-11Recursive revbump from textproc/icu 57.1ryoon1-2/+2
2016-03-05Bump PKGREVISION for security/openssl ABI bump.jperkin1-2/+2
2015-10-10Recursive revbump from textproc/icuryoon1-2/+2
2015-08-23Bump PKGREVISION for nettle shlib major bump.wiz1-1/+2
2015-04-18Add sqlite3 PKG_OPTION. USE_CMAKE instead of autotools. Update opensslrodent1-7/+11
dependency. Bump BUILDLINK_A{B,P}I* in buildlink3.mk due to API changes. From NEWS: == GNU ZRTP 4.4.0 == Changes the handling of HMAC and Hash contexts to avoild tool many malloc/free calls and thus memory pointer problems. Enhance the handling an check the nonce when using multi-stream mode. This required a modification to the class file and some modifications on the API. The old functions are now deprecated but still usable. Nevertheless you should change your application to use the new fuctions which support the new nonce handling and checks. Some bug fixing as well. == GNU ZRTP 4.3.1 == This is a bugfix release. It fixes several compiler issues in iOS8 Clang, Mircosoft C++ compiler (VS 2012) etc. This release also adds a fix to address a possible problem when using 'memset(...)' on a memory area immediately followed by a 'free(...)' call to free this memory area. Some compilers may otpimize the code and do not call 'memset(...)'. That's bad for software that deals with secure keys :-) . The fix removes this possible vulnerability. == GNU ZRTP 4.3.0 == This version adds some new API that provide to set retry timer values and to get some retry counters. Application may now set some values of the retry counters during the discovery (Hello) and the negotiation phase. Applications may increase the number of retries or modify the capping to support slow or bad networks. To get some idea about the actual number of retries during ZRTP negotiation an application may now use the new API to get an array of counters. The ZRTP state engine records how many retries occured during the different protocol states. Note: only the ZRTP initiator performs packet retries after the discovery (Hello) phase. The responder would always return zero alues for the other retry counters. Because we have a new set of functions the API changed, thus it's necessary to recompile applications that use the new library version. == GNU ZRTP 4.2.4 == Only small changes to enable Android X86 (see clients/tivi/android) as an example. Rename functions aes_init() to aes_init_zrtp() to avoid names clashes with other libreries that may include own AES modules. == GNU ZRTP 4.2.3 == The optional SAS relay feature (refer to RFC6189, chapter 7.3) is not longer compiled by default. If your project needs this support then modify the CMakeLists.txt file and uncomment a 'add_definition' statments. See comment in the CMakelists.txt file. The reasons to disable this optional feature in the default build: it's rarely used and some concerns about misusing this feature. == GNU ZRTP 4.2.2 == A small enhancement in SRTP handling to provide a longer bit-shift register with 128 bits. The replay now check accepts packets which are up to 127 sequence number behing the current packet. The upper layer (codecs) gets more packets on slower/bad networks that we may see on mobile 3G/4G connections. If the codecs do not remove silence then this may lead to some longer audio replay, similar to sattelite communication. == GNU ZRTP 4.2.1 == Bug fixes in the SRTP part that checks for replay and updates the ROC. The wrong computations lead to false replay indications and to wrong HMAC, thus they dropped to much packets, in particular under bad network conditions. Changed the handling the the zrtp_getSasType function the the ZrtpCWrapper. Please check the inline documentation and the compiler warning how to use the return value of the function.
2014-04-07Updated to latest release, 4.2.0. Shared library name change. From NEWS:rodent1-3/+3
Implemented a new function to read the ZID file if the ZID file backend is SQlite3. This is not a security problem because the ZRTP cache was always public and readable, refer to RFC6189. SQL statement returns all ZID records, sorted by date, newest on top. The function can then step thru the DB cursor and read the records. The version also include sevral fixes, usually compiler warnings, some small problems reported by 'cppcheck' analyser. Because we have a new set of functions the API changed, thus it's necessary to recompile applications that use the new library version.
2014-02-12Recursive PKGREVISION bump for OpenSSL API version bump.tron1-1/+2
2014-01-12Remove FETCH_USING, not a package-setable variable.wiz1-2/+1
2014-01-10Updated to latest release, 4.1.2. Resolves:rodent1-4/+8
http://secunia.com/advisories/53818/ From NEWS: == GNU ZRTP 4.1.1 == Is a bug fix release that fixes some problems when building a standalone version of the library, i.e. with embedded crypto algorithms and not using on openSSL. Another fix was necessary for NetBSD thread handling. == GNU ZRTP 4.1.0 == Small enhancements when dealing with non-NIST algorithms. An application may set a ''algorithm selection policy'' to control the selection behaviour. In addition the the standrad selection policy (as per RFC6189) this version provides a _non-NIST_ selection policy: if the selected public key algorithm is a non-NIST ECC algorithm then the other selection functions prefer non-NIST HASH algorithms (Skein etc). == GNU ZRTP 4.0.0 == For this version I added some new algorithms for the DH key agreement and the Skein Hash for ZRTP. Not further functional enhancments. Added a new (old) build parameter -DCORE_LIB that will build a ZRTP core library. This was available in V2.3 but I somehow lost this for 3.0 You may add other build parameters, such as SQLITE and CRYPTO_STANDALONE if you build the core library. == GNU ZRTP 3.2.0 == The main ZRTP modules contain fixes for three vulnerabilities found by Mark Dowd. Thus we advise application developers to use this version of the library. The vulnerabilities may lead to application crashes during ZRTP negotiation if an attacker sends prepared ZRTP packets. The fixes remove these attack vectors. Some small other enhancements and cleanup, mainly inside client code. Some enhancements in cache handling and the handling of retained shared secrets. This change was proposed by Phil, is a slight security enhacement and is fully backward comaptible. Because of some API changes clients must be compiled and linked with the new library. For details please refer to the Git logs. == GNU ZRTP 3.1.0 == This version adds some new features and code that supports some other client and this accounts for the most changes inside this release. The ZRTP core functionality was not changed as much (bug fixes, cleanup mainly) and remains fully backward compatible with older library versions. However, one nice enhancement was done: the addition of a standalone SDES support module. This module supports basic SDES only without the fancy stuff like many other SDES implementations. Thus it's pretty interoperable. Some other features are: - add some android support for a client, may serve as template for others - documentation and code cleanup Because of some API changes clients must be compiled and linked with the new library. == GNU ZRTP 3.0.0 == This is a major enhancement and restructuring of the overall ZRTP distribution. This was necessary because more and more other clients use ZRTP and add their specific glue code. Also some clients are not prepared to use openSSL or other crypto libraries to their code and distributions. Here a summary of the changes - a new directory layout to accomodate various clients - add standalone crypto modules, for example for AES, to have a real standalone ZRTP/SRTP library that does not require any other crypto library (optional via CMake configuration) - Re-structure ZRTP cache and add SQlite3 as optional storage backend The default settings for CMake build the normal ZRTP library that use openSSL as crypto backend, use the normal file based cache and include the GNU ccRTP modules. This is a librray that is to a large degree compatible with the earlier builds. Please refer to the top level CMakeFile.txt for options how to switch on the standalone crypto mode or the SQlite3 based cache storage.
2014-01-01Recursive PKGREVISION bump for libgcrypt-1.6.0 shlib major bump.wiz1-1/+2
2013-06-27Updated to latest release. No functional differences in pkgsrc files. Fromrodent1-2/+2
ChangeLog: 2.3.3: - fallback to gcrypt if no openssl elliptical support
2013-04-22Reduce included dependencies.rodent1-5/+1
2013-04-17Import libzrtpcpp-2.3.2 as net/libzrtpcpp.rodent1-0/+30
libzrtpcpp, a separate extension package to ccrtp, provides support for the ZRTP protocol (as defined in the Internet draft draft-zimmermann-avt-zrtp).
generated by cgit v1.2.3 (git 2.46.0) at 2026-07-11 08:55:59 +0000