/// Returns true if failure was likely caused by rejected
/// credentials. In some cases, we cannot be 100% certain that
/// credentials were rejected, but it's worth noting when we
/// observe a failure event that was more than likely caused by
/// rejected credentials.
Returns true if failure was likely caused by rejected
credentials. In some cases, we cannot be 100% certain that
credentials were rejected, but it's worth noting when we
observe a failure event that was more than likely caused by
rejected credentials.
Returns true if failure was likely caused by rejected credentials . In some cases we cannot be 100% certain that credentials were rejected but it ' s worth noting when we observe a failure event that was more than likely caused by rejected credentials .
pub fn likely_due_to_credential_rejected(&self) -> bool {
        match self {
            // Assuming the correct type of credentials are given, a
            // bad password will cause a variety of errors depending
            // on the security type. All of the following cases assume
            // no frames were dropped unintentionally. For example,
            // it's possible to conflate a WPA2 bad password error
            // with a dropped frame at just the right moment since the
            // error itself is *caused by* a dropped frame.
            // For WPA1 and WPA2, the error will be
            // EstablishRsnaFailure::KeyFrameExchangeTimeout.  When
            // the authenticator receives a bad MIC (derived from the
            // password), it will silently drop the EAPOL handshake
            // frame it received.
            //
            // NOTE: The alternative possibilities for seeing an
            // EstablishRsnaFailure::KeyFrameExchangeTimeout are an
            // error in our crypto parameter parsing and crypto
            // implementation, or a lost connection with the AP.
            ConnectFailure::EstablishRsnaFailure(EstablishRsnaFailure {
                auth_method: Some(auth::MethodName::Psk),
                reason: EstablishRsnaFailureReason::KeyFrameExchangeTimeout,
            }) => true,
            // For WEP, the entire association is always handled by
            // fullmac, so the best we can do is use
            // fidl_mlme::AssociateResultCode. The code that arises
            // when WEP fails with rejected credentials is
            // RefusedReasonUnspecified. This is a catch-all error for
            // a WEP authentication failure, but it is being
            // considered good enough for catching rejected
            // credentials for a deprecated WEP association.
            ConnectFailure::AssociationFailure(AssociationFailure {
                bss_protection: BssProtection::Wep,
                code: fidl_ieee80211::StatusCode::RefusedUnauthenticatedAccessNotSupported,
            }) => true,
            _ => false,
        }
    }
pub fn likely_due_to_credential_rejected ( & self ) -> bool { match self { // Assuming the correct type of credentials are given, a // bad password will cause a variety of errors depending // on the security type. All of the following cases assume // no frames were dropped unintentionally. For example, // it's possible to conflate a WPA2 bad password error // with a dropped frame at just the right moment since the // error itself is *caused by* a dropped frame. // For WPA1 and WPA2, the error will be // EstablishRsnaFailure::KeyFrameExchangeTimeout.  When // the authenticator receives a bad MIC (derived from the // password), it will silently drop the EAPOL handshake // frame it received. // // NOTE: The alternative possibilities for seeing an // EstablishRsnaFailure::KeyFrameExchangeTimeout are an // error in our crypto parameter parsing and crypto // implementation, or a lost connection with the AP. ConnectFailure :: EstablishRsnaFailure ( EstablishRsnaFailure { auth_method : Some ( auth :: MethodName :: Psk ) , reason : EstablishRsnaFailureReason :: KeyFrameExchangeTimeout , } ) => true , // For WEP, the entire association is always handled by // fullmac, so the best we can do is use // fidl_mlme::AssociateResultCode. The code that arises // when WEP fails with rejected credentials is // RefusedReasonUnspecified. This is a catch-all error for // a WEP authentication failure, but it is being // considered good enough for catching rejected // credentials for a deprecated WEP association. ConnectFailure :: AssociationFailure ( AssociationFailure { bss_protection : BssProtection :: Wep , code : fidl_ieee80211 :: StatusCode :: RefusedUnauthenticatedAccessNotSupported , } ) => true , _ => false , } }
Returns true if failure was likely caused by rejected
credentials.
Returns true if failure was likely caused by rejected credentials .
&self