Fix handling of invalid certificates in JingleSessionManager.

remoting/protocol/jingle_session_manager.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include <limits>
 
 #include "remoting/protocol/jingle_session_manager.h"
 
 #include "base/base64.h"
 #include "base/message_loop.h"
@@ skipping 426 matching lines @@
     child = element->FirstNamed(QName(kChromotingXmlNamespace,
                                       kAuthenticationTag));
     if (child)
       child = child->FirstNamed(QName(kChromotingXmlNamespace,
                                       kCertificateTag));
 
     if (child) {
       std::string base64_cert = child->BodyText();
       std::string der_cert;
       bool ret = base::Base64Decode(base64_cert, &der_cert);
-      DCHECK(ret) << "Failed to decode certificate";
+      if (!ret) {
+        LOG(ERROR) << "Failed to decode certificate received from the peer.";
+        return false;
+      }
       certificate = net::X509Certificate::CreateFromBytes(der_cert.data(),
                                                           der_cert.length());
     }
 
     *content = new ContentDescription(config.release(), auth_token,
                                       certificate);
     return true;
   }
   LOG(ERROR) << "Invalid description: " << element->Str();
   return false;
@@ skipping 79 matching lines @@
     scoped_refptr<net::X509Certificate> certificate) {
   cricket::SessionDescription* desc = new cricket::SessionDescription();
   desc->AddContent(JingleSession::kChromotingContentName,
                    kChromotingXmlNamespace,
                    new ContentDescription(config, auth_token, certificate));
   return desc;
 }
 
 }  // namespace protocol
 }  // namespace remoting