summaryrefslogtreecommitdiffstats
path: root/net/third_party
Commit message (Collapse)AuthorAgeFilesLines
* net/third_party/nss: sync patches/ directory.agl@chromium.org2010-07-083-1/+129
| | | | | | | | | | | * Add a patch for r50960 (Cache the peer's intermediate CA certificates...) No code changes. TEST=none BUG=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51859 0039d316-1c4b-4281-b951-d872f2087c98
* Cache the peer's intermediate CA certificates in session ID, so thatwtc@chromium.org2010-06-283-0/+45
| | | | | | | | | | | | | | they're available when we resume a session. Right now when we resume a session, only the server certificate is available, so we may have an incomplete certificate chain. TBR=agl BUG=47181 TEST=no "certificate not trusted" error on the Mac after using Chrome for a long time. Review URL: http://codereview.chromium.org/2855025 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50960 0039d316-1c4b-4281-b951-d872f2087c98
* Add a unit test to check KeygenHandler's thread-safetydavidben@chromium.org2010-06-251-8/+14
| | | | | | | | | | | | We'll want some semblance of thread-safety when we make keygen asynchronous. R=wtc,mattm BUG=148 TEST=unit test Review URL: http://codereview.chromium.org/2838010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50903 0039d316-1c4b-4281-b951-d872f2087c98
* Change Windows' application/x-x509-user-cert handling to allow any ↵rsleevi@chromium.org2010-06-241-13/+0
| | | | | | | | | | | | certificate that has a private key, regardless of where it was generated, rather than restricting it to keys generated via <keygen> in the current browsing session. BUG=148 TEST=None R=wtc Review URL: http://codereview.chromium.org/2874002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50695 0039d316-1c4b-4281-b951-d872f2087c98
* Don't need to copy the challenge data before calling DER_Encode becausewtc@chromium.org2010-06-242-10/+8
| | | | | | | | | | | DER_Encode will copy it. Document the GenKeyAndSignChallenge function. R=mattm,davidben BUG=148 TEST=none Review URL: http://codereview.chromium.org/2866011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50682 0039d316-1c4b-4281-b951-d872f2087c98
* Move the Mozilla-derived code in net/base/keygen_handler_nss.ccwtc@chromium.org2010-06-184-0/+388
| | | | | | | | | | | | | to the new net/third_party/mozilla_security_manager directory. Fix nits. R=mattm,davidben BUG=148 TEST=none Review URL: http://codereview.chromium.org/2824014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50259 0039d316-1c4b-4281-b951-d872f2087c98
* Removed gssapi namespace.ahendrickson@google.com2010-06-102-20/+8
| | | | | | | | | BUG=33033. TEST=None. Review URL: http://codereview.chromium.org/2682006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49414 0039d316-1c4b-4281-b951-d872f2087c98
* Use SSLClientSocketNSS on Mac OS X. By default, chrome still useswtc@chromium.org2010-06-011-13/+18
| | | | | | | | | | | | | | | | | | SSLClientSocketMac. Specify the --use-nss-for-ssl command-line option to use SSLClientSocketNSS. The nss.gyp in src/net/third_party/nss is renamed ssl.gyp to avoid a naming conflict with the nss.gyp in src/third_party/nss. The GYP generator for Xcode project files disallows same-named .gyp files. SSL client authentication doesn't work yet. R=mark BUG=30689 TEST=No build and test failures on Mac and Windows. Review URL: http://codereview.chromium.org/2322008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@48650 0039d316-1c4b-4281-b951-d872f2087c98
* Adding gssapi.h to third_party.ahendrickson@google.com2010-05-184-0/+914
| | | | | | | | | | | Moved to net/third_party. BUG=None. TEST=None. Review URL: http://codereview.chromium.org/2011013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47563 0039d316-1c4b-4281-b951-d872f2087c98
* GYP changes for FreeBSD and OpenBSDpvalchev@google.com2010-05-141-2/+2
| | | | | | Review URL: http://codereview.chromium.org/1480002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47327 0039d316-1c4b-4281-b951-d872f2087c98
* Pass license check script for most of the tree.evan@chromium.org2010-03-192-0/+38
| | | | | | | | | | | | | Modified license-checker script to allow pruning directories we know to be ok. Still need to do a bit of third_party/* , as well as file a bunch of bugs on pieces where the licenses aren't clear, but I'm running out of energy. Review URL: http://codereview.chromium.org/1100003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42045 0039d316-1c4b-4281-b951-d872f2087c98
* ssl_SecureSend should not do handshake when the handshake wait state iswtc@chromium.org2010-03-163-62/+104
| | | | | | | | | | | wait_finished and we are false starting. R=agl BUG=38103 TEST=SSLClientSocketTest.Read_FullDuplex should not hang on Ubuntu Karmic. Review URL: http://codereview.chromium.org/850008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@41731 0039d316-1c4b-4281-b951-d872f2087c98
* NSS and NPN: send NextProtocol on resume and disable NPN without SPDY.agl@chromium.org2010-03-122-17/+40
| | | | | | | | | | | | | | | | | | | NPN on resume was broken symmetrically between OpenSSL and NSS (which is probably why we didn't notice for so long). OpenSSL wasn't expecting the message and NSS wasn't sending it. This change sends the NextProtocol message when resuming and disables NPN when not using SPDY. The reason for the latter is that we have GFEs deployed which don't expect NextProtocol when resuming and we have to wait some time before they get replaced. Because of this, we can't have NPN enabled by default. Instead, we'll use --host-resolver-rules to redirect everything to known-good GFEs in the mean time. http://codereview.chromium.org/841003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@41433 0039d316-1c4b-4281-b951-d872f2087c98
* SSL False Start Supportagl@chromium.org2010-03-029-3/+390
| | | | | | | | | | | | | | | | | | | | | | | | | * Adds TLS false start support. This allows us to start sending encrypted data before we have validated the server's Finished message. (This behaviour is already enabled on Android.) I've verified that this works using netem to add a 200ms delay on the loopback adaptor. I've also checked that an incorrect Finished message from the server causes an error by hacking the Go TLS server. Beware when looking at packet traces that the time taken in NSS's SQLite calls can exceed the RTT of the connection and make it appear that this code isn't functioning. * Adds DEBUG and TRACE defines to libssl when building Chromium in Debug mode. This means that setting SSLTRACE in the environment now works for debug builds. (Reland. First landed in r39905, reverted in r40024 because it uncovered a bug. Then landed in r40124 and reverted in r40126 because the faster SSL handshakes made a flake UI test worse. UI test fixed in r40285.) http://codereview.chromium.org/518065 BUG=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40438 0039d316-1c4b-4281-b951-d872f2087c98
* Send an empty renegotiation info extension instead of SCSVwtc@chromium.org2010-03-023-2/+36
| | | | | | | | | | | | | | | | unless TLS is disabled. This allows implementers of server side secure renegotiation to use Linux Chrome as a test client that sends empty renegotiation info extensions in initial handshakes. Rename README.google to README.chromium. R=agl BUG=none TEST=none Review URL: http://codereview.chromium.org/660233 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40337 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "Fix the case where the browser livelocks if we cannot open a file."agl@chromium.org2010-03-019-390/+3
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40291 0039d316-1c4b-4281-b951-d872f2087c98
* Fix the case where the browser livelocks if we cannot open a file.agl@chromium.org2010-02-269-3/+390
| | | | | | | | | | | | | | | | | | | | If one tries to upload a file that one doesn't have read access to, the browser livelocks. It tries to read from the file, gets nothing but spins forever because it knows that it hasn't finished reading. To address this, firstly we add a check at stat() time to make sure that we can read the file. However, this doesn't take care of the case where the access() call was incorrect, or the permissions have changed under us. In this case, we replace the missing file with NULs. (Land attempt three: first in r39446, reverted in r39448. Second in r39899, reverted in r39901.) http://codereview.chromium.org/541022 BUG=30850 TEST=Try to upload a file that isn't readable (i.e. /etc/shadow). The resulting upload should be a 0 byte file. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40146 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "SSL False Start Support"agl@chromium.org2010-02-269-390/+3
| | | | | | | (Again. Looks like it might have uncovered another issue but I'm about to go to lunch and I don't want to leave the tree red.) git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40126 0039d316-1c4b-4281-b951-d872f2087c98
* SSL False Start Supportagl@chromium.org2010-02-269-3/+390
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Adds TLS false start support. This allows us to start sending encrypted data before we have validated the server's Finished message. (This behaviour is already enabled on Android.) I've verified that this works using netem to add a 200ms delay on the loopback adaptor. I've also checked that an incorrect Finished message from the server causes an error by hacking the Go TLS server. Beware when looking at packet traces that the time taken in NSS's SQLite calls can exceed the RTT of the connection and make it appear that this code isn't functioning. * Adds DEBUG and TRACE defines to libssl when building Chromium in Debug mode. This means that setting SSLTRACE in the environment now works for debug builds. (Reland. First landed in r39905, reverted in r40024 because it uncovered a bug.) http://codereview.chromium.org/518065 BUG=none TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40124 0039d316-1c4b-4281-b951-d872f2087c98
* Revert "SSL False Start Support"agl@chromium.org2010-02-259-390/+3
| | | | git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40024 0039d316-1c4b-4281-b951-d872f2087c98
* SSL False Start Supportagl@chromium.org2010-02-249-3/+390
| | | | | | | | | | | | | | | | | | | | | | | | * Adds TLS false start support. This allows us to start sending encrypted data before we have validated the server's Finished message. (This behaviour is already enabled on Android.) I've verified that this works using netem to add a 200ms delay on the loopback adaptor. I've also checked that an incorrect Finished message from the server causes an error by hacking the Go TLS server. Beware when looking at packet traces that the time taken in NSS's SQLite calls can exceed the RTT of the connection and make it appear that this code isn't functioning. * Adds DEBUG and TRACE defines to libssl when building Chromium in Debug mode. This means that setting SSLTRACE in the environment now works for debug builds. http://codereview.chromium.org/518065 BUG=none TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39905 0039d316-1c4b-4281-b951-d872f2087c98
* net/third_party/nss: update to NSS_3_12_6_RC0agl@chromium.org2010-02-165-8/+26
| | | | | | | | | BUG=none TEST=none http://codereview.chromium.org/593089 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39123 0039d316-1c4b-4281-b951-d872f2087c98
* arm with its sysroot needs a new path to ../../../build/linux/pkg-config-wrapperfbarchard@chromium.org2010-02-161-1/+1
| | | | | | | | | BUG=35869 TEST=gclient runhooks --force should work for arm configurations of linux. Review URL: http://codereview.chromium.org/600144 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39110 0039d316-1c4b-4281-b951-d872f2087c98
* Update our copy of libssl from NSS CVS.agl@chromium.org2010-02-1119-315/+2167
| | | | | | | | http://codereview.chromium.org/596013 BUG=none TEST=none git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38773 0039d316-1c4b-4281-b951-d872f2087c98
* Port SSLClientSocketNSS to Windows. The next step is towtc@chromium.org2010-01-281-23/+55
| | | | | | | | | | | | | | | actually use it (controlled by a boolean flag in SSLConfig, which is controlled by a command-line switch). On Windows we still use CryptoAPI to verify and display certificates. SSL client authentication isn't supported yet. R=agl,mark BUG=28744 TEST=No build errors. Review URL: http://codereview.chromium.org/557027 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37427 0039d316-1c4b-4281-b951-d872f2087c98
* Remove a C99-ism that Visual C++ doesn't support -- declare a variable inwtc@chromium.org2010-01-271-1/+2
| | | | | | | | | | | the middle of a block. R=agl BUG=none TEST=no compilation error on Linux. Review URL: http://codereview.chromium.org/552178 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37270 0039d316-1c4b-4281-b951-d872f2087c98
* Fix libssl.so link failures on Linux shared lib build.mmoss@google.com2010-01-271-0/+6
| | | | | | | | | | | | http://build.chromium.org/buildbot/waterfall.fyi/builders/Chromium%20Linux%20Builder%20(dbg-shlib)/builds/6369/steps/compile/logs/stdio This has been broken for a long time, I think basically since Linux switched to use_system_ssl=0. Also fix a couple unrelated shared lib failures in media. Review URL: http://codereview.chromium.org/553097 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37256 0039d316-1c4b-4281-b951-d872f2087c98
* Remove the fallback Mozilla code for parsing FTP LIST response.phajdan.jr@chromium.org2010-01-205-2559/+0
| | | | | | | | | | | | | | | | | | The new parser seems to be compatible enough to do that. The Mozilla code was very helpful in the process of developing the new parser. Also add UI encouraging users to submit bug reports when we can't parse the listings, and an option to see the raw data sent by the server. This should allow us to fix remaining compatibility problems with very rare listing types or variations. When ?raw is found at the end of an FTP url and it is a directory listing, the parsing logic is bypassed and the data is displayed as-is with text/plain MIME type. TEST=none BUG=25520 Review URL: http://codereview.chromium.org/549053 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36632 0039d316-1c4b-4281-b951-d872f2087c98
* Clarify licenses on a bunch of files.evan@chromium.org2009-12-291-0/+36
| | | | | | | | | | | In this process, I also filed bugs on various projects we depend on that also have unclear licenses. BUG=28291 Review URL: http://codereview.chromium.org/521009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35323 0039d316-1c4b-4281-b951-d872f2087c98
* SSL: fix overflow error.agl@chromium.org2009-12-151-3/+3
| | | | | | | | | | | | In the previous code, the addition was performed as an unsigned char. This means that a value of 255 would wrap to 0 and throw us into a loop. BUG=none TEST=Have the server send an NPN extension with an element of length 255. http://codereview.chromium.org/500032 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34621 0039d316-1c4b-4281-b951-d872f2087c98
* Sync NSS to pickup https://bugzilla.mozilla.org/show_bug.cgi?id=531188agl@chromium.org2009-12-032-12/+18
| | | | | | | | This fixes decompression failures with some sites. R=wtc git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33625 0039d316-1c4b-4281-b951-d872f2087c98
* NSS: sync with CVS version.agl@chromium.org2009-12-015-44/+40
| | | | | | http://codereview.chromium.org/450021 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33383 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: add next-protocol-negotiation to libssl.agl@chromium.org2009-11-308-5/+293
| | | | | | | | | | | | This is an experimental, client only implementation of next-protocol-negotiation: http://www.imperialviolet.org/binary/draft-agl-tls-nextprotoneg-00.html This only affects the internal copy of libssl and is only active when built with use_system_ssl=0, which is not currently the default. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33327 0039d316-1c4b-4281-b951-d872f2087c98
* Sync ParseFTPList with Mozilla upstream.phajdan.jr@chromium.org2009-11-302-177/+193
| | | | | | | | | | | | | | | | Also fix chromium.patch so that it's possible to apply it. It turns out my editor removed whitespace from ParseFTPList.cpp anyway, and somehow the patch itself was corrupted. The plan is to remove this code after our own LIST parsing code is ready, but for now we still need it. TEST=none BUG=none Review URL: http://codereview.chromium.org/450008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33312 0039d316-1c4b-4281-b951-d872f2087c98
* Linux: enable building with a local version of libssl.agl@chromium.org2009-11-1753-0/+35136
| | | | | | http://codereview.chromium.org/394003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@32135 0039d316-1c4b-4281-b951-d872f2087c98
* Apply compatibility fixes for FTP LIST parsing code.phajdan.jr@chromium.org2009-09-222-2/+47
| | | | | | | | | TEST=none BUG=21770,21771 Review URL: http://codereview.chromium.org/214043 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26812 0039d316-1c4b-4281-b951-d872f2087c98
* Followup after http://codereview.chromium.org/201034 to correctly handle months.phajdan.jr@chromium.org2009-09-113-0/+16
| | | | | | | | | TEST=none BUG=none Review URL: http://codereview.chromium.org/199082 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26012 0039d316-1c4b-4281-b951-d872f2087c98
* Get the latest ParseFTPList code from Mozilla, and apply only the absolutelyphajdan.jr@chromium.org2009-09-104-1117/+2069
| | | | | | | | | | | | | required changes. This way future merging would be much easier. TEST=none BUG=none Review URL: http://codereview.chromium.org/201034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25878 0039d316-1c4b-4281-b951-d872f2087c98
* Move Mozilla FTP LIST response parsing code to net/third_party directory.phajdan.jr@chromium.org2009-09-013-0/+1530
This should make licensing terms and third-party origin of the code more clear. TEST=none BUG=none Review URL: http://codereview.chromium.org/179041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@25047 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-02 15:20:03 +0000