Update libsrtp to 1.5.2

Update libsrtp to 1.5.2
This CL updates libsrtp to 1.5.2 which includes the patches that were added
manually here before. This CL also adds the latest changes to improve
support for compiling on Windows which already landed upstream in libsrtp
commit 945eeee980e496ecad0f7df39c8033fe18983921. When this has landed,
the remaining issues as seen in CL 981593002 should be fixed and 
libsrtp should be fine to roll.

The libsrtp RNG through BoringSSL is disabled and the default RNG used
instead (as was with previous versions of libsrtp). This RNG is only
used during self-testing of libsrtp and BoringSSL can't be used inside
Chrome from WebRTC as that sandbox doesn't have access to "/dev/urandom"
as used by libsrtp.

BUG=328475
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=295151

[fancycode, 2015-04-20 22:11:36]

mail@joachim-bauch.de changed reviewers:
+ jiayl@chromium.org, juberti@chromium.org

[fancycode, 2015-04-20 22:13:03]

Sorry, I don't know how to create a CL from the SVN checkout as in
https://codereview.chromium.org/936663005/.

Could you please take a look? When this has landed, it should be fine to roll
into Chromium.

[jiayl, 2015-04-20 23:11:50]

On 2015/04/20 22:13:03, fancycode wrote:
> Sorry, I don't know how to create a CL from the SVN checkout as in
> https://codereview.chromium.org/936663005/.
> 
> Could you please take a look? When this has landed, it should be fine to roll
> into Chromium.

To create a CL from svn:

1. checkout the code using "gclient sync" with a .gclient file like this:
solutions = [
  {
    "managed": False,
    "name": "src",
    "url": "svn://svn.chromium.org/chrome/trunk/deps/third_party/libsrtp",
    "custom_deps": {},
    "deps_file": "DEPS",
    "safesync_url": "",
  },
]

2. make the changes, use "gcl change $NAME" to create a change
3. use "gcl upload $NAME" to upload to code review.

[fancycode, 2015-04-20 23:18:53]

On 2015/04/20 23:11:50, jiayl wrote:
> To create a CL from svn:
[...]

Thanks, but I don't have access to the SVN repository (I don't have a
@chromium.org account):

________ running 'svn checkout
svn://svn.chromium.org/chrome/trunk/deps/third_party/libsrtp
/my/path/to/libsrtp/src --non-interactive --ignore-externals' in
'/my/path/to/libsrtp'
svn: Can't get username or password

[fancycode, 2015-04-23 13:16:59]

On 2015/04/20 23:18:53, fancycode wrote:
> On 2015/04/20 23:11:50, jiayl wrote:
> > To create a CL from svn:
> [...]
> 
> Thanks, but I don't have access to the SVN repository (I don't have a
> @chromium.org account):
> 
> ________ running 'svn checkout
> svn://svn.chromium.org/chrome/trunk/deps/third_party/libsrtp
> /my/path/to/libsrtp/src --non-interactive --ignore-externals' in
> '/my/path/to/libsrtp'
> svn: Can't get username or password

Is there anything I can do to help with this?

[jiayl, 2015-04-23 15:44:54]

I think we can continue with this CL. I can help you submit once Justin
approves it.

On Thu, Apr 23, 2015 at 6:16 AM, <mail@joachim-bauch.de> wrote:

> On 2015/04/20 23:18:53, fancycode wrote:
>
>> On 2015/04/20 23:11:50, jiayl wrote:
>> > To create a CL from svn:
>> [...]
>>
>
>  Thanks, but I don't have access to the SVN repository (I don't have a
>> @chromium.org account):
>>
>
>  ________ running 'svn checkout
>> svn://svn.chromium.org/chrome/trunk/deps/third_party/libsrtp
>> /my/path/to/libsrtp/src --non-interactive --ignore-externals' in
>> '/my/path/to/libsrtp'
>> svn: Can't get username or password
>>
>
> Is there anything I can do to help with this?
>
> https://codereview.chromium.org/1098043003/
>

To unsubscribe from this group and stop receiving emails from it, send an email
to chromium-reviews+unsubscribe@chromium.org.

[fancycode, 2015-04-29 21:24:28]

Ping?

[juberti2, 2015-04-29 23:01:26]

On 2015/04/29 21:24:28, fancycode wrote:
> Ping?

lgtm

[jiayl, 2015-04-30 23:20:39]

jiayl@chromium.org changed reviewers:
+ kjellander@chromium.org

[jiayl, 2015-04-30 23:20:40]

I got 500 response when I tried to commit this.
Plus, I use gcl to create and land changes, but it's soon deprecated:
http://crbug.com/475321

[kjellander_chromium, 2015-05-06 12:40:16]

The CQ bit was checked by kjellander@chromium.org

[commit-bot: I haz the power, 2015-05-06 12:44:55]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-05-06 12:44:56]

Commit queue rejected this change because it did not recognize the base URL.
Please commit your change manually.

[kjellander_chromium, 2015-05-06 14:50:14]

On 2015/05/06 12:44:56, I haz the power (commit-bot) wrote:
> Commit queue rejected this change because it did not recognize the base URL.
> Please commit your change manually.

Hmm, CQ doesn't seem to work. 
Can you try again?

2 months ago you managed to submit https://codereview.chromium.org/936663005/
and I think gcl should still work.
If it doesn't, file a go/chromeinfraticket and point at this CL.

[jiayl, 2015-05-06 16:44:52]

On 2015/05/06 14:50:14, kjellander wrote:
> On 2015/05/06 12:44:56, I haz the power (commit-bot) wrote:
> > Commit queue rejected this change because it did not recognize the base URL.
> > Please commit your change manually.
> 
> Hmm, CQ doesn't seem to work. 
> Can you try again?
> 
> 2 months ago you managed to submit https://codereview.chromium.org/936663005/
> and I think gcl should still work.
> If it doesn't, file a go/chromeinfraticket and point at this CL.

OK, it worked this time.

Committed revision 295151.

[kjellander_chromium, 2015-05-07 08:39:33]

On 2015/05/06 16:44:52, jiayl wrote:
> On 2015/05/06 14:50:14, kjellander wrote:
> > On 2015/05/06 12:44:56, I haz the power (commit-bot) wrote:
> > > Commit queue rejected this change because it did not recognize the base
URL.
> > > Please commit your change manually.
> > 
> > Hmm, CQ doesn't seem to work. 
> > Can you try again?
> > 
> > 2 months ago you managed to submit
https://codereview.chromium.org/936663005/
> > and I think gcl should still work.
> > If it doesn't, file a go/chromeinfraticket and point at this CL.
> 
> OK, it worked this time.
> 
> Committed revision 295151.

Great. I added a "Committed:" message manually to this CL description and closed
it.