From kde-devel Mon Sep 24 06:36:27 2007 From: Thiago Macieira Date: Mon, 24 Sep 2007 06:36:27 +0000 To: kde-devel Subject: Re: SSL Dialog for application to use Message-Id: <200709240836.39724.thiago () kde ! org> X-MARC-Message: https://marc.info/?l=kde-devel&m=119061591830239 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0455606322==" --===============0455606322== Content-Type: multipart/signed; boundary="nextPart2767443.fzn7WTzbqR"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2767443.fzn7WTzbqR Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Andreas Pakulat wrote: >> Also, mind you: there is no intention of providing an API to display a >> certificate. You should use only the KDE SSL implementation with its >> QTcpSocket-based class. > >Ok, that answers my question. I will stick with the home-grown one then. Yep, makes sense. This will explain to people that the SVN support is not part of KDE and=20 they have to configure it themselves. For instance, it will not use the=20 proxy settings (once we have that...). =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 --nextPart2767443.fzn7WTzbqR 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) iD8DBQBG91rsM/XwBW70U1gRAs5cAKC5eWR7/7xA26rjZwxr1HBLz1jycQCgjaGl XmQCQAMzh7p6BO1yKp7bLoc= =iYce -----END PGP SIGNATURE----- --nextPart2767443.fzn7WTzbqR-- --===============0455606322== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --===============0455606322==--