It's not worth our time to review FTPS in the
context of IPv6 since nothing changes.
Let's dive right into testing it instead.
We've learned earlier in this course that FTPS is just like FTP,
except with SSL protection for privacy.
As such, all the same TCP ports and flows operate identically.
Let's quickly test an active mode download and passive
mode upload for our packet capture.
First, the download script.
It's identical to its IPv4 counterpart except uses IPv6 addresses.
Let's test it out.
The server features include AUTH TLS, PBSZ,
and PROT, which are necessary for FTPS.
For a detailed explanation of these individual commands,
please review the FTPS module.
We mostly care about AUTH TLS right now.
The client sends the AUTH TLS command to the server.
The server encourages the client to continue using FTPS.
The client sends the user command and the server
responds with its digital certificate,
which we are manually trusting on the client side.
The client then authenticates using the PASS command,
and the regular FTP active mode process continues.
I won't belabor that.
Time for the passive mode upload.
There are two small differences between this file and the active mode download.
First, passive mode is enabled, which is also the lftp default.
Next, the put command is used instead of get.
Pretty simple.
Time to execute the script.
I won't go through this again because the mode of FTP has no
impact on the initial authentication process.
After that, FTP passive mode operates normally.
Question for you.
Despite this traffic being encrypted,
is there a way to tell the difference between FTPS active
and FTPS passive traffic in Wireshark?
We'll double back to answer this question in a few clips when we explore the packet capture.