Go
Go
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 Go Downloads
success := false
ftp := chilkat.NewFtp2()
ftp.SetHostname("ftp.example.com")
ftp.SetUsername("myFtpLogin")
ftp.SetAuthTls(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.
ftp.SetPassword("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.
ftp.SetRequireSslCertVerify(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.
ftp.SetTlsPinSet("sha256//YLh1dUR9y6Kja30RrAn7JKnbQG/uEtLMkBgFF2Fuihg=")
success = ftp.Connect()
if success == false {
fmt.Println(ftp.LastErrorText())
ftp.DisposeFtp2()
return
}
// SslServerCertVerified reports whether the certificate chain was successfully verified.
if ftp.SslServerCertVerified() {
fmt.Println("The server certificate was verified.")
}
success = ftp.Disconnect()
if success == false {
fmt.Println(ftp.LastErrorText())
ftp.DisposeFtp2()
return
}
ftp.DisposeFtp2()