ELFX4(CIPHER - The selected feature is not availableCIPHER - Bad input parametersCIPHER - Failed to allocate memoryCIPHER - Input data contains invalid padding and is rejectedCIPHER - Decryption of block requires a full blockCIPHER - Authentication failed (for AEAD modes)CIPHER - The context is invalid. For example, because it was freedCIPHER - Cipher hardware accelerator failedDHM - Bad input parametersDHM - Reading of the DHM parameters failedDHM - Making of the DHM parameters failedDHM - Reading of the public values failedDHM - Making of the public value failedDHM - Calculation of the DHM secret failedDHM - The ASN.1 data is not formatted correctlyDHM - Allocation of memory failedDHM - Read or write of file failedDHM - DHM hardware accelerator failedDHM - Setting the modulus and generator failedECP - Bad input parameters to functionECP - The buffer is too small to write toECP - The requested feature is not available, for example, the requested curve is not supportedECP - The signature is not validECP - Memory allocation failedECP - Generation of random value, such as ephemeral key, failedECP - Invalid private or public keyECP - The buffer contains a valid signature followed by more dataECP - The ECP hardware accelerator failedECP - Operation in progress, call again with the same parameters to continueMD - The selected feature is not availableMD - Bad input parameters to functionMD - Failed to allocate memoryMD - Opening or reading of file failedMD - MD hardware accelerator failedPEM - No PEM header or footer foundPEM - PEM string is not as expectedPEM - Failed to allocate memoryPEM - RSA IV is not in hex-formatPEM - Unsupported key encryption algorithmPEM - Private key password can't be emptyPEM - Given private key password does not allow for correct decryptionPEM - Unavailable feature, e.g. hashing/encryption combinationPEM - Bad input parameters to functionPK - Memory allocation failedPK - Type mismatch, eg attempt to encrypt with an ECDSA keyPK - Bad input parameters to functionPK - Read/write of file failedPK - Unsupported key versionPK - Invalid key tag or valuePK - Key algorithm is unsupported (only RSA and EC are supported)PK - Private key password can't be emptyPK - Given private key password does not allow for correct decryptionPK - The pubkey tag or value is invalid (only RSA and EC are supported)PK - The algorithm tag or value is invalidPK - Elliptic curve is unsupported (only NIST curves are supported)PK - Unavailable feature, e.g. RSA disabled for RSA keyPK - The buffer contains a valid signature followed by more dataPK - PK hardware accelerator failedPKCS12 - Bad input parameters to functionPKCS12 - Feature not available, e.g. unsupported encryption schemePKCS12 - PBE ASN.1 data not as expectedPKCS12 - Given private key password does not allow for correct decryptionPKCS5 - Bad input parameters to functionPKCS5 - Unexpected ASN.1 dataPKCS5 - Requested encryption or digest alg not availablePKCS5 - Given private key password does not allow for correct decryptionRSA - Bad input parameters to functionRSA - Input data contains invalid padding and is rejectedRSA - Something failed during generation of a keyRSA - Key failed to pass the validity check of the libraryRSA - The public key operation failedRSA - The private key operation failedRSA - The PKCS#1 verification failedRSA - The output buffer for decryption is not large enoughRSA - The random generator failed to generate non-zerosRSA - The implementation does not offer the requested operation, for example, because of security violations or lack of functionalityRSA - RSA hardware accelerator failedSSL - The requested feature is not availableSSL - Bad input parameters to functionSSL - Verification of the message MAC failedSSL - An invalid SSL record was receivedSSL - The connection indicated an EOFSSL - An unknown cipher was receivedSSL - The server has no ciphersuites in common with the clientSSL - No RNG was provided to the SSL moduleSSL - No client certification received from the client, but required by the authentication modeSSL - Our own certificate(s) is/are too large to send in an SSL messageSSL - The own certificate is not set, but needed by the serverSSL - The own private key or pre-shared key is not set, but neededSSL - No CA Chain is set, but required to operateSSL - An unexpected message was received from our peerSSL - A fatal alert message was received from our peerSSL - Verification of our peer failedSSL - The peer notified us that the connection is going to be closedSSL - Processing of the ClientHello handshake message failedSSL - Processing of the ServerHello handshake message failedSSL - Processing of the Certificate handshake message failedSSL - Processing of the CertificateRequest handshake message failedSSL - Processing of the ServerKeyExchange handshake message failedSSL - Processing of the ServerHelloDone handshake message failedSSL - Processing of the ClientKeyExchange handshake message failedSSL - Processing of the ClientKeyExchange handshake message failed in DHM / ECDH Read PublicSSL - Processing of the ClientKeyExchange handshake message failed in DHM / ECDH Calculate SecretSSL - Processing of the CertificateVerify handshake message failedSSL - Processing of the ChangeCipherSpec handshake message failedSSL - Processing of the Finished handshake message failedSSL - Memory allocation failedSSL - Hardware acceleration function returned with errorSSL - Hardware acceleration function skipped / left alone dataSSL - Processing of the compression / decompression failedSSL - Handshake protocol not within min/max boundariesSSL - Processing of the NewSessionTicket handshake message failedSSL - Session ticket has expiredSSL - Public key type mismatch (eg, asked for RSA key exchange and presented EC key)SSL - Unknown identity received (eg, PSK identity)SSL - Internal error (eg, unexpected failure in lower-level module)SSL - A counter would wrap (eg, too many messages exchanged)SSL - Unexpected message at ServerHello in renegotiationSSL - DTLS client must retry for hello verificationSSL - A buffer is too small to receive or write a messageSSL - None of the common ciphersuites is usable (eg, no suitable certificate, see debug messages)SSL - No data of requested type currently available on underlying transportSSL - Connection requires a write callSSL - The operation timed outSSL - The client initiated a reconnect from the same portSSL - Record header looks valid but is not expectedSSL - The alert message received indicates a non-fatal errorSSL - Couldn't set the hash for verifying CertificateVerifySSL - Internal-only message signaling that further message-processing should be doneSSL - The asynchronous operation is not completed yetSSL - Internal-only message signaling that a message arrived earlySSL - An encrypted DTLS-frame with an unexpected CID was receivedSSL - An operation failed due to an unexpected version or configurationSSL - A cryptographic operation is in progress. Try again laterSSL - Invalid value in SSL configX509 - Unavailable feature, e.g. RSA hashing/encryption combinationX509 - Requested OID is unknownX509 - The CRT/CRL/CSR format is invalid, e.g. different type expectedX509 - The CRT/CRL/CSR version element is invalidX509 - The serial tag or value is invalidX509 - The algorithm tag or value is invalidX509 - The name tag or value is invalidX509 - The date tag or value is invalidX509 - The signature tag or value invalidX509 - The extension tag or value is invalidX509 - CRT/CRL/CSR has an unsupported version numberX509 - Signature algorithm (oid) is unsupportedX509 - Signature algorithms do not match. (see \c ::mbedtls_x509_crt sig_oid)X509 - Certificate verification failed, e.g. CRL, CA or signature check failedX509 - Format not recognized as DER or PEMX509 - Input invalidX509 - Allocation of memory failedX509 - Read/write of file failedX509 - Destination buffer is too smallX509 - A fatal error occurred, eg the chain is too long or the vrfy callback failed|ip!}#x})PU)0, LA AT, 1A @, =A @, CA (@, EA \@, KA <`, L8c@l8!N , lA `@H, vA \@, {A @t, ~A @H, A <`, 8cA, ~@4<`8c8!N , K@ <`8cK, }A D@D, }@ <`8cKh, yA 8@\, zA @4, {@ <`8cK<, |A, |@ <`8cK , yA, z@ <`8cK, xA @, x@ <`8cK, qA ,@, tA @, uA@, v@ D<`8cK, cA $@, hA @, jA @, kA<<`, l8cAp, k@ <`8cK\, wA, w@ <`8cK@, tA, u@ <`8cK$, sA@D, s@ <`8cK, oA @\, pA`@4, q@ <`8cK, rA\, r@ <`8cK, oA4, p@ \<`8cK, nA@, n@ 0<`8cK, DAp@ , E@ p<`8cK`, 8A @, ;A@d, A, >@<`8cK, aAx, a@<`8cK, _AT@D, `@<`8cK, OA@\, QA@4, Q@<`8cKd, RA, ^@<`8cKH, OA, P@<`8cK,, NA@T, N@$<`8cK , fA, f@<<`8cK, dA|@4, e@8<`8cK, MAL, M@X<`8cK, cA$, d@4<`8cK<`8cK<`8cK<`8cKt<`8cKh<`8cK\<`8cKP<`8cKD<`8cK8<`8cK,<`8cK <`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cKx<`8cKl<`8cK`<`8cKT<`8cKH<`8cK<<`8cK0<`8cK$<`8cK<`8cK <`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK|<`8cKp<`8cKd<`8cKX<`8cKL<`8cK@<`8cK4<`8cK(<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cKt<`8cKh<`8cK\<`8cKP<`8cKD<`8cK8<`8cK,<`8cK <`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cK<`8cKx8`Kp8`Kh8`K`8`KX8`KP8`KH8`K@8`K88`K08`K(8`K 8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K<`8cK<`8cK<`8cKt8`Kl8`Kd8`K\8`KT8`KL8`KD8`K<8`K48`K,8`K$8`K8`K8`K 8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K8`K|8`Kt|ip!}#x})PU)^8`9)( tA=@U):9J|jH.8!N UNKNOWN ERROR CODE (%04X)%s : !|+y@8! N |#x||x$8x=`k}iN!p}?xPsA<xH<|fy8Axx=`k}iN!,wAW_Ax=`k}iN!||yA8|P(@x<8|~=`k}i;;N!9?( t@d<xxx8=`k$}i|8! N $|8! N =@U):9J|H.,A<xx8K<x8KERROR - Generic errorBIGNUM - An error occurred while reading from or writing to a fileHMAC_DRBG - Too many random requested in single callBIGNUM - Bad input parameters to functionHMAC_DRBG - Input too large (Entropy + additional)BIGNUM - There is an invalid character in the digit stringHMAC_DRBG - Read/write error in fileBIGNUM - The buffer is too small to write toHMAC_DRBG - The entropy source failedBIGNUM - The input arguments are negative or result in illegal outputOID - output buffer is too smallBIGNUM - The input argument for division is zero, which is not allowedBIGNUM - The input arguments are not acceptableBIGNUM - Memory allocation failedGCM - Authenticated decryption failedGCM - GCM hardware accelerator failedGCM - Bad input parameters to functionBLOWFISH - Bad input dataBLOWFISH - Blowfish hardware accelerator failedBLOWFISH - Invalid data input lengthARC4 - ARC4 hardware accelerator failedAES - Invalid key lengthAES - Invalid input dataAES - Invalid data input lengthAES - Feature not available. For example, an unsupported AES key sizeAES - AES hardware accelerator failedBASE64 - Output buffer too smallBASE64 - Invalid character in inputOID - OID is not foundMD5 - MD5 hardware accelerator failedPADLOCK - Input data should be alignedCTR_DRBG - The entropy source failedSHA1 - SHA-1 hardware accelerator failedCTR_DRBG - The requested random buffer length is too bigSHA256 - SHA-256 hardware accelerator failedCTR_DRBG - The input (entropy + additional data) is too largeSHA512 - SHA-512 hardware accelerator failedCTR_DRBG - Read or write error in fileENTROPY - Critical entropy source failureENTROPY - No strong sources have been added to pollENTROPY - No more sources can be addedENTROPY - Read/write error in fileENTROPY - No sources have been added to pollNET - Failed to open a socketNET - Buffer is too small to hold the dataNET - The connection to the given server / port failedNET - The context is invalid, eg because it was free()edNET - Binding of the socket failedNET - Polling the net context failedNET - Could not listen on the socketNET - Input invalidNET - Could not accept the incoming connectionNET - Reading information from the socket failedNET - Sending information through the socket failedNET - Connection was reset by peerCHACHA20 - Invalid input parameter(s)NET - Failed to get an IP address for the given hostnameCHACHA20 - Feature not available. For example, s part of the API is not implementedCHACHAPOLY - The requested operation is not permitted in the current stateCHACHA20 - Chacha20 hardware accelerator failedCHACHAPOLY - Authenticated decryption failed: data was not authenticPOLY1305 - Invalid input parameter(s)POLY1305 - Feature not available. For example, s part of the API is not implementedPOLY1305 - Poly1305 hardware accelerator failedASN1 - Out of data when parsing an ASN1 data structureASN1 - ASN1 tag was of an unexpected valueASN1 - Error when trying to determine the length or invalid lengthASN1 - Actual length differs from expected lengthASN1 - Data is invalidASN1 - Memory allocation failedASN1 - Buffer too small when writing ASN.1 data structureERROR - This is a bug in the librarySHA1 - SHA-1 input data was malformedSHA256 - SHA-256 input data was malformedSHA512 - SHA-512 input data was malformedGCC: (OpenWrt GCC 11.2.0 r20058-7370479224) 11.2.0zR|A BY A W A 8<BLLPA AD A ABA ABAB{ AAAABA B AAAABA      ,<E V]ferror.cCSWTCH.4mbedtls_high_level_strerrmbedtls_low_level_strerrmbedtls_strerrormemsetsnprintfstrlenZb&*BXFX^b~@@00h h"&>B^bXX((:>rz    *.F 8J 8bhfh     "\&\BF^LbLzH~H    P"PJ <N <f4j4     & * BxFxz~PP6h:hVZr|v|PP$$\\DD L L   0 "0 *@ .@ 6 : B F N R Z ^ fX jX r v ~ H  H   ( (                 < < ` ` H H     &( *( 2 ` 6 ` > B J N V Z b f n r z ~               T T     H H       " & . 2 : > Fp Jp Rt Vt ^ b jH nH v( z(   t t     ` `      X  X t t    h  h     | "| * . 6| :| B F N R Z ^ f d j d r v ~     H  H     0 0   ` ` t t        &.B F H wL xh nvwxwx  wx w<xbjz\ 0X $(,4d<DHLT0XL\|`|$lDlDt$Hx 8\ $,4 $< X@ |D H L 4P T X ` h t|    L      D p<T.symtab.strtab.shstrtab.text.data.bss.rodata.mbedtls_high_level_strerr.str1.4.rela.text.mbedtls_high_level_strerr.rela.text.mbedtls_low_level_strerr.rodata.mbedtls_strerror.str1.4.rela.text.mbedtls_strerror.rodata.str1.4.rela.rodata.CSWTCH.4.comment.note.GNU-stack.rela.eh_frame4!4'4,24 Z U@C /<z@R 20$0@@R,  21 ?x@S  0AL4AA@W<$ B  CmW`'