Re: [gentoo-user] Re: encrypted email (gentoo-windows)

[Mick <michaelkintzios@gmail.com>]

[-- Attachment #1: Type: Text/Plain, Size: 2525 bytes --]

On Sunday 27 March 2011 15:48:53 James wrote:
> Mick <michaelkintzios <at> 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:
> > 
> > http://www.globalsign.com/support/personal-certificate/per_outlook07.html
> 
> Hello Mick,
> 
> 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".......
> 
> 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.
> 
> 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 
MSWindows in a virtual machine (e.g. virtualbox-bin will take only a few 
minutes) and configure the OS and mail client to send and receive 
signed/encrypted messages as preferred.  Otherwise, you may quickly run 
aground when the corporate users technical knowledge stops them configuring 
their machines as necessary.

PS.  Some corporate set ups will have the MS Windows SSL certificate store 
settings access blocked for normal users.  In that case only MSWindows 
recognised S/MIME Root CAs will be usable without warnings.  As far as I 
recall Comodo is recognised.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]