| /external/webrtc/webrtc/libjingle/xmpp/ |
| D | xmppauth.cc | 45 const std::vector<std::string>& mechanisms, in ChooseBestSaslMechanism() argument
49 contains(mechanisms, buzz::AUTH_MECHANISM_OAUTH2)) { in ChooseBestSaslMechanism()
55 contains(mechanisms, buzz::AUTH_MECHANISM_GOOGLE_TOKEN)) { in ChooseBestSaslMechanism()
61 contains(mechanisms, buzz::AUTH_MECHANISM_GOOGLE_COOKIE)) { in ChooseBestSaslMechanism()
66 if (contains(mechanisms, buzz::AUTH_MECHANISM_PLAIN)) { in ChooseBestSaslMechanism()
|
| D | plainsaslhandler.h | 31 …virtual std::string ChooseBestSaslMechanism(const std::vector<std::string> & mechanisms, bool encr… in ChooseBestSaslMechanism() argument
37 …std::vector<std::string>::const_iterator it = std::find(mechanisms.begin(), mechanisms.end(), "PLA… in ChooseBestSaslMechanism()
38 if (it == mechanisms.end()) { in ChooseBestSaslMechanism()
|
| D | xmpplogintask.cc | 182 std::vector<std::string> mechanisms; in Advance() local
188 mechanisms.push_back(pelMech->BodyText()); in Advance()
192 std::string choice(pctx_->ChooseBestSaslMechanism(mechanisms, pctx_->IsEncrypted())); in Advance()
|
| D | saslhandler.h | 32 …virtual std::string ChooseBestSaslMechanism(const std::vector<std::string> & mechanisms, bool encr…
|
| D | xmppauth.h | 46 const std::vector<std::string>& mechanisms,
|
| D | xmppengineimpl.cc | 356 const std::vector<std::string>& mechanisms, bool encrypted) { in ChooseBestSaslMechanism() argument
357 return sasl_handler_->ChooseBestSaslMechanism(mechanisms, encrypted); in ChooseBestSaslMechanism()
|
| D | xmppengineimpl.h | 180 const std::vector<std::string>& mechanisms, bool encrypted);
|
| /external/e2fsprogs/debian/attic/ |
| D | comerrg-dev.menu | 6 have the problems identified with mechanisms commonly in use." \
|
| /external/libmojo/mojo/public/c/ |
| D | README.md | 14 not, and access to the IPC mechanisms must be via the primitives defined in this
|
| /external/autotest/test_suites/ |
| D | control.dummy_server | 16 so that we can test result gathering and reporting mechanisms.
|
| D | control.dummy | 16 so that we can test result gathering and reporting mechanisms.
|
| /external/wpa_supplicant_8/wpa_supplicant/doc/docbook/ |
| D | wpa_background.sgml | 51 <para>Keys can be managed using two different mechanisms. WPA can
55 "WPA-Personal", respectively. Both mechanisms will generate a
|
| /external/e2fsprogs/debian/attic/libs/ |
| D | control | 28 have the problems identified with mechanisms commonly in use.
63 have the problems identified with mechanisms commonly in use.
|
| /external/netperf/ |
| D | README.solaris | 20 reports. The CPU time accounting mechanisms either do not track time
|
| /external/autotest/server/tests/barriertest_2client/ |
| D | control.srv | 9 A functional test of autotest's Barrier mechanisms for synchronizing
|
| /external/eigen/doc/ |
| D | TopicLazyEvaluation.dox | 5 Executive summary: Eigen has intelligent compile-time mechanisms to enable lazy evaluation and remo…
23 For these reasons, Eigen has intelligent compile-time mechanisms to determine automatically when to…
|
| /external/libmicrohttpd/doc/chapters/ |
| D | sessions.inc | 69 instead of in memory. Still, having mechanisms to expire data
|
| /external/clang/docs/ |
| D | SafeStack.rst | 102 handling mechanisms, intrinsics such as ``__builtin_frame_address``, or
110 stronger safe stack protection mechanisms, that rely on software fault
|
| /external/mesa3d/src/mesa/tnl/ |
| D | NOTES | 43 The module provides customizability through several mechanisms. The
|
| /external/ltp/testcases/open_posix_testsuite/Documentation/ |
| D | HOWTO_RunTests | 32 and the framework merely calls these mechanisms. To build functional and
|
| /external/deqp/doc/testspecs/GLES3/ |
| D | performance.txt | 40 frames and utilize platform-defined standard mechanisms to display each
|
| /external/deqp/doc/testspecs/GLES2/ |
| D | performance.txt | 40 frames and utilize platform-defined standard mechanisms to display each
|
| /external/wpa_supplicant_8/hostapd/ |
| D | README | 127 802.1X would also allow other mechanisms.
274 Keys can be managed using two different mechanisms. WPA can either use
278 respectively. Both mechanisms will generate a master session key for
|
| /external/ltp/testcases/kernel/device-drivers/v4l/user_space/ |
| D | README | 65 tries some things which are supposed to test the error handling mechanisms
|
| /external/e2fsprogs/debian/ |
| D | control.in | 52 have the problems identified with mechanisms commonly in use.
64 have the problems identified with mechanisms commonly in use.
|