Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#6517 closed Bug report (rejected)

Certificate expired! (v3.3.5.1)

Reported by: Whitey.net Owned by:
Priority: low Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: XP Pro SP3

Description

Doing an FTPES connection to WebDomainNow.com (with any random username and password) gives a "Unknown certificate" message which says that the certificate expired in 01/01/1970 !!!

Is the certificate faulty, or FileZilla ?

By the way, this is the same certificate mentioned in bug #5693
so it's possible that those code changes caused the problem.

Screenshot attached as a B&W GIF to make the filesize tiny.

Thanks!

Attachments (2)

Unknown certificate.gif (15.7 KB ) - added by Whitey.net 10 years ago.
Screenshot of "Unknown certificate" dialog box.
decoded_certificate.unber (11.9 KB ) - added by Tim Kosse 10 years ago.
Decoded certificate

Download all attachments as: .zip

Change History (5)

by Whitey.net, 10 years ago

Attachment: Unknown certificate.gif added

Screenshot of "Unknown certificate" dialog box.

comment:1 by Whitey.net, 10 years ago

Priority: criticallow

by Tim Kosse, 10 years ago

Attachment: decoded_certificate.unber added

Decoded certificate

comment:2 by Tim Kosse, 10 years ago

Resolution: rejected
Status: newclosed

Definitely a broken certificate.

I have attached the decoded certificate. The notAfter field of the certificate is:

<P O="211" T="[UNIVERSAL 24]" TL="2" V="15" A="GeneralizedTime">19020219092442Z</P>

According to RFC 2459 which defines the structure of the certificate, the GeneralizedTime of the notAfter MUST be encoded according to YYYYMMDDHHMMSSZ.

19020219092442Z
YYYYMMDDHHMMSSZ

This clearly shows that the certificate has expired over a hundred years ago.

comment:3 by Tim Kosse, 10 years ago

Better formatting:

19020219092442Z
YYYYMMDDHHMMSSZ
Note: See TracTickets for help on using tickets.