--===============0773449091==
Content-Type: multipart/signed;
  boundary="nextPart1287214.ghMgVA1Mvd";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1287214.ghMgVA1Mvd
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Wednesday 10 June 2009 20:42:12 Anthony J Moulen wrote:
> If you work inside a large corporate environment you will probably find
> a lot of self signed certificates.  If they have done the right thing they
> will have established an internal signer to sign all the certificates, but
> many won't do this, or with hundreds of test environments it isn't cost
> effective to really manage anything but self signed with long
> expiration dates.

You raise good points but at the same time, the use-case for the dialog sho=
uld=20
not be adjusted toward making it easier for large corporations to click-
through their broken certificates.

Large corporations that use KDE will not be compiling it from kde.org but w=
ill=20
instead be purchasing it via a distribution vendor, who can make any necess=
ary=20
dialog fixups/changes to support the needs of the corporation.

Regards,
 - Michael Pyne

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEABECAAYFAkowYRQACgkQqjQYp5Omm0rl1gCeIp6ABZwqXMOuxUyrKMnufZz4
taoAn3GNkGto0D7JW/m2//YpcKdERJ+I
=hxi2
-----END PGP SIGNATURE-----

--nextPart1287214.ghMgVA1Mvd--

--===============0773449091==
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 <<

--===============0773449091==--