--On Saturday, June 22, 2002 02:36:44 PM +0200 Neil Blakey-Milner
<[EMAIL PROTECTED]> wrote:
>> There is always the option
>> to use SSL, which is my preference, but unfortunately neither SSL nor
>> SASL have widespread IMAP client support yet.
>
> Most IMAP clients I know of support SSL. Outl
On Sat, Jun 22, 2002 at 02:36:44PM +0200, Neil Blakey-Milner wrote:
> On Sat 2002-06-22 (00:06), Chris Dillon wrote:
> > There is always the option
> > to use SSL, which is my preference, but unfortunately neither SSL nor
> > SASL have widespread IMAP client support yet.
>
> Most IMAP clients I k
Lyndon Nerenberg wrote:
> Terry> Personally, I think SASL should have specified that you
> Terry> crypt(3) the passwords, and then use the resulting hash as
> Terry> the password value for the shared secret on both ends. At
> Terry> least that way, you would not have to pass clear
On Sat, 22 Jun 2002, Neil Blakey-Milner wrote:
> On Sat 2002-06-22 (00:06), Chris Dillon wrote:
> > Yes, but this is the case with any IMAP server and doesn't really
> > have anything to do with Cyrus in particular. Unlike other IMAP
> > servers, however, Cyrus supports SASL which offers plenty
> "Terry" == Terry Lambert <[EMAIL PROTECTED]> writes:
Terry> Personally, I think SASL should have specified that you
Terry> crypt(3) the passwords, and then use the resulting hash as
Terry> the password value for the shared secret on both ends. At
Terry> least that way, you
On Sat 2002-06-22 (00:06), Chris Dillon wrote:
> Yes, but this is the case with any IMAP server and doesn't really have
> anything to do with Cyrus in particular. Unlike other IMAP servers,
> however, Cyrus supports SASL which offers plenty of non-plain-text
> authentication options, unfortunatel
Chris Dillon wrote:
> > While I appreciate the positive support of Cyrus, I guess I need to
> > point out that this approach only works if you are willing to send
> > passwords over the wire in plaintext.
>
> Yes, but this is the case with any IMAP server and doesn't really have
> anything to do
On Fri, 21 Jun 2002, Terry Lambert wrote:
> Chris Dillon wrote:
> > On Fri, 21 Jun 2002, Terry Lambert wrote:
> > > It has functionality that can not be implemented without adding to
> > > how UNIX does things. Basically, it needs to be able to hook the
> > > account constructor/destructor.
> >
Terry Lambert wrote:
> Chris Dillon wrote:
> > It's quite simple to integrate Cyrus IMAP with the local system.
> > Cyrus will by default use the system password database for its
> > authentication,
>
> While I appreciate the positive support of Cyrus, I guess I need
> to point out that this appr
Chris Dillon wrote:
> On Fri, 21 Jun 2002, Terry Lambert wrote:
> > It has functionality that can not be implemented without adding to
> > how UNIX does things. Basically, it needs to be able to hook the
> > account constructor/destructor.
>
> It's quite simple to integrate Cyrus IMAP with the l
On Fri, 21 Jun 2002, Terry Lambert wrote:
> It has functionality that can not be implemented without adding to
> how UNIX does things. Basically, it needs to be able to hook the
> account constructor/destructor.
It's quite simple to integrate Cyrus IMAP with the local system.
Cyrus will by defa
Lamont Granquist wrote:
> > > Cyrus imapd is a real pain in the ass to administer local user accounts
> > > with though.
> >
> > You mean that it doesn't integrate well with the UNIX credentials
> > system. THe issue here is that Cyrus needs to be able to hook
> > create/delete actions on account
On Thu, 20 Jun 2002, Terry Lambert wrote:
> Lamont Granquist wrote:
> > Cyrus imapd is a real pain in the ass to administer local user accounts
> > with though.
>
> You mean that it doesn't integrate well with the UNIX credentials
> system. THe issue here is that Cyrus needs to be able to hook
Lamont Granquist wrote:
> Cyrus imapd is a real pain in the ass to administer local user accounts
> with though.
You mean that it doesn't integrate well with the UNIX credentials
system. THe issue here is that Cyrus needs to be able to hook
create/delete actions on accounts, and UNIX fails to pr
Cyrus imapd is a real pain in the ass to administer local user accounts
with though. The cyradm program is extremely deficient. Its great if you
want to offer people imap e-mail without offering them shell access. For
local access, though, there's a higher administrative overhead. I'm back
to
Jason Andresen wrote:
> "Brandon D. Valentine" wrote:
> > On Tue, 18 Jun 2002, Darren Pilgrim wrote:
> > >It's not exactly FreeBSD, but how about rewriting pine and uw-imap?
> > >Last I heard they could use a little work.
> >
> > It would have to be a complete reimplementation thanks to the retard
16 matches
Mail list logo
