3980d4696059b0f92a181c127d9051176cc44872 |
|
09-Dec-2015 |
hbos <hbos@webrtc.org> |
RTCCertificate::Expires() and ::HasExpired() implemented using SSLCertificate::CertificateExpirationTime(). This is a re-upload of https://codereview.webrtc.org/1494103003 which was reverted and now re-landing. BUG=chromium:544894 Review URL: https://codereview.webrtc.org/1511753003 Cr-Commit-Position: refs/heads/master@{#10951}
/external/webrtc/webrtc/base/sslidentity.h
|
cd6f539a083f1c5ac4a548b73c03c444a813528d |
|
08-Dec-2015 |
hbos <hbos@webrtc.org> |
Revert of RTCCertificate::Expires() and ::HasExpired() implemented (patchset #5 id:140001 of https://codereview.webrtc.org/1494103003/ ) Reason for revert: RTCCertificate's expires_timestamp_ns was renamed to Expires but the old function is still used in one place in Chromium... https://uberchromegw.corp.google.com/i/chromium.webrtc.fyi/builders/Mac%20Builder/builds/7405 Original issue's description: > RTCCertificate::Expires() and ::HasExpired() implemented using SSLCertificate::CertificateExpirationTime(). > > NOPRESUBMIT=true > BUG=chromium:544894 > > Committed: https://crrev.com/20ef654174e245b3a06c9e9045bb97be9acd90cf > Cr-Commit-Position: refs/heads/master@{#10930} TBR=torbjorng@webrtc.org,hta@webrtc.org,kjellander@chromium.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=chromium:544894 Review URL: https://codereview.webrtc.org/1506883005 Cr-Commit-Position: refs/heads/master@{#10933}
/external/webrtc/webrtc/base/sslidentity.h
|
20ef654174e245b3a06c9e9045bb97be9acd90cf |
|
08-Dec-2015 |
hbos <hbos@webrtc.org> |
RTCCertificate::Expires() and ::HasExpired() implemented using SSLCertificate::CertificateExpirationTime(). NOPRESUBMIT=true BUG=chromium:544894 Review URL: https://codereview.webrtc.org/1494103003 Cr-Commit-Position: refs/heads/master@{#10930}
/external/webrtc/webrtc/base/sslidentity.h
|
46c9cc01901ecd3af0191872f9660b710d5fe757 |
|
01-Dec-2015 |
Torbjorn Granlund <torbjorng@google.com> |
Provide method for returning certificate expiration time stamp. We convert ASN1 time via std::tm to int64_t representing milliseconds-since-epoch. We do not use time_t since that cannot store milliseconds, and expires for 32-bit platforms in 2038 also for seconds. Conversion via std::tm might might seem silly, but actually doesn't add any complexity. One would expect tm -> seconds-since-epoch to already exist on the standard library. There is mktime, but it uses localtime (and sets an environment variable, and has the 2038 problem). The ASN1 TIME parsing is limited to what is required by RFC 5280. BUG=webrtc:5150 R=hbos@webrtc.org, nisse@webrtc.org, tommi@webrtc.org Review URL: https://codereview.webrtc.org/1468273004 . Cr-Commit-Position: refs/heads/master@{#10854}
/external/webrtc/webrtc/base/sslidentity.h
|
4e572470a3f181a043f9f9b98cc0153b7195b9f5 |
|
08-Oct-2015 |
torbjorng <torbjorng@webrtc.org> |
Provide RSA2048 as per RFC Original CL here: https://codereview.webrtc.org/1329493005 That CL is in patch set #1 of this CL. This CL resolves a method collision in Chrome. BUG=webrtc:4972 Review URL: https://codereview.webrtc.org/1394223002 Cr-Commit-Position: refs/heads/master@{#10222}
/external/webrtc/webrtc/base/sslidentity.h
|
335204c550e9570d356d0d6264475ac40c7f92f6 |
|
08-Oct-2015 |
torbjorng <torbjorng@webrtc.org> |
Revert of Provide RSA2048 as per RFC (patchset #9 id:200001 of https://codereview.webrtc.org/1329493005/ ) Reason for revert: Breaks chrome. Original issue's description: > provide RSA2048 as per RFC > > BUG=webrtc:4972 > > Committed: https://crrev.com/0df3eb03c9a6a8299d7e18c8c314ca58c2f0681e > Cr-Commit-Position: refs/heads/master@{#10209} TBR=hbos@webrtc.org,juberti@google.com,jbauch@webrtc.org,henrikg@webrtc.org NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:4972 Review URL: https://codereview.webrtc.org/1397703002 Cr-Commit-Position: refs/heads/master@{#10210}
/external/webrtc/webrtc/base/sslidentity.h
|
0df3eb03c9a6a8299d7e18c8c314ca58c2f0681e |
|
08-Oct-2015 |
torbjorng <torbjorng@webrtc.org> |
provide RSA2048 as per RFC BUG=webrtc:4972 Review URL: https://codereview.webrtc.org/1329493005 Cr-Commit-Position: refs/heads/master@{#10209}
/external/webrtc/webrtc/base/sslidentity.h
|
9b5476de9aa2326e7be10c251babe342c91f4a80 |
|
22-Sep-2015 |
Henrik Boström <hbos@webrtc.org> |
sslidentity.cc/IntKeyTypeFamilyToKeyType function added, converting from int to KeyType. Added to prevent Chromium from breaking if KeyType (now an enum) starts being used in Chromium before KeyType changes to a parameterizable class. When enum -> class change happens, IntKeyTypeFamilyToKeyType will be updated at the same time. Once Chromium starts using class KeyType with parameters this function can be removed. R=tommi@webrtc.org Review URL: https://codereview.webrtc.org/1363543002 . Cr-Commit-Position: refs/heads/master@{#10013}
/external/webrtc/webrtc/base/sslidentity.h
|
3c089d751ede283e21e186885eaf705c3257ccd2 |
|
16-Sep-2015 |
henrikg <henrikg@webrtc.org> |
Add RTC_ prefix to contructormagic macros. We must remove dependency on Chromium, i.e. we can't use Chromium's base/logging.h. That means we need to define these macros in WebRTC also when doing Chromium builds. And this causes redefinition. * DISALLOW_ASSIGN -> RTC_DISALLOW_ASSIGN * DISALLOW_COPY_AND_ASSIGN -> RTC_DISALLOW_COPY_AND_ASSIGN * DISALLOW_IMPLICIT_CONSTRUCTORS -> RTC_DISALLOW_IMPLICIT_CONSTRUCTORS Related CL: https://codereview.webrtc.org/1335923002/ BUG=chromium:468375 NOTRY=true Review URL: https://codereview.webrtc.org/1345433002 Cr-Commit-Position: refs/heads/master@{#9953}
/external/webrtc/webrtc/base/sslidentity.h
|
97579a4e122ad42592b5d7da9475e128da63a948 |
|
01-Sep-2015 |
glaznev <glaznev@webrtc.org> |
Add option to enable ECDSA key for Java API. Review URL: https://codereview.webrtc.org/1312293003 Cr-Commit-Position: refs/heads/master@{#9835}
/external/webrtc/webrtc/base/sslidentity.h
|
87713d0fe6fb9c86abe501bdf3d26ef4287ee617 |
|
25-Aug-2015 |
Henrik Boström <hbos@webrtc.org> |
RTCCertificates added to RTCConfiguration, used by WebRtcSession/-DescriptionFactory. This CL allows you to, having generated one or more RTCCertificates, supply them to RTCConfiguration for CreatePeerConnection use. This means an SSLIdentity does not have to be generated with a DtlsIdentityStore[Interface/Impl] as part of the CreatePeerConnection steps because the certificate contains all the necessary information. To create an RTCCertificate you have to do the identity generation yourself though. But you could reuse the same RTCCertificate for multiple connections. BUG=webrtc:4927 R=tommi@webrtc.org, torbjorng@webrtc.org Review URL: https://codereview.webrtc.org/1288033009 . Cr-Commit-Position: refs/heads/master@{#9774}
/external/webrtc/webrtc/base/sslidentity.h
|
b6d4ec418504fd947c6f96829c73180e9487e203 |
|
17-Aug-2015 |
Torbjorn Granlund <torbjorng@google.com> |
Support generation of EC keys using P256 curve and support ECDSA certs. This CL started life here: https://webrtc-codereview.appspot.com/51189004 BUG=webrtc:4685, webrtc:4686 R=hbos@webrtc.org, juberti@webrtc.org Review URL: https://codereview.webrtc.org/1189583002 . Cr-Commit-Position: refs/heads/master@{#9718}
/external/webrtc/webrtc/base/sslidentity.h
|
5e56c5927e097f095aef2e9f7be49fd3d59221e1 |
|
11-Aug-2015 |
Henrik Boström <hbos@webrtc.org> |
DtlsIdentityStoreInterface added and the implementation is called DtlsIdentityStoreImpl (previously named without the -Impl bit and without an interface). DtlsIdentityStoreImpl is updated to take KeyType into account, something which will be relevant after this CL lands: https://codereview.webrtc.org/1189583002 The DtlsIdentityService[Interface] classes are about to be removed (to be removed when Chromium no longer implements and uses the interface). This was an unnecessary layer of complexity. The FakeIdentityService is now instead a FakeDtlsIdentityStore. Where a service was previously passed around, a store is now passed around. Identity generation is now commonly performed using DtlsIdentityStoreInterface. Previously, if a service was not specified, WebRtcSessionDescriptionFactory could fall back on its own generation code. Now, a store has to be provided for generation to occur. For more information about the steps being taken to land this without breaking Chromium, see referenced bug. BUG=webrtc:4899 R=magjed@webrtc.org, tommi@webrtc.org Review URL: https://codereview.webrtc.org/1176383004 . Cr-Commit-Position: refs/heads/master@{#9696}
/external/webrtc/webrtc/base/sslidentity.h
|
5b4ce3391d60229342963ef524b7c1e359e5bfc4 |
|
05-Aug-2015 |
Henrik Boström <hbos@webrtc.org> |
DtlsIdentityStoreInterface added. New PeerConnectionFactoryInterface::CreatePeerConnection taking both service and store added (old CreatePC signature still exists). This is CL is part of an effort to land https://codereview.webrtc.org/1176383004 without breaking Chromium. See bug for more information. BUG=webrtc:4899 R=tommi@webrtc.org Review URL: https://codereview.webrtc.org/1268363002 . Cr-Commit-Position: refs/heads/master@{#9680}
/external/webrtc/webrtc/base/sslidentity.h
|
67186fe00cc68cbe03aa66d17fb4962458ca96d2 |
|
09-Mar-2015 |
kwiberg@webrtc.org <kwiberg@webrtc.org> |
Fix clang style warnings in webrtc/base Mostly this consists of marking functions with override when applicable, and moving function bodies from .h to .cc files. Not inlining virtual functions with simple bodies such as { return false; } strikes me as probably losing more in readability than we gain in binary size and compilation time, but I guess it's just like any other case where enabling a generally good warning forces us to write slightly worse code in a couple of places. BUG=163 R=kjellander@webrtc.org, tommi@webrtc.org Review URL: https://webrtc-codereview.appspot.com/47429004 Cr-Commit-Position: refs/heads/master@{#8656} git-svn-id: http://webrtc.googlecode.com/svn/trunk@8656 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/webrtc/base/sslidentity.h
|
f048872e915a3ee229044ec4bc541f6cbf9e4de1 |
|
13-May-2014 |
henrike@webrtc.org <henrike@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Adds a modified copy of talk/base to webrtc/base. It is the first step in migrating talk/base to webrtc/base. BUG=N/A R=niklas.enbom@webrtc.org Review URL: https://webrtc-codereview.appspot.com/17479005 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6129 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/webrtc/base/sslidentity.h
|
e9a604accd54ab14dbf98f99ccdcf3ae1c54d27c |
|
13-May-2014 |
perkj@webrtc.org <perkj@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Revert 6107 "Adds a modified copy of talk/base to webrtc/base. I..." This breaks Chromium FYI builds and prevent roll of webrtc/libjingle to Chrome. http://chromegw.corp.google.com/i/chromium.webrtc.fyi/builders/Win%20Builder/builds/457 > Adds a modified copy of talk/base to webrtc/base. It is the first step in migrating talk/base to webrtc/base. > > BUG=N/A > R=andrew@webrtc.org, wu@webrtc.org > > Review URL: https://webrtc-codereview.appspot.com/12199004 TBR=henrike@webrtc.org Review URL: https://webrtc-codereview.appspot.com/14479004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6116 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/webrtc/base/sslidentity.h
|
2c7d1b39b9374d2bc9bda4755fd4813db66a135c |
|
12-May-2014 |
henrike@webrtc.org <henrike@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> |
Adds a modified copy of talk/base to webrtc/base. It is the first step in migrating talk/base to webrtc/base. BUG=N/A R=andrew@webrtc.org, wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/12199004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@6107 4adac7df-926f-26a2-2b94-8c16560cd09d
/external/webrtc/webrtc/base/sslidentity.h
|