From bernhard at intevation.de Wed Apr 7 21:50:47 2004 From: bernhard at intevation.de (Bernhard Reiter) Date: Wed, 7 Apr 2004 21:50:47 +0200 Subject: [Kolab-announce] Proko2 is Good News Towards Kolab2 Message-ID: <20040407195047.GA10528@intevation.de> Dear Members of the Kolab-Community, "Proko2" is Good News: We can go towards Kolab2! The companies Klar?lvdalens Datakonsult AB, Erfrakon PartG and Intevation GmbH have a new contract to deliver an advanced groupware solution. "Proko2" (Project for Kolab2) is our code name for it. Though we cannot name our customers, we will work with the community: * publish technical details about Proko2. * release our code as Free Software. * contribute to the Kolab project. We envision to go for Kolab2. When we started Kolab1 there was no community; now our group now is part of one. Proko2 has the highest priority for us and we want to handle involved interests openly. By taking the lead for Kolab2 we set out to create a consistent groupware solution with good quality. Anyone who wants to join and help pursing that goal is welcome! We suggest that www.kolab.org will be the site driven by the community. Separate web pages will document the contracts (Kroupware, Proko2). Ideally www.kolab.org becomes first place to go for information about Kolab. Current structure of the Kolab Project is threefold: 1) Kolab Specification 2) Server 3) Client a) KDE b) Windows c) Web Kolab was founded on the results of the now-finished "Kroupware" contract. The architecture document became the Kolab1 specification. Implementations are there for 2) (Kolab1 Server) and 3a) (KDE Kolab1 Client). For 3b) there was the combination of OL2000 and Bynari v1 Plugin. With Kolab1 it was impossible to work on the same calender folder with both clients due to incompatible storage formats. What are our plans for Proko2? Make Kontact to be able to act as the KDE client. Come up with a Windows client option that can fully interact on the same data as the KDE Kolab2 client. In order to reach that goal we want to propose a common format that can be implemented by Outlook Plugins. Access control lists, groups, shared folders, multiple accounts in one client and facilities to see overview calenders shall enable delegation szenarios (secretary-boss) and projects group collaboration. Client convenience functions like: Better out-of-office messages and intelligent removal of outdated items. On the server side we also plan to add: * a virus filter, * user quotas, * more email aliases and email sending control, * the possibility that other LDAP servers can be used, * a multi location capabilities. Naturally we aim for making Proko2 production ready and supportable in German. This includes fixing bugs, enhancing usability, writing documentation and have internationalisation. For all that we will propose a Kolab2 specification. Towards creating a great Free Software groupware solution: Give us your feedback! Bernhard Reiter, April the 7nd, 2004 Proko2 Coordinator -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-announce/attachments/20040407/4c63e8f4/attachment.bin From thomas at intevation.de Thu Apr 29 18:14:43 2004 From: thomas at intevation.de (Thomas Arendsen Hein) Date: Thu, 29 Apr 2004 18:14:43 +0200 Subject: [Kolab-announce] Mailinglists in domain kolab.org Message-ID: <20040429161442.GA24921@intevation.de> Hi! After kolab-users at kolab.org now the other Kolab mailinglists were changed to the new domain. The old addresses @intevation.org will continue to work for some time. Please change your aliases, filter rules, mailto links etc. to: kolab-users at kolab.org kolab-devel at kolab.org kolab-announce at kolab.org kolab-commits at kolab.org The web interface URLs are: https://kolab.org/mailman/listinfo/kolab-users https://kolab.org/mailman/listinfo/kolab-devel https://kolab.org/mailman/listinfo/kolab-announce https://kolab.org/mailman/listinfo/kolab-commits Regards, Thomas Arendsen Hein -- Email: thomas at intevation.de http://intevation.de/~thomas/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-announce/attachments/20040429/082cb9d0/attachment.bin From bernhard at intevation.de Mon May 10 19:52:58 2004 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 10 May 2004 19:52:58 +0200 Subject: [Kolab-announce] Fwd: [OpenPKG-SA-2004.019] OpenPKG Security Advisory (kolab) Message-ID: <200405101952.58574.bernhard@intevation.de> Attached a security advisory for the Kolab Server. The problem affected all versions. The wrong permission problem is locally exploitable if you have local users. In addition to the OpenPGK advisory, the following rpm package is the fix for the Kolab 1.0.x engine: kolab-1.0-1.0.20.src.rpm It can be found an the usual download place listed at http://kroupware.org/howto-kolab.html -------------- next part -------------- An embedded message was scrubbed... From: Thomas Lotterer Subject: [OpenPKG-SA-2004.019] OpenPKG Security Advisory (kolab) (Was: Re: Possible Kolab LDAP configuration information disclosure) Date: Wed, 5 May 2004 16:32:38 +0200 Size: 7502 Url: http://kolab.org/pipermail/kolab-announce/attachments/20040510/ee1bf9d6/attachment.txt -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2145 bytes Desc: signature Url : http://kolab.org/pipermail/kolab-announce/attachments/20040510/ee1bf9d6/smime.bin From bernhard at intevation.de Mon May 10 20:26:48 2004 From: bernhard at intevation.de (Bernhard Reiter) Date: Mon, 10 May 2004 20:26:48 +0200 Subject: [Kolab-announce] Fwd: [OpenPKG-SA-2004.019] In-Reply-To: <200405101952.58574.bernhard@intevation.de> References: <200405101952.58574.bernhard@intevation.de> Message-ID: <20040510182648.GB1291@intevation.de> On Mon, May 10, 2004 at 07:52:58PM +0200, Bernhard Reiter wrote: > Attached a security advisory for the Kolab Server. > The problem affected all versions. > The wrong permission problem is locally exploitable > if you have local users. > > In addition to the OpenPGK advisory, > the following rpm package is the fix for the Kolab 1.0.x engine: > kolab-1.0-1.0.20.src.rpm > It can be found an the usual download place listed > at http://kroupware.org/howto-kolab.html In case you know what S/MIME signatures are: My signatures was broken by the list manager on the cited email. A freshly discovered mailman bug#[815297]. If you manually want to check the signature, add another space between those three lines in the forwarded mail headers: > X-KMail-EncryptionState: > X-KMail-SignatureState: > X-KMail-MDN-Sent: Bernhard -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://kolab.org/pipermail/kolab-announce/attachments/20040510/f64ae51d/attachment.bin