From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Q3vzF-0000TT-Dc for garchives@archives.gentoo.org; Sun, 27 Mar 2011 19:50:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F2321C05A; Sun, 27 Mar 2011 19:49:35 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id EA32E1C05A for ; Sun, 27 Mar 2011 19:49:34 +0000 (UTC) Received: by wwj40 with SMTP id 40so2897413wwj.10 for ; Sun, 27 Mar 2011 12:49:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:from:reply-to:to:subject:date:user-agent :references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=hqUjOBZAbw0GKwI5QVOCNTeFb7QnqTLXWNv/rZRJMgU=; b=EOD8u0z9+6kSxkDbnw0DcJMGoUD/tsEaYVhz8rlHvSNqZW05eNrdKwFaKyPASD5i12 Cka5XcNFW5mBOl11rXIVGY60z5eyOVeDMpZNWVX1+lTgV3fumPGfq83gPesMQjJZ54eo jXvFYI8Fl4HiYuc8ZfKPRVO3GmiYWLgb4yDRk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=iF45XXw6lVVEOHdisZ7FFZhGnpnNz3j6qqTwK8+arZAJaNDHWwpl7IoJFOmcH/yvQf B/dyj5RF0QdPnij+kOMgOnr4u0g7fzAQlyu/abyepRM7J16MfpSKPy3l4A1IumpzKZVz 7nHMaao/h/jD/BRwgXpefFm9Ww6YOtOasMFmk= Received: by 10.227.176.72 with SMTP id bd8mr3068818wbb.196.1301255374128; Sun, 27 Mar 2011 12:49:34 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id b20sm1623221wbb.33.2011.03.27.12.49.32 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 27 Mar 2011 12:49:32 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: encrypted email (gentoo-windows) Date: Sun, 27 Mar 2011 20:49:43 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.36-gentoo-r5; KDE/4.4.5; x86_64; ; ) References: <201103271211.27870.michaelkintzios@gmail.com> In-Reply-To: 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-Type: multipart/signed; boundary="nextPart1341329.lBMJ9nj2Z9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201103272049.54122.michaelkintzios@gmail.com> X-Archives-Salt: X-Archives-Hash: c6b74c040ebbaaacbfa231a4f423dfff --nextPart1341329.lBMJ9nj2Z9 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Sunday 27 March 2011 15:48:53 James wrote: > Mick gmail.com> writes: > > Google has many examples and step-by-step instructions for configuring > > Outlook to use SSL Certs (S/MIME), usually by the purveyors of all these > > expensive certificate services: > >=20 > > http://www.globalsign.com/support/personal-certificate/per_outlook07.ht= ml >=20 > Hello Mick, >=20 > Exactly what I was looking for. Not just the part I included, but > your entire answer. Gmane get'[s fussy about including too much > previous text in responses. Sure, I've set up numerous email clients, > like Thunderbird and such on doze systems before (encryption or not); > that's a no-brainer. Outlook in a rigid corporate environment without the > admin's help on that side..... interesting. If their spam filters > are too aggressive, it will most likely quarantine the incoming encrypted > files. A program of encryption, but makes files look like text to > spam filters, would be keen, but most likely crackable, due to the > limited char_set? Never tried this but hey, there is ALWAYS a way > to "skin the cat"....... >=20 > But I have never tried to help an ordinary Outlook user get encryption > working, so as to exchange encrypted email, with their linux bretheran > without their Admin's involvement. Most admins at corps do not care, but > they are understaffed and only support what they support. So you have > articulated some options where I can help a generic corporate user setup > and use encryption, without their admin's involvement, which I guess is > what I did not clearly explain in previous posts, as the goal all along, > using Outlook or other > MS based applications. >=20 > THANKS; for sharing your knowledge and view of the landscape. > I've got it from here. Glad I could help James. :-) Before you start helping remotely MSWindows users I recommend you install=20 MSWindows in a virtual machine (e.g. virtualbox-bin will take only a few=20 minutes) and configure the OS and mail client to send and receive=20 signed/encrypted messages as preferred. Otherwise, you may quickly run=20 aground when the corporate users technical knowledge stops them configuring= =20 their machines as necessary. PS. Some corporate set ups will have the MS Windows SSL certificate store= =20 settings access blocked for normal users. In that case only MSWindows=20 recognised S/MIME Root CAs will be usable without warnings. As far as I=20 recall Comodo is recognised. =2D-=20 Regards, Mick --nextPart1341329.lBMJ9nj2Z9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk2PlOIACgkQVTDTR3kpaLbJHgCg8TvgJldpcjtm+Njp8mFufhCG 1X4AnRWHNag2Hfz0+JsIP3bMx5pj7Ris =inb+ -----END PGP SIGNATURE----- --nextPart1341329.lBMJ9nj2Z9--