Forcing a higher SSL encryption >168Bit

Grendel · 01-03-2005, 07:35 AM

Hi@all,

does anyone knows how to force
a higher ssl-encyption as 168Bit with ioFTPD ?
(which is maximum I can get on 2003 Servers).

Yes... of cause I know it would be much slower
then a MD5 128bit key,
but AES256-SHA - for expamle - would be nice
and not a problem for other ftp-servers.

Is there a way to create other/better certificates for it ?
Any ideas ?

^ng3| · 01-21-2005, 04:06 AM

just
Min_Cipher_Strength = 168

[L] 234 AUTH SSL successful.
[L] Connected. Negotiating SSL session..
[L] SSL negotiation successful...
[L] SSL encrypted session using cipher DES-CBC3-SHA (168 bits)

neoxed · 01-21-2005, 04:33 AM

This question was posted a few days ago...

http://www.ioftpd.com/board/showthre...?threadid=4492

The reason is that ioFTPD utilizes the Microsoft Security Support Provider Interface (SSPI) for encrypting data; and it does not allow anything higher than 168bits. Other FTP servers make use of the OpenSSL library (like glftpd), which supports higher encryption strengths at the expense of performance and flexibility (for the programmer). Anyway, 168bits is MORE than suitable.