AutoIt
AutoIt
Verify and Pin the FTPS Server Certificate
See more FTP Examples
Demonstrates the certificate-verification properties RequireSslCertVerify, TlsPinSet, and the read-only SslServerCertVerified.
Background: By default a TLS connection is not rejected merely because certificate-chain verification fails, so
RequireSslCertVerify = true is the important hardening step — it makes an expired, unsigned, or untrusted certificate abort the connection. TlsPinSet adds public-key pinning on top: the handshake fails unless the server's SPKI fingerprint matches one you configured, defending against a mis-issued certificate that would otherwise validate. Pinning supplements verification rather than replacing it. SslServerCertVerified reports the outcome.Chilkat AutoIt Downloads
Local $bSuccess = False
$oFtp = ObjCreate("Chilkat.Ftp2")
$oFtp.Hostname = "ftp.example.com"
$oFtp.Username = "myFtpLogin"
$oFtp.AuthTls = True
; Normally you would not hard-code the password in source. You should instead obtain it
; from an interactive prompt, environment variable, or a secrets vault.
$oFtp.Password = "myPassword"
; Reject the connection if the server certificate cannot be verified (expired, bad signature,
; untrusted chain, etc.). The default is False, which does not reject on verification
; failure -- set True for security.
$oFtp.RequireSslCertVerify = True
; Optionally pin the server's public key. If none of the configured SPKI fingerprints matches,
; the TLS handshake fails. Pinning supplements normal verification; it does not replace it.
$oFtp.TlsPinSet = "sha256//YLh1dUR9y6Kja30RrAn7JKnbQG/uEtLMkBgFF2Fuihg="
$bSuccess = $oFtp.Connect()
If ($bSuccess = False) Then
ConsoleWrite($oFtp.LastErrorText & @CRLF)
Exit
EndIf
; SslServerCertVerified reports whether the certificate chain was successfully verified.
If ($oFtp.SslServerCertVerified) Then
ConsoleWrite("The server certificate was verified." & @CRLF)
EndIf
$bSuccess = $oFtp.Disconnect()
If ($bSuccess = False) Then
ConsoleWrite($oFtp.LastErrorText & @CRLF)
Exit
EndIf