Custom Query (8170 matches)
Results (385 - 387 of 8170)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #5633 | fixed | Be less trusting of trusted certificates | ||
| Description |
When FileZilla is told to trust a self-signed certificate, that certificate will be accepted for any connection. For example, if I trust a certificate from some random guy for my connection to ftp.randomguy.net, that certificate will also be treated as valid for filezilla-project.org, google.com, sourceforge.net and so on. The certificate (or rather FileZillas trust in the certificate) ought to be bound to a specific hostname or to a specific site in the site manager. Steps to reproduce the problem:
The result: FileZilla connects without warnings to the second server, even though the certificate belongs to a completely different server. Software versions: FileZilla 3.3.4.1, GnuTLS 2.8.6 |
|||
| #5635 | fixed | MKD command should return directory-name on success | ||
| Description |
RFC 959: "upon successful completion of an MKD command, the server should return a line of the form: 257<space>"<directory-name>"<space><commentary> FileZilla returns: C: MKD Folder1 S: 257 Directory created successfully |
|||
| #5647 | fixed | MKD command ignores leading spaces | ||
| Description |
Leading spaces are truncated by MKD commands. Same issue also exists for files. S: 220-FileZilla Server version 0.9.36 beta S: 220-written by Tim Kosse (Tim.Kosse@gmx.de) S: 220 Please visit http://sourceforge.net/projects/filezilla/ ... C: MKD Folder1 S: 257 Directory created successfully C: MKD Folder1 S: 550 Directory already exists |
|||
