You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some behaviours around PASV that need looking into:
We accept multiple pasv commands (and open new passive ports each time) - do we want to close the previous listening port, or not accept the new command?
With the timeout on pasv that was added: when the passive listening timeout is reached, how are we supposed to behave according to the RFC? Should we return some 4xx in response to the command that was received too late? (LIST, STOR, RETR)
The text was updated successfully, but these errors were encountered:
robklg
changed the title
Look into PASV
Look into correct PASV behaviour
Oct 26, 2022
Looked into this, and it looks like the correct (or at least common) behavior is to close the previously requested data port and open a new one. If a data command is received after the listening period timeout, we should return a 425 error.
There are some behaviours around PASV that need looking into:
The text was updated successfully, but these errors were encountered: