Re: dothack and cyrus 2.0.16
> There might be a little bit of pain involved for large sites to migrate > to IMAP 2.1/SASL 2.x, but there aren't any showstoppers that I'm aware > of. > > If CMU can do it (and yes, they are using Sendmail 8.12.x with SMTP > AUTH), then any site should be able to do it. I have asked several times on the list, and nobody has told us of a way to handle the dual environment using the sasldb as the database. -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc.
Re: dothack and cyrus 2.0.16
> I'll take a shot at it (it being an interim tool). Is this basically > what people are looking for? > > a saslpasswd that does it's operations on both /etc/sasldb (old sasl) > and /etc/sasldb2 (new sasl) Yeppers. > a sasldblistusers that will list from either Not so important for us, and may be very confusing. I would say #1 has priority, because we can teach the admins how to query both. > a saslconv to convert from one to the other <- this would be a no go if > the data encryption changed (not just stored different) Yeppers. -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc.
RE: dothack and cyrus 2.0.16
Hi: The 2.0.15 HIERSEP-r2 patch is function perfectly (thanks Simon !!) Yesterday I did some tests to this "patched cyrus" and works as expected... Regards Enric Ramos > -Mensaje original- > De: Jeremy Howard [mailto:[EMAIL PROTECTED]] > Enviado el: martes, 29 de enero de 2002 21:45 > Para: Joe Rhett > CC: [EMAIL PROTECTED]; Ken Murchison > Asunto: Re: dothack and cyrus 2.0.16 > > > Joe Rhett wrote: > > Maybe, but in forcing the new SASL you've raised the entry > bar too high > for > > any production configuration to join. Your baby might be > born, but she's > > on the moon and we have no spaceships to get there yet. > > > Ken's scratched his itch. He wanted hier-sep so he wrote it, > and he merged > it into 2.1. Good on him for sharing the code with the rest of us. :-) > > If you want the code merged into another version, then go > ahead and do it. > There's already a 2.0.15 version around (apparently missing > one header file, > which will have to be dug up from somewhere). I'll even host > the updated > patch on the Cyrus-utils project if you send it to me. These > things don't > get written unless someone who wants it, writes it... > > >
Re: dothack and cyrus 2.0.16
Jeremy Howard wrote: > > Ken Murchison wrote: > > There might be a little bit of pain involved for large sites to migrate > > to IMAP 2.1/SASL 2.x, but there aren't any showstoppers that I'm aware > > of. > > > > If CMU can do it (and yes, they are using Sendmail 8.12.x with SMTP > > AUTH), then any site should be able to do it. > > > Could you tell us a little more about that experience? How is CMU set up? 2 > separate SASL libraries (one of each version)? How is sasldb handled between > the 2, if at all? What are the main sources of pain likely to be seen in the > upgrade, and how can they be mitigated? I can't speak for CMU, since I'm not employed there, and wasn't involved with the upgrade. Larry and/or Rob would be the ones to describe their upgrade process. As for my experience, I was, and have been, running SASL v1.5.x (Sendmail) and SASL 2.x (IMAP) concurrently on my production server (which is also my dev box) since before IMAP 2.1 was released. Since I don't need sasldb (none of my clients use anything other than PLAIN/LOGIN), I am using the same PAM module for both libraries. SASL v1.5 talks directly to PAM, and SASL v2.x uses saslauthd). If you don't need sasldb, or don't have a large number of clients which used shared secret mechs, this is a trivial config. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: dothack and cyrus 2.0.16
On Tue, 29 Jan 2002, Eric Estabrooks wrote: > a saslconv to convert from one to the other <- this would be a no go if > the data encryption changed (not just stored different) This exists.. it's the dbconverter-2 utility that is included in the SASLv2 distribution. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 235 * 412-CMU-TREK Research Systems Programmer * /usr/contributed Gatekeeper
Re: dothack and cyrus 2.0.16
I'll take a shot at it (it being an interim tool). Is this basically what people are looking for? a saslpasswd that does it's operations on both /etc/sasldb (old sasl) and /etc/sasldb2 (new sasl) a sasldblistusers that will list from either a saslconv to convert from one to the other <- this would be a no go if the data encryption changed (not just stored different) Eric
Re: dothack and cyrus 2.0.16
Ken Murchison wrote: > There might be a little bit of pain involved for large sites to migrate > to IMAP 2.1/SASL 2.x, but there aren't any showstoppers that I'm aware > of. > > If CMU can do it (and yes, they are using Sendmail 8.12.x with SMTP > AUTH), then any site should be able to do it. > Could you tell us a little more about that experience? How is CMU set up? 2 separate SASL libraries (one of each version)? How is sasldb handled between the 2, if at all? What are the main sources of pain likely to be seen in the upgrade, and how can they be mitigated?
Re: dothack and cyrus 2.0.16
Joe Rhett wrote: > Maybe, but in forcing the new SASL you've raised the entry bar too high for > any production configuration to join. Your baby might be born, but she's > on the moon and we have no spaceships to get there yet. > Ken's scratched his itch. He wanted hier-sep so he wrote it, and he merged it into 2.1. Good on him for sharing the code with the rest of us. :-) If you want the code merged into another version, then go ahead and do it. There's already a 2.0.15 version around (apparently missing one header file, which will have to be dug up from somewhere). I'll even host the updated patch on the Cyrus-utils project if you send it to me. These things don't get written unless someone who wants it, writes it...
Re: dothack and cyrus 2.0.16
Jeremy Howard wrote: > > Joe Rhett wrote: > > Maybe, but in forcing the new SASL you've raised the entry bar too high > for > > any production configuration to join. Your baby might be born, but she's > > on the moon and we have no spaceships to get there yet. > > > Ken's scratched his itch. He wanted hier-sep so he wrote it, and he merged > it into 2.1. Good on him for sharing the code with the rest of us. :-) Not entirely true. I didn't want it, but I knew that other people did. I also knew that by leveraging the altnamespace work (which I was getting paid for), this would be fairly trivial add-on. There might be a little bit of pain involved for large sites to migrate to IMAP 2.1/SASL 2.x, but there aren't any showstoppers that I'm aware of. If CMU can do it (and yes, they are using Sendmail 8.12.x with SMTP AUTH), then any site should be able to do it. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
RE: dothack and cyrus 2.0.16
On Tue, 2002-01-29 at 15:08, Ramiro Morales wrote: > Enric, > > Are you sure? > > I see the imap/namespace.h file at line 10858 in Simon's patch I screwed up he was right , I just put a new vversion up I didnt realised he had my patch to start iwth. but ive fixed it all now (should have CC list) -- Simon
RE: dothack and cyrus 2.0.16
Enric, Are you sure? I see the imap/namespace.h file at line 10858 in Simon's patch So patch should be creating it. diff was run with the -N switch so it interpret new files in one dir as inexistent file with the same name in the other dir) Maybe you are using a patch not from GNU? BTW: Simon, nice site, the patches are really interesting. I will consider some of them for a future release of my Red Hat rpms of Cyrus (It will take time to create/test a cyrus SASL 2.1.x package and after that a Cyrus IMPAd 2.1.1 package so I will stick with 2.0.16 by now) On 29 Jan 2002 at 9:28, Enric Ramos wrote about "RE: dothack and cyrus 2.0.16": Subject: RE: dothack and cyrus 2.0.16 Date sent: Tue, 29 Jan 2002 09:28:45 +0100 From: "Enric Ramos" <[EMAIL PROTECTED]> To: "simon" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> } } Thanks Simon. } This is tha patch I tested yesterday... } } ... } } But I have the same problem mentioned before... } When I apply this patch, it includes references to "namespace.h" and } this file doesn't exists in cyrus distribution... } } Ken: } } Thanks for you suggestion. } } } Enric Ramos } Network & System Specialyst } Atlas Internet Solutions } [EMAIL PROTECTED] } } } > -Mensaje original- } > De: simon [mailto:[EMAIL PROTECTED]] } > Enviado el: lunes, 28 de enero de 2002 23:28 } > Para: [EMAIL PROTECTED] } > Asunto: Re: dothack and cyrus 2.0.16 } > } > } > On Mon, 2002-01-28 at 21:38, Ken Murchison wrote: } > > } > > } > > Joe Rhett wrote: } > > > } > > > Any chance one of you could do this so that the branch is } > validated and up } > > > to date, please? } > } > Briref note I have a patch for this (taken from the cvs ) at:- } > } > http://www.surf.org.uk/downloads/HIERSEP-r2.patch } > } > -- } > Simon Loader } > } > } -- Ramiro
Re: dothack and cyrus 2.0.16
> There is no further development on any branches other than HEAD at this > time (um, well, Rob is working on some sieve byte-code stuff but this is > limited to a small set of files, even though he's working on a branch). > > Unfortunately, I don't have the time, inclination or desire to port the > hier-sep. The intent of putting this functionality into v2.1 was to try > to get people who want/need this feature to upgrade (just like the TLS > caching code, SQUAT indexing, etc). If there is a need/want for this, > someone who hasn't already upgraded will have to do the port. Maybe, but in forcing the new SASL you've raised the entry bar too high for any production configuration to join. Your baby might be born, but she's on the moon and we have no spaceships to get there yet. -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc.
RE: dothack and cyrus 2.0.16
Thanks Simon. This is tha patch I tested yesterday... ... But I have the same problem mentioned before... When I apply this patch, it includes references to "namespace.h" and this file doesn't exists in cyrus distribution... Ken: Thanks for you suggestion. Enric Ramos Network & System Specialyst Atlas Internet Solutions [EMAIL PROTECTED] > -Mensaje original- > De: simon [mailto:[EMAIL PROTECTED]] > Enviado el: lunes, 28 de enero de 2002 23:28 > Para: [EMAIL PROTECTED] > Asunto: Re: dothack and cyrus 2.0.16 > > > On Mon, 2002-01-28 at 21:38, Ken Murchison wrote: > > > > > > Joe Rhett wrote: > > > > > > Any chance one of you could do this so that the branch is > validated and up > > > to date, please? > > Briref note I have a patch for this (taken from the cvs ) at:- > > http://www.surf.org.uk/downloads/HIERSEP-r2.patch > > -- > Simon Loader > >
Re: dothack and cyrus 2.0.16
On Mon, 2002-01-28 at 21:38, Ken Murchison wrote: > > > Joe Rhett wrote: > > > > Any chance one of you could do this so that the branch is validated and up > > to date, please? Briref note I have a patch for this (taken from the cvs ) at:- http://www.surf.org.uk/downloads/HIERSEP-r2.patch -- Simon Loader
Re: dothack and cyrus 2.0.16
Joe Rhett wrote: > > Any chance one of you could do this so that the branch is validated and up > to date, please? There is no further development on any branches other than HEAD at this time (um, well, Rob is working on some sieve byte-code stuff but this is limited to a small set of files, even though he's working on a branch). Unfortunately, I don't have the time, inclination or desire to port the hier-sep. The intent of putting this functionality into v2.1 was to try to get people who want/need this feature to upgrade (just like the TLS caching code, SQUAT indexing, etc). If there is a need/want for this, someone who hasn't already upgraded will have to do the port. > This is your baby :-} Yup, and she's already born! > > On Mon, Jan 28, 2002 at 04:05:54PM -0500, Ken Murchison wrote: > > If you *REALLY* need this functionality for 2.0.16, I'd suggest doing > > this via CVS. Grab the 'hier-sep' branch and the merge the > > 'cyrus-release-2-0-16' tag. > > > > Ken > > > > > > > > Enric Ramos wrote: > > > > > > Hi. > > > > > > Firstofall thanks for your help... > > > I've found the HIERSEP-r2.patch for cyrus-imapd-2.0.15.. > > > > > > Unfortunately, after apply this patch it includes references into > > > imapd.c,master.c etc... to namespace.h file... > > > I havn't got this file anywhere, and obviosly, afetr applying this patch > > > cyrus doesn't compile... > > > > > > Do you know where could I find this file (namespace.h) ?? > > > > > > I have search in 2.0.16,2.1.1,2.0.15... but this file doesn't exists... > > > > > > Thsnks ! > > > > > > Enric > > > > > > > -Mensaje original- > > > > De: Jeremy Howard [mailto:[EMAIL PROTECTED]] > > > > Enviado el: sábado, 26 de enero de 2002 8:22 > > > > Para: Joe Rhett > > > > CC: Enric Ramos; [EMAIL PROTECTED] > > > > Asunto: Re: dothack and cyrus 2.0.16 > > > > > > > > > > > > > > > We are locking for "dothack" patch in order to be able to create > > > > logins > > > > > > > with dots... > > > > > > > > > > > > > The alternate separator patch is incorporated into 2.1, > > > > which provides > > > > the > > > > > > same functionality. > > > > > > > > > > Yes, yes, but 2.1 requires the new SASL and all those > > > > problems. Since the > > > > > 'final answer' is "stick with 2.0 until all the other > > > > applications are > > > > > updated" then you need to keep supporting 2.0. > > > > > > > > > Well then search for "althier" on google. There's a 2.0.15 > > > > patch floating > > > > around. > > > > > > > > > > > > -- > > Kenneth Murchison Oceana Matrix Ltd. > > Software Engineer 21 Princeton Place > > 716-662-8973 x26 Orchard Park, NY 14127 > > --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp > > -- > Joe Rhett Chief Geek > [EMAIL PROTECTED] ISite Services, Inc. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Re: dothack and cyrus 2.0.16
Any chance one of you could do this so that the branch is validated and up to date, please? This is your baby :-} On Mon, Jan 28, 2002 at 04:05:54PM -0500, Ken Murchison wrote: > If you *REALLY* need this functionality for 2.0.16, I'd suggest doing > this via CVS. Grab the 'hier-sep' branch and the merge the > 'cyrus-release-2-0-16' tag. > > Ken > > > > Enric Ramos wrote: > > > > Hi. > > > > Firstofall thanks for your help... > > I've found the HIERSEP-r2.patch for cyrus-imapd-2.0.15.. > > > > Unfortunately, after apply this patch it includes references into > > imapd.c,master.c etc... to namespace.h file... > > I havn't got this file anywhere, and obviosly, afetr applying this patch > > cyrus doesn't compile... > > > > Do you know where could I find this file (namespace.h) ?? > > > > I have search in 2.0.16,2.1.1,2.0.15... but this file doesn't exists... > > > > Thsnks ! > > > > Enric > > > > > -Mensaje original----- > > > De: Jeremy Howard [mailto:[EMAIL PROTECTED]] > > > Enviado el: sábado, 26 de enero de 2002 8:22 > > > Para: Joe Rhett > > > CC: Enric Ramos; [EMAIL PROTECTED] > > > Asunto: Re: dothack and cyrus 2.0.16 > > > > > > > > > > > > We are locking for "dothack" patch in order to be able to create > > > logins > > > > > > with dots... > > > > > > > > > > > The alternate separator patch is incorporated into 2.1, > > > which provides > > > the > > > > > same functionality. > > > > > > > > Yes, yes, but 2.1 requires the new SASL and all those > > > problems. Since the > > > > 'final answer' is "stick with 2.0 until all the other > > > applications are > > > > updated" then you need to keep supporting 2.0. > > > > > > > Well then search for "althier" on google. There's a 2.0.15 > > > patch floating > > > around. > > > > > > > > -- > Kenneth Murchison Oceana Matrix Ltd. > Software Engineer 21 Princeton Place > 716-662-8973 x26 Orchard Park, NY 14127 > --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc.
Re: dothack and cyrus 2.0.16
If you *REALLY* need this functionality for 2.0.16, I'd suggest doing this via CVS. Grab the 'hier-sep' branch and the merge the 'cyrus-release-2-0-16' tag. Ken Enric Ramos wrote: > > Hi. > > Firstofall thanks for your help... > I've found the HIERSEP-r2.patch for cyrus-imapd-2.0.15.. > > Unfortunately, after apply this patch it includes references into > imapd.c,master.c etc... to namespace.h file... > I havn't got this file anywhere, and obviosly, afetr applying this patch > cyrus doesn't compile... > > Do you know where could I find this file (namespace.h) ?? > > I have search in 2.0.16,2.1.1,2.0.15... but this file doesn't exists... > > Thsnks ! > > Enric > > > -Mensaje original- > > De: Jeremy Howard [mailto:[EMAIL PROTECTED]] > > Enviado el: sábado, 26 de enero de 2002 8:22 > > Para: Joe Rhett > > CC: Enric Ramos; [EMAIL PROTECTED] > > Asunto: Re: dothack and cyrus 2.0.16 > > > > > > > > > We are locking for "dothack" patch in order to be able to create > > logins > > > > > with dots... > > > > > > > > > The alternate separator patch is incorporated into 2.1, > > which provides > > the > > > > same functionality. > > > > > > Yes, yes, but 2.1 requires the new SASL and all those > > problems. Since the > > > 'final answer' is "stick with 2.0 until all the other > > applications are > > > updated" then you need to keep supporting 2.0. > > > > > Well then search for "althier" on google. There's a 2.0.15 > > patch floating > > around. > > > > -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
RE: dothack and cyrus 2.0.16
Hi. Firstofall thanks for your help... I've found the HIERSEP-r2.patch for cyrus-imapd-2.0.15.. Unfortunately, after apply this patch it includes references into imapd.c,master.c etc... to namespace.h file... I havn't got this file anywhere, and obviosly, afetr applying this patch cyrus doesn't compile... Do you know where could I find this file (namespace.h) ?? I have search in 2.0.16,2.1.1,2.0.15... but this file doesn't exists... Thsnks ! Enric > -Mensaje original- > De: Jeremy Howard [mailto:[EMAIL PROTECTED]] > Enviado el: sábado, 26 de enero de 2002 8:22 > Para: Joe Rhett > CC: Enric Ramos; [EMAIL PROTECTED] > Asunto: Re: dothack and cyrus 2.0.16 > > > > > > We are locking for "dothack" patch in order to be able to create > logins > > > > with dots... > > > > > > > The alternate separator patch is incorporated into 2.1, > which provides > the > > > same functionality. > > > > Yes, yes, but 2.1 requires the new SASL and all those > problems. Since the > > 'final answer' is "stick with 2.0 until all the other > applications are > > updated" then you need to keep supporting 2.0. > > > Well then search for "althier" on google. There's a 2.0.15 > patch floating > around. > >
Re: dothack and cyrus 2.0.16
> > We are locking for "dothack" patch in order to be able to create logins > > with dots... > > > The alternate separator patch is incorporated into 2.1, which provides the > same functionality. Yes, yes, but 2.1 requires the new SASL and all those problems. Since the 'final answer' is "stick with 2.0 until all the other applications are updated" then you need to keep supporting 2.0. -- Joe Rhett Chief Geek [EMAIL PROTECTED] ISite Services, Inc.
Re: dothack and cyrus 2.0.16
> > > We are locking for "dothack" patch in order to be able to create logins > > > with dots... > > > > > The alternate separator patch is incorporated into 2.1, which provides the > > same functionality. > > Yes, yes, but 2.1 requires the new SASL and all those problems. Since the > 'final answer' is "stick with 2.0 until all the other applications are > updated" then you need to keep supporting 2.0. > Well then search for "althier" on google. There's a 2.0.15 patch floating around.
Re: dothack and cyrus 2.0.16
> We are locking for "dothack" patch in order to be able to create logins > with dots... > The alternate separator patch is incorporated into 2.1, which provides the same functionality.
