On Thu, 20 Nov 2003, Dan Fandrich wrote:

> This sounds like an important new protocol for curl.

I think it feels like one that fits well into the library, yes.

> Is the existing curl behaviour for ftps:// still available if necessary?

Nope, not as I've done things now. I've tried to follow these specs instead. I
couldn't find any decent way to keep the current while at the same time
attempt to do it right.

> Does anyone use that existing behaviour (it seems that it implements
> something like the "SSL connect" method mentioned at the web site you gave
> the other day, but on port 21 instead of 990, right)?

I don't know anyone that uses the current ftps behavior, so if there's anyone
reading this who uses it, please speak up! And if there's anyone speaking up
later on, I think we can deal with it then. The current approach is a big hack
and I feel good about finally doing this "the right way".

> Does the code fall back to "AUTH SSL" instead of "AUTH TLS" for backward
> compatibility?

Not right now, no. But things like that should be easy to fix once we get to
try servers that work that way.

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
 [[ Do not post private mails to this email address. They won't reach me. ]]
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/