9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] upas/smtpd password authentication
Date: Mon, 17 Dec 2007 13:05:52 -0800	[thread overview]
Message-ID: <2324AE74-36F9-4BF3-B0C8-55B517EFBFFE@orthanc.ca> (raw)
In-Reply-To: <1a579fc66314c00596b0b6f99acf5fc8@quanstro.net>


On 2007-Dec-16, at 15:16 , erik quanstrom wrote:

> tls seems like something extra to break.  i have several
> dozen mac/windows users that need detailed instructions
> for every change.
>
> i'm not a security expert.  what case that i can't currently see
> would tls solve for me that's worth the extra configuration.
> what am i missing?

Starting with RFC 3516 (latest IMAP4rev1), TLS support is mandatory.  
I'm not sure what problems you're running into with clients -- I've  
rolled out TLS-aware IMAP clients to hundreds of end-users, and it's  
no more difficult than any of the other IMAP4 configuration you have  
to deal with.  For most clients these days, enabling TLS involves  
ticking off a checkbox.


  parent reply	other threads:[~2007-12-17 21:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-15  0:09 erik quanstrom
2007-12-15  0:16 ` Steve Simon
2007-12-15  0:26   ` erik quanstrom
2007-12-16 18:02     ` Russ Cox
2007-12-16 23:16       ` erik quanstrom
2007-12-17 16:54         ` Jonathan D. Proulx
2007-12-17 17:26           ` erik quanstrom
2007-12-17 18:33             ` Jonathan D. Proulx
2007-12-17 19:40           ` Wes Kussmaul
2007-12-17 17:52         ` Russ Cox
2007-12-17 21:05         ` Lyndon Nerenberg [this message]
2007-12-17 21:08           ` Lyndon Nerenberg
2007-12-17 21:10           ` erik quanstrom
2007-12-17 23:12             ` Lyndon Nerenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2324AE74-36F9-4BF3-B0C8-55B517EFBFFE@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).