From kde-core-devel  Sun Sep 30 18:14:18 2007
From: Thiago Macieira <thiago () kde ! org>
Date: Sun, 30 Sep 2007 18:14:18 +0000
To: kde-core-devel
Subject: Re: Update on KIO & KSSL
Message-Id: <200709302014.19473.thiago () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=119117611619277
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1327604.8olOmYGGc8"

--nextPart1327604.8olOmYGGc8
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

George Staikos wrote:
>On 30-Sep-07, at 10:48 AM, Allen Winter wrote:
>> On Thursday 06 September 2007 8:43:47 am George Staikos wrote:
>>> This is probably the best (safest) approach for now.  The only
>>> problem remaining is how to get app developers to put appropriate UI
>>> in place since SSL is very heavily dependent on a proper UI.
>>
>> Time to beg.
>> George? Anyone?  I checked with Thiago and he is very busy with
>> other things.
>>
>> We really need to get KSSL to work.  Time is running very short.
>>
>> You can have all the time you need ... as long as you can get
>> something operational in the next 3-4 weeks. :)
>
>    What part of it doesn't work?  I think you're saying "we need new
>features".  I'm sorry but I just don't have time right now.

To be very specific:

KSSL works. Just fine, inside TCPSlaveBase.

What we need are two separate things:

1) an implementation of an SSL Socket that uses that KSSL, hopefully=20
keeping so much of its internals private that it can choose another=20
backend in the future. I've started that with the patch I posted: it's a=20
QTcpSocket-based socket implementation that behaves similarly to=20
QSslSocket. It requires a public function to activate it (in KIO,=20
probably) as well as a lot of testing.

2) port TCPSlaveBase to this new socket class from #1. This will require=20
some work as well on the blocking-mode part of QTcpSocket, since there=20
are some caveats there. I plan on helping there whenever possible.

All of this work is entirely binary-compatible. And aside from the=20
addition of a new method to activate encryption, it's also forwards and=20
backwards compatible. It can be enabled/disabled on a compile-time basis=20
so that we detect our problems without exposing it to our users.

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

--nextPart1327604.8olOmYGGc8
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBG/+d7M/XwBW70U1gRAoCZAJ9Q7dLOD+9z0YphCfsQAOpCDgLJKwCeM8b8
027LZu/gpHLijpe5zCDOoss=
=o2cD
-----END PGP SIGNATURE-----

--nextPart1327604.8olOmYGGc8--