/* * Copyright 2004 The WebRTC Project Authors. All rights reserved. * * Use of this source code is governed by a BSD-style license * that can be found in the LICENSE file in the root of the source * tree. An additional intellectual property rights grant can be found * in the file PATENTS. All contributing project authors may * be found in the AUTHORS file in the root of the source tree.
*/
#include"absl/memory/memory.h" #include"api/task_queue/pending_task_safety_flag.h" #include"rtc_base/checks.h" #include"rtc_base/crypto_random.h" #include"rtc_base/logging.h" #include"rtc_base/string_encode.h" #include"rtc_base/time_utils.h"// For TimeMillis
namespace cricket { using ::webrtc::SafeTask;
// RFC 5389 says SHOULD be 500ms. // For years, this was 100ms, but for networks that // experience moments of high RTT (such as 2G networks), this doesn't // work well. constint STUN_INITIAL_RTO = 250; // milliseconds
// The timeout doubles each retransmission, up to this many times // RFC 5389 says SHOULD retransmit 7 times. // This has been 8 for years (not sure why). constint STUN_MAX_RETRANSMISSIONS = 8; // Total sends: 9
// We also cap the doubling, even though the standard doesn't say to. // This has been 1.6 seconds for years, but for networks that // experience moments of high RTT (such as 2G networks), this doesn't // work well. constint STUN_MAX_RTO = 8000; // milliseconds, or 5 doublings
void StunRequestManager::FlushForTest(int msg_type) {
RTC_DCHECK_RUN_ON(thread_); for (constauto& [unused, request] : requests_) { if (msg_type == kAllRequestsForTest || msg_type == request->type()) { // Calling `Send` implies starting the send operation which may be posted // on a timer and be repeated on a timer until timeout. To make sure that // a call to `Send` doesn't conflict with a previously started `Send` // operation, we reset the `task_safety_` flag here, which has the effect // of canceling any outstanding tasks and prepare a new flag for // operations related to this call to `Send`.
request->ResetTasksForTest();
request->Send(webrtc::TimeDelta::Zero());
}
}
}
bool StunRequestManager::CheckResponse(StunMessage* msg) {
RTC_DCHECK_RUN_ON(thread_);
RequestMap::iterator iter = requests_.find(msg->transaction_id()); if (iter == requests_.end()) returnfalse;
StunRequest* request = iter->second.get();
// Now that we know the request, we can see if the response is // integrity-protected or not. Some requests explicitly disables // integrity checks using SetAuthenticationRequired. // TODO(chromium:1177125): Remove below! // And we suspect that for some tests, the message integrity is not set in the // request. Complain, and then don't check. bool skip_integrity_checking =
(request->msg()->integrity() == StunMessage::IntegrityStatus::kNotSet); if (!request->AuthenticationRequired()) { // This is a STUN_BINDING to from stun_port.cc or // the initial (unauthenticated) TURN_ALLOCATE_REQUEST.
} elseif (skip_integrity_checking) { // TODO(chromium:1177125): Remove below! // This indicates lazy test writing (not adding integrity attribute). // Complain, but only in debug mode (while developing).
RTC_LOG(LS_ERROR)
<< "CheckResponse called on a passwordless request. Fix test!";
RTC_DCHECK(false)
<< "CheckResponse called on a passwordless request. Fix test!";
} else { if (msg->integrity() == StunMessage::IntegrityStatus::kNotSet) { // Checking status for the first time. Normal.
msg->ValidateMessageIntegrity(request->msg()->password());
} elseif (msg->integrity() == StunMessage::IntegrityStatus::kIntegrityOk &&
msg->password() == request->msg()->password()) { // Status is already checked, with the same password. This is the case // we would want to see happen.
} elseif (msg->integrity() ==
StunMessage::IntegrityStatus::kIntegrityBad) { // This indicates that the original check had the wrong password. // Bad design, needs revisiting. // TODO(crbug.com/1177125): Fix this.
msg->RevalidateMessageIntegrity(request->msg()->password());
} else {
RTC_CHECK_NOTREACHED();
}
}
if (!msg->GetNonComprehendedAttributes().empty()) { // If a response contains unknown comprehension-required attributes, it's // simply discarded and the transaction is considered failed. See RFC5389 // sections 7.3.3 and 7.3.4.
RTC_LOG(LS_ERROR) << ": Discarding response due to unknown " "comprehension-required attribute.";
requests_.erase(iter); returnfalse;
} elseif (msg->type() == GetStunSuccessResponseType(request->type())) { if (!msg->IntegrityOk() && !skip_integrity_checking) { returnfalse;
} // Erase element from hash before calling callback. This ensures // that the callback can modify the StunRequestManager any way it // sees fit.
std::unique_ptr<StunRequest> owned_request = std::move(iter->second);
requests_.erase(iter);
owned_request->OnResponse(msg); returntrue;
} elseif (msg->type() == GetStunErrorResponseType(request->type())) { // Erase element from hash before calling callback. This ensures // that the callback can modify the StunRequestManager any way it // sees fit.
std::unique_ptr<StunRequest> owned_request = std::move(iter->second);
requests_.erase(iter);
owned_request->OnErrorResponse(msg); returntrue;
} else {
RTC_LOG(LS_ERROR) << "Received response with wrong type: " << msg->type()
<< " (expecting "
<< GetStunSuccessResponseType(request->type()) << ")"; returnfalse;
}
}
bool StunRequestManager::CheckResponse(constchar* data, size_t size) {
RTC_DCHECK_RUN_ON(thread_); // Check the appropriate bytes of the stream to see if they match the // transaction ID of a response we are expecting.
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung und die Messung sind noch experimentell.