Home
Welcome to the LibSrtp Project Wiki! This wiki aims at documenting and defining the development process and status of the LibSrtp Project
Up to date documentation for the libSRPT library is available either in README.md or a html version, including API documentation, can be generated in the doc/html folder with make libsrtp2doc.
The current released version of libsrtp is 2.5.0 . The 1.6 version of libsrtp is effectively frozen with only major security fixes or bugs going in to the 1_5_x_throttle. The expectation is for users of libsrtp to move to the most recent 2.x release.
For details regarding what is included in each release see the CHANGES file in the libsrtp repo.
The following links can be used to download latest stable release.
This provides a brief overview of the development process for the LibSrtp Project. There is only one active branch/version and that is the master branch. Code committed to the master branch will be used in the next major/minor release, at which point the focus of the will shift to the next release.
There are two libSRTP mailing list.
- libsrtp@lists.packetizer.com for general news / announcements / discussions. This is an open list, see https://lists.packetizer.com/mailman/listinfo/libsrtp for singing up.
- libsrtp-security@lists.packetizer.com for disclosing security issues to the libsrtp maintenance team. This is a closed list but anyone can send to it.
...
...
- Ensure that CHANGES file has been updated
- Edit CHANGES and configure.ac to contain the correct release number
[2.1.3], ie remove the-pre. - Generate configure script with new version:
autoreconf -ivf - Commit both modified files, this is now the release commit.
- Tag this commit with a release tag:
git tag v2.1.3 - Increment the version number in CHNAGES and configure.ac, append
-pre[2.1.4-pre] - Generate configure script with new version:
autoreconf -ivf - Increment the version number in CMakeLists.txt
- Commit modified files.
- Push commits to branch.
- Push release tag
git push origin tag v2.1.3 - Update release tags.
- Create new release in github https://github.com/cisco/libsrtp/releases/new .
The commit that is meant to be used for the release should be tag with vX.Y.Z, afterwards the major and minor release tags should be updated.
The major and minor release tags can be update from the command line with:
git tag v2 v2.1.3 -f
git push origin tag v2 -f
git tag v2.1 v2.1.3 -f
git push origin tag v2.1 -f
The Following branches are "actively" maintained by libsrtp project.
Main branch for all development and security/bug fixes.
Security and patch releases for version 1.6