From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 05CDF1385DD for ; Sat, 5 Sep 2015 01:09:40 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 909CD14218; Sat, 5 Sep 2015 01:09:32 +0000 (UTC) Received: from BLU004-OMC1S30.hotmail.com (blu004-omc1s30.hotmail.com [65.55.116.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 94C4E141EC for ; Sat, 5 Sep 2015 01:09:31 +0000 (UTC) Received: from BLU436-SMTP209 ([65.55.116.9]) by BLU004-OMC1S30.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 4 Sep 2015 18:09:30 -0700 X-TMN: [iljvHPTzDjp1WeOT7/kE547XrE4pKASJ] X-Originating-Email: [frodriguez.developer@outlook.com] Message-ID: From: Fernando Rodriguez To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] broken seamonkey :( Date: Fri, 4 Sep 2015 21:08:47 -0400 User-Agent: KMail/4.14.8 (Linux/3.18.20; KDE/4.14.8; x86_64; ; ) In-Reply-To: <87k2s5lra5.fsf@heimdali.yagibdah.de> References: <87oahjmg8s.fsf@heimdali.yagibdah.de> <87k2s5lra5.fsf@heimdali.yagibdah.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-OriginalArrivalTime: 05 Sep 2015 01:09:30.0369 (UTC) FILETIME=[847D8F10:01D0E777] X-Archives-Salt: 72112da7-a40a-43c4-974d-a2e503e75bcb X-Archives-Hash: e1c08d595eea7f43deedd53f7846f6ca On Saturday, September 05, 2015 1:05:06 AM lee wrote: > In this case, I happen to have full physical access to the server and > thus to the certificate stored on it. This is not the case for, let's > say, an employee checking his work-email from home whom I might give the > login-data on the phone and instruct to add an exception when the dialog > to do so pops up when they are trying to connect. As a workaround you can create your own CA cert. I tested with a windows self- signed cert (I guess the correct term is self-issued) and the openssl command will show two certs. The second is the CA. http://datacenteroverlords.com/2012/03/01/creating-your-own-ssl-certificate-authority/ -- Fernando Rodriguez