- libsrtp - lists.packetizer.com

libSRTP version 2.6.0 has been released
by Pascal Bühler (pabuhler) 24 Feb '24

24 Feb '24

For more details please see the CHANGES file or got to https://github.com/cisco/libsrtp/releases/tag/v2.6.0 The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.6.0.tar.gz https://github.com/cisco/libsrtp/archive/v2.6.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Thank you to everybody that has contributed. Work as started in libSRTP v3, more details can be found at https://github.com/cisco/libsrtp/issues/669 . libSRTP team.

1 0

Question about AUTH_FAIL
by lmcdasi＠yahoo.com 25 Oct '23

25 Oct '23

Hi, I have a question regarding error code AUTH_FAIL during srtp_unprotect. I'm using gstreamer to send srtp audio packets and during transmission I do have a 'pause/resume functionality. At pause the gst-launch cmd is terminated. At resume the gst-launch is restarted but by having a new SSRC (which is a mistake), while the srtp key remains the same and the sequence number is higher than the last one. I'm using: AES_CM_128_HMAC_SHA1_32 Since the SSRC has changed, should't the srtp library return an AUTH_FAIL ? It does not complain that the SSRC has changed and I do not understand why. Thank you. BR,Dan S.

2 1

Q: libsrtp debug
by lmcdasi＠yahoo.com 19 Jun '23

19 Jun '23

I'm trying to use the library in java. I have wrote all jna mapping's required. When the code is executing create_session I'm getting SRTP_ERR_STATUS_BAD_PARAM I do not see where my error is & enabling logs in the library may help. Any suggestions ? Thx.

3 8

libSRTP version 2.5.0 has been release
by Pascal Buhler (pabuhler) 01 Feb '23

01 Feb '23

For more details please see the CHANGES file or view change log at https://github.com/cisco/libsrtp/compare/v2.4.0...v2.5.0 The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.5.0.tar.gz https://github.com/cisco/libsrtp/archive/v2.5.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Thank you to everybody that has contributed. libSRTP team.

1 0

libSRTP version 2.4.1 has been released
by Pascal Buhler (pabuhler) 09 Sep '21

09 Sep '21

This is a patch release containing the fix: "Use a full-length key even with null ciphers" This was both a compatibility and security issue, full details are available at https://github.com/cisco/libsrtp/pull/559 . The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.4.1.tar.gz https://github.com/cisco/libsrtp/archive/v2.4.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Thank you. libSRTP team.

1 0

libSRTP version 2.4.0 has been released
by Pascal Buhler (pabuhler) 13 Aug '21

13 Aug '21

Major changes in this release are: - Remove EKT files, this was never completed and the draft has since changed. - Adds support for Mbedtls as a crypto backend. - Support apple silicon build. - Adds support for the Meson build system. This is an alternative to Cmake and auto tools. For more details and a complete list of changes please see the CHANGES file. The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.4.0.tar.gz https://github.com/cisco/libsrtp/archive/v2.4.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Thank you to everybody that has contributed. libSRTP team.

1 0

Question about libsrtp's ECCN information.
by hikaru-kosakada＠sharp.co.jp 15 Oct '20

15 Oct '20

Dear support, I'm Hikaru Kosakada from SHARP corporation. We are currently developing an app using this libsrtp library, and getting ready to export our app. Could you tell me the ECCN information of libsrtp? (US ECCN number, Encryption Status, CCATS etc ...) Thank you. Kosakada

3 3

Modified payload encryption
by Hilman Fitriana 25 Jul '20

25 Jul '20

Hello, I run voip communication with srtp security where asterisk is the communication server and linphone is the endpoint. I tried to modify the encryption module to the payload only (enc_start) where the modifications I made caused the size of the encrypted payload to increase. When tested by communication, several packets are successfully sent from the sender to the receiver, but in the middle it causes an error. On the linphone, an error appears stating segmentation faults or sometimes bus errors. I think it happened because of the size of the memory that must be adjusted again. On the asterisk itself which utilizes the shared library of srtp, I can't find out whether it causes the same error or not because of the use of log files when compiling with the command: ./configure --with-log-file = "./ log.txt" causes asterisk forced to stop due to failure to load this srtp module. What I want to ask is, which part and how to reset the size of the payload? I am confused because the existing parameters are the result of casting from other parameters. Thanks, Hilman

2 1

libsrtp file as log
by Hilman Fitriana 20 Jul '20

20 Jul '20

Hello, I want to ask about the libsrtp log file. In the srtp.srtp.c code, there is one of the `debug_print (mod_srtp, .......) 'commands. Will it enter the file when we use the command ./configure --with-log-file? If yes, where is the location of the file? Thank you, Hilman

2 1

AES CM implementation in SRTP
by Hilman Fitriana 23 Jun '20

23 Jun '20

Hello. I want to ask about the implementation of the AES ICM method in the SRTP payload encryption process. In my understanding, the AES ICM encryption process works by doing `bitwise XOR` between the `keystream buffer` and the `buffer itself (plaintext)`. Keystream buffers are generated through the AES process with the input value of iv and the master key. Following is the implementation of the AES CM method in the srtp library. static srtp_err_status_t srtp_aes_icm_encrypt(void *cv,unsigned char *buf,unsigned int *enc_len){ srtp_aes_icm_ctx_t *c = (srtp_aes_icm_ctx_t *)cv; unsigned int bytes_to_encr = *enc_len; unsigned int i; uint32_t *b; printf("\nbuffer (plaintext)in hexa: %s \n",v128_hex_string(buf)); //............................................................. //pass /* now loop over entire 16-byte blocks of cast-iron */ for (i = 0; i < (bytes_to_encr / sizeof(v128_t)); i++) { /* fill buffer with new keystream */ srtp_aes_icm_advance(c); /* * add keystream into the data buffer (this would be a lot faster * if we could assume 32-bit alignment!) */ #if ALIGN_32 //............................................................. //pass #else if ((((uintptr_t)buf) & 0x03) != 0) { } else { printf("\nkeystream :%s\n",v128_hex_string(&c->keystream_buffer)); b = (uint32_t *)buf; *b++ ^= c->keystream_buffer.v32[0]; *b++ ^= c->keystream_buffer.v32[1]; *b++ ^= c->keystream_buffer.v32[2]; *b++ ^= c->keystream_buffer.v32[3]; buf = (uint8_t *)b; } #endif /* #if ALIGN_32 */ } //............................................................. //pass printf("\nbuffer after encrypt (ciphertext):%s\n",v128_hex_string(buff)); return srtp_err_status_ok; } I then tried to display the plaintext stored in buf as well as the keystream used for bitwise xor operations. However, when displaying ciphertext, it does not show the results of bitwise xor `plaintext` and `keystream`. Can anyone help me understand the code? Thank you

2 1

SRTP Payload
by Hilman Fitriana 07 Jun '20

07 Jun '20

Hello, I want to ask about the payload from SRTP. Here I use the 128-bit AES_CM encryption feature. What I want to ask is for every srtp_protect / srtp_protect_mki function call, does that represent an SRTP packet? Then in the srtp_protect_mki module, the srtp_encrypt function will be called which is related to the srtp_aes_icm_encrypt function. Then what I want to ask is what is the payload size which is the parameter of the function? Will selection of the AES_CM_128 bit feature affect the payload length of each SRTP packet? Thank you

1 0

libSRTP version 2.3.0 has been released
by Pascal Buhler (pabuhler) 23 Dec '19

23 Dec '19

Hi, Version 2.3.0 of libSRTP is now released from master. Major changes in this release are a fuzzer for libsrtp, NSS as optional crypto back end and cmake support for building. For more details and a complete list of changes please see the CHANGES file. The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.3.0.tar.gz https://github.com/cisco/libsrtp/archive/v2.3.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Thank you to everybody that has contributed. libSRTP team.

1 0

libsrtp version 2.2.0 hase been released
by Pascal Buhler (pabuhler) 16 May '18

16 May '18

Hi, Version 2.2.0 of libsrtp is now released from the 2_2_x_throttle, https://github.com/cisco/libsrtp/tree/2_2_x_throttle . The major change with this release is that the all the code has been reformatted to be consistent and this consistency can be enforced with the include .clang-format file. This resulted in a lot of none functional changes but was considered worth it to simplify maintenance in the future. There are numerous other minor fixes, see the CHANGES file for more details The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.2.0.tar.gz https://github.com/cisco/libsrtp/archive/v2.2.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Thank you to everybody that has contributed. libSRTP team.

1 0

libsrtp version 1.6.0 hase been released
by Pascal Buhler (pabuhler) 01 Aug '17

01 Aug '17

Version 1.6.0 of libsrtp has now been released. This release restores compatibility between version 1 and version 2.1.0 and later. >From this point 1.5.x is effectively EOL and there will be no more changes to 1_5_x_throttle. It is strongly recommended for people currently using a 1.5.x release to move to the 1.6.0 release if they are unable to move the 2.1.0 release. The 1_6_x_throttle will only receive important security fixes. Regards The libsrtp maintenance team.

1 0

Version 2.1.0 released
by Pascal Buhler (pabuhler) 15 Jun '17

15 Jun '17

Hi, Version 2.1.0 of libsrtp is now released from the 2_1_x_throttle, https://github.com/cisco/libsrtp/tree/2_1_x_throttle . Please read the CHANGES file or look at the git log to get an overview of what has changed since 2.0.0 . The following links are available for downloading: https://github.com/cisco/libsrtp/archive/v2.1.0.tar.gz https://github.com/cisco/libsrtp/archive/v2.1.tar.gz https://github.com/cisco/libsrtp/archive/v2.tar.gz Going forward we would like to make two new release in the short time. 1.6.0 release that addresses compatibility issues with the 2.1.0 release and a 2.2.0 release that will focus mostly on cleaning up the code repository with for example consistent formatting of the code as well as try to close as many of the open issues as possible. Thank you to everybody that has contributed. libSRTP team.

1 0

brancing for 2.1.0 release
by Pascal Buhler (pabuhler) 24 May '17

24 May '17

Hi A 2_1_x_throttle branch has been created, this will be the base for the 2.1.0 release. There are no outstanding issues blocking this release so if no new issues are found then the plan is to release 2.1.0 by 1st June. It would be greatly appreciated if people take the time to test out this release now! Especially related to various platform support. The 2.1.0 release contains several fixes that make it potentially incompatible with the current 1.5.x release. Due to this there will be an accompanying 1.6.0 release to ensure that there is compatibility between the 1.x series and the latest 2.x version for those that cannot migrate to 2.1.0 for any reason. Regards libsrtp team.

1 0

Soliciting feedback on new AES-GCM related bug found in libSRTP 1.5.4 & 2.0.0
by Pascal Buhler (pabuhler) 23 Feb '17

23 Feb '17

Hi, The following bug was recently reported on github https://github.com/cisco/libsrtp/issues/256, this bug relates to AES-GCM on little-endian system. Fixing this bug will cause some backward compatibility issues with existing libSRTP version, but not fixing is not really an option due to interop issues with other AES-GCM implementations as well as it being a potential security problem. Current plan is to fix as part of the upcoming 2.1.0 release and then simultaneously create patch release for 1.5.x. If this bug affects your usage of libSRTP and you would like to discuss how a fix is released then please reply to this mail at libsrtp(a)lists.packetizer.com<mailto:libsrtp@lists.packetizer.com> or else comment directly on the github issue. pascal

1 0

libSRTP project has moved, this mailer is retired!
by Pascal Buhler (pabuhler) 23 Feb '17

23 Feb '17

Hi, For those that do not know already the libSRTP project has completely moved from https://sourceforge.net/projects/srtp to https://github.com/cisco/libsrtp . As part of this move the mailer's hosted on sourceforge , srtp-development(a)lists.sourceforge.net<mailto:srtp-development@lists.sourceforge.net> & srtp-users(a)lists.sourceforge.net<mailto:srtp-users@lists.sourceforge.net> can no long be maintained and so are retiring. There is a new libsrtp mailer set up at libsrtp(a)lists.packetizer.com<mailto:libsrtp@lists.packetizer.com> for general news / announcements / discussions. This is an open list, to subscribe go to https://lists.packetizer.com/mailman/listinfo/libsrtp . Bets regards Pascal, on behalf of libSRTP maintenance team.

1 0