Opened 14 years ago

Last modified 14 years ago

#984 closed Bug report

Installing commercial SSL cert hangs FZS @ 100% CPU usage

Reported by: aellsworth Owned by:
Priority: high Component: FileZilla Server
Keywords: Cc: aellsworth, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

To reproduce:

Generate a certificate signing request (CSR). Example
with openssl:

openssl req -new -out certreq.txt

Give the private key a password of "test". For this
example, the corresponding private key will be dropped
in the current directory as "privkey.pem". Note the
location of this file.

Use the CSR you just created to obtain a Thawte trial
SSL certificate for free:

https://www.thawte.com/cgi/server/try.exe

Paste in the text from the certreq.txt file, and save
the resultant certificate text in a new file, certnew.pem.

Pull up the FileZilla server interface. Access Edit ->
Settings. Click SSL/TLS settings. Click Enable SSL/TLS
support. Enter the full path to privkey.pem in the
"Private key file" field. Enter the full path to the
new Thawte trial certificate in the "Certificate file"
field. Press OK.

Filezilla server interface hangs, and consumes 100% of
CPU. Interface must be force-killed.

Version: Filezilla server 0.9.10a
Platform: Windows Server 2003.

Change History (3)

comment:1 Changed 14 years ago by aellsworth

FYI, I believe this may be related to encrypted private key
files. OpenSSL (and just about any other program that will
generate a private key file) requires encryption to protect
the private key. This is typically done via a text
passphrase (OpenSSL requires a minimum of 4 character
passphrase, and will not accept a null passphrase). There is
no provision in FZS to enter the passphrase for a private key.

Also, the self-generated certificate and private key that
FZS creates appears to have an unencrypted private key,
further supporting this theory.

comment:2 Changed 14 years ago by Tim Kosse

Yes, it's the password protected keyfiles that are causing
this problem. I'm working on a solution. I plan to release a
fixed version this weekend.

comment:3 Changed 14 years ago by aellsworth

I can confirm that this problem is fixed.

Note: See TracTickets for help on using tickets.