<testcase> <info> <keywords> FTPS PORT LIST </keywords> </info> # # Server-side <reply> # When doing LIST, we get the default list output hard-coded in the test # FTPS server <datacheck> total 20 drwxr-xr-x 8 98 98 512 Oct 22 13:06 . drwxr-xr-x 8 98 98 512 Oct 22 13:06 .. drwxr-xr-x 2 98 98 512 May 2 1996 .NeXT -r--r--r-- 1 0 1 35 Jul 16 1996 README lrwxrwxrwx 1 0 1 7 Dec 9 1999 bin -> usr/bin dr-xr-xr-x 2 0 1 512 Oct 1 1997 dev drwxrwxrwx 2 98 98 512 May 29 16:04 download.html dr-xr-xr-x 2 0 1 512 Nov 30 1995 etc drwxrwxrwx 2 98 1 512 Oct 30 14:33 pub dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr </datacheck> </reply> # # Client-side <client> <features> SSL </features> <server> ftps </server> <name> FTPS dir list, PORT with specified IP </name> <command> -k --ftp-ssl-control -P %CLIENTIP ftps://%HOSTIP:%FTPSPORT/ </command> </client> # # Verify data after the test has been "shot" <verify> # Strip all valid kinds of PORT and EPRT that curl can send <strip> ^PORT \d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3},\d{1,3} ^EPRT \|1\|\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}\|\d{1,5}\| </strip> <protocol> USER anonymous PASS ftp@example.com PBSZ 0 PROT C PWD PORT 127,0,0,1,243,212 TYPE A LIST QUIT </protocol> </verify> </testcase>