Date: Thu, 01 Jan 2015 16:13:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 196248] net/libsrtp: Upgrade to latest from GitHub Message-ID: <bug-196248-13-ZioxH4rP3p@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196248-13@https.bugs.freebsd.org/bugzilla/> References: <bug-196248-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196248 --- Comment #7 from Mikhail T. <mi@ALDAN.algebra.com> --- (In reply to Tijl Coosemans from comment #6) > I'd like to propose this alternate patch. It updates the port to version > 1.5.0 instead of using a development version. Considering the sort of "release-management" that GitHub seems to encourage, I doubt, using such a release ("version 1.5.0") will mean, what we usually mean by the term... Because nothing in our ports-tree is really using libsrtp at the moment, we don't need to worry (much) about "legacy" code. I'd say, we may as well offer a snapshot of the current master-branch of the project. > It also enables the use of some crypto functions from libcrypto (OpenSSL) which > eliminates the sha1_update function from the library so it no longer conflicts > with the same function from polarssl. So, we'll now have both OpenSSL and polarssl linked into libsrtp? If polarssl can not be easily replaced by OpenSSL (from base) completely, should we not use polarssl's implementation(s) of digests (like sha1) instead of -lcrypto's? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196248-13-ZioxH4rP3p>