Synchronize the release of the openEuler-22.03-LTS-SP1

0001-Include-some-information-about-supported-ciphers.patch

@@ -0,0 +1,39 @@
+From 46fb1a2c2dc91e1410d3e9043fd088158bed4c92 Mon Sep 17 00:00:00 2001
+From: Pascal Buhler <pabuhler@cisco.com>
+Date: Mon, 12 Dec 2022 01:22:47 +0100
+Subject: [PATCH] Include some information about supported ciphers
+
+Provide a little info on the consequence of configuring different crypto backends, as request in #620 .
+---
+ README.md | 10 ++++++++++
+ 1 file changed, 10 insertions(+)
+
+diff --git a/README.md b/README.md
+index 1e42a0b..22cda48 100644
+--- a/README.md
++++ b/README.md
+@@ -220,11 +220,21 @@ will want to read the Security Considerations section of [RFC 3711](https://tool
+ In addition, it is important that you read and understand the
+ terms outlined in the [License and Disclaimer](#license-and-disclaimer) section.
+ 
++This library also supports the AES-GCM Authenticated Encryption methods
++described in [RFC 7714](https://tools.ietf.org/html/rfc7714)
++
+ --------------------------------------------------------------------------------
+ 
+ <a name="implementation-notes"></a>
+ ## Implementation Notes
+ 
++  * It is possible to configure which 3rd party (ie openssl/nss/etc) crypto backend
++    libSRTP will be built with. If no 3rd party backend is set then libSRTP provides
++    an internal implementation of AES and Sha1. The internal implementation only
++    supports AES-128 & AES-256, so to use AES-192 or the AES-GCM group of ciphers a
++    3rd party crypto backend must be configured. For this and performance reasons it
++    is highly recommended to use a 3rd party crypto backend.
++  
+   * The `srtp_protect()` function assumes that the buffer holding the
+     rtp packet has enough storage allocated that the authentication
+     tag can be written to the end of that packet. If this assumption
+-- 
+2.42.0.windows.2
+

libsrtp.spec

@@ -1,6 +1,6 @@
 Name:           libsrtp
 Version:        2.4.2
-Release:        4
+Release:        6
 Summary:        Library for SRTP (Secure Realtime Transport Protocol)
 License:        BSD
 URL:            https://github.com/cisco/libsrtp
@@ -10,7 +10,8 @@ BuildRequires:  gcc
 
 Patch0001:      0001-cast-time_t-values-to-known-types-for-formatting-in-.patch
 Patch0002:      0002-Include-directory-should-point-to-include-not-to-inc.patch
-Patch0003:      0001-Export-CMake-Targets.patch
+Patch0003:      0001-Include-some-information-about-supported-ciphers.patch
+Patch0004:      0001-Export-CMake-Targets.patch
 
 %description
 This package provides an implementation of the Secure Real-time Transport Protocol (SRTP),
@@ -51,9 +52,15 @@ development of %{name}.
 %{_libdir}/*.so
 
 %changelog
-* Thu Feb 1 2024 liubo <liubo1@xfusion.com> - 2.4.2-4
+* Tue May 28 2024 yaoxin <yao_xin001@hoperun.com> - 2.4.2-6
+- Rebuild +1
+
+* Thu Feb 1 2024 liubo <liubo1@xfusion.com> - 2.4.2-5
 - Export CMake Targets
 
+* Wed Dec 27 2023 liubo <liubo1@xfusion.com> - 2.4.2-4
+- Include some information about supported ciphers
+
 * Wed Nov 22 2023 liubo <liubo1@xfusion.com> - 2.4.2-3
 - Include directory should point to 'include' not to 'include/srtp2'