This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author janssen
Recipients giampaolo.rodola, gregory.p.smith, iElectric, janssen, pitrou, roberte
Date 2008-03-21.23:28:35
SpamBayes Score 0.24609965
Marked as misclassified No
Message-id <4b3e516a0803211628v34e75ea2pbfaba5beec566501@mail.gmail.com>
In-reply-to <1206103386.75.0.449687951428.issue2054@psf.upfronthosting.co.za>
Content
On Fri, Mar 21, 2008 at 5:43 AM, Robert E. <report@bugs.python.org> wrote:

>
> Robert E. <robert@re-factory.de> added the comment:
>
> Concerning the plain-text login. I think a FTPS class should default to
> encrypted login (you could use the ftp class if you dont want). In no
> way should the login credentials be sent unencrypted on default. Using
> another parameter might be a soulution to that, though I would prefer
> the library to raise an error if establishing an FTPS connection did not
> succeed. The main program could then catch it and decide how to proceed
> (using plain ftp or aborting according to a given policy).

Sounds reasonable to me.

Note that FTP is an old and somewhat gnarly protocol, and
doesn't work the way more recent application protocols do.  The SSL
module is designed for TCP-based single-connection call-response
protocols, more or less.  Doing FTPS right might mean we'd have to
extend it.
Files
File name Uploaded
unnamed janssen, 2008-03-21.23:28:35
History
Date User Action Args
2008-03-21 23:28:38janssensetspambayes_score: 0.2461 -> 0.24609965
recipients: + janssen, gregory.p.smith, pitrou, giampaolo.rodola, roberte, iElectric
2008-03-21 23:28:36janssenlinkissue2054 messages
2008-03-21 23:28:36janssencreate