Dennis Leist | 1 May 18:59 2004
Picon

kolab_bootstrap -b with auth troubles

Hi everbody,

First of all. THX for ur feedback concrning kolab and kernel 2.6.
Installation of the src-packages (downloaded two days ago) succeeded 
without errs.

The bootstrap script ended up with the following errors:

<snip>
Please enter Hostname [kolab.mpg-intern.net]:
proceeding with Hostname kolab.mpg-intern.net
Please enter your Maildomain [mpg-intern.net]:mpg-intern.net
proceeding with Maildomain mpg-intern.net
prepare LDAP database...
kill running slapd (if any)
temporarily start slapd
no dc=kolab,dc=mpg-intern,,dc=net object found, creating one
failed to write basedn entry : modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 171, <DATA> line 283.
no kolab config object in ldap, generating a reasonable default
mynetworkinterfaces: 127.0.0.0/8
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 226, <DATA> line 283.
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 234, <DATA> line 283.
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 242, <DATA> line 283.
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 251, <DATA> line 283.
failed to write entry: modifications require authentication at 
(Continue reading)

Dennis Leist | 4 May 14:15 2004
Picon

kolab_bootstrap -b with auth troubles

Hi everbody,

First of all. THX for ur feedback concrning kolab and kernel 2.6.
Installation of the src-packages (downloaded two days ago) succeeded 
without errs.

The bootstrap script ended up with the following errors:

<snip>
Please enter Hostname [kolab.mpg-intern.net]:
proceeding with Hostname kolab.mpg-intern.net
Please enter your Maildomain [mpg-intern.net]:mpg-intern.net
proceeding with Maildomain mpg-intern.net
prepare LDAP database...
kill running slapd (if any)
temporarily start slapd
no dc=kolab,dc=mpg-intern,,dc=net object found, creating one
failed to write basedn entry : modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 171, <DATA> line 283.
no kolab config object in ldap, generating a reasonable default
mynetworkinterfaces: 127.0.0.0/8
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 226, <DATA> line 283.
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 234, <DATA> line 283.
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 242, <DATA> line 283.
failed to write entry: modifications require authentication at 
/kolab/etc/kolab/kolab_bootstrap line 251, <DATA> line 283.
failed to write entry: modifications require authentication at 
(Continue reading)

Martin Konold | 4 May 23:33 2004
Picon

Re: kolab_bootstrap -b with auth troubles

Am Tuesday 04 May 2004 02:15 pm schrieb Dennis Leist:

Hi Dennis,

This looks strange to me with regards to the hostnames used.

> Please enter Hostname [kolab.mpg-intern.net]:
> Please enter your Maildomain [mpg-intern.net]:mpg-intern.net
> no dc=kolab,dc=mpg-intern,,dc=net object found, creating one

> failed to write entry: modifications require authentication at

> generate self-signed certificate for hostname
> kolab.mpg-intern.music-pool.net... done

So which are your real hostnames and what is your real mail domain. Are the 
above names correct in your DNS?

Regards,
-- martin

Dipl.-Phys. Martin Konold

e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Nobelstrasse 15, 70569 Stuttgart, Germany
fon: 0711 67400963, fax: 0711 67400959
email: martin.konold <at> erfrakon.de
Martin Konold | 4 May 23:37 2004
Picon

Re: kolab ready to with Kernel 2.6.5-8.26 (SuSE 9.1)?

Am Wednesday 28 April 2004 01:20 pm schrieb Thomas Lotterer:

Hi,

> like apache, postfix, imapd etc. have little if any relationship to the
> kernel (keep in mind they run on non-Linux OSs as well).

Today it just came to my attention that Kolab 1.0.x does not bootstrap on a 
SUSE 9.1 with the provided SUSE 9.1 kernel-2.6. Downgrading to kernel 2.4.21 
helped. 

The reason seems to be the outdated rpm in Kolab 1.0.x which uses a different 
incompatible O_DIRECT semantic with the db.

Yours,
-- martin

Dipl.-Phys. Martin Konold

e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Nobelstrasse 15, 70569 Stuttgart, Germany
fon: 0711 67400963, fax: 0711 67400959
email: martin.konold <at> erfrakon.de
Thomas Lotterer | 5 May 08:42 2004

Re: kolab ready to with Kernel 2.6.5-8.26 (SuSE 9.1)?

On Tue, May 04, 2004, Martin Konold wrote:

> Am Wednesday 28 April 2004 01:20 pm schrieb Thomas Lotterer:
> 
> > like apache, postfix, imapd etc. have little if any relationship to the
> > kernel (keep in mind they run on non-Linux OSs as well).
> 
> Today it just came to my attention that Kolab 1.0.x does not          
> bootstrap on a SUSE 9.1 with the provided SUSE 9.1 kernel-2.6.        
> Downgrading to kernel 2.4.21 helped.                                  
> 
> The reason seems to be the outdated rpm in Kolab 1.0.x which uses a
> different incompatible O_DIRECT semantic with the db.
> 
This should not be a problem with the kolab package from OpenPKG 2.0.
I remember we debugged this issue down into the kernel sources to find
out O_DIRECT is fully broken in 2.2 and 2.4 kernels. We found out that
RedHat completely ignores this flag to make software work. According to
the HISTORY [1] OpenPKG was patched on 15-Sep-2003, see [2] and read the
comment around O_DIRECT there.

Anyway we'll check this as soon as SuSE 9.1 is availabe for download
which I'm checking for bidaily.

[1] http://cvs.openpkg.org/getfile?f=openpkg-src/openpkg/HISTORY
[2] http://cvs.openpkg.org/chngview?cn=12237

--
Thomas.Lotterer <at> cw.com, Cable & Wireless
(Continue reading)

Martin Konold | 5 May 09:08 2004
Picon

Re: kolab ready to with Kernel 2.6.5-8.26 (SuSE 9.1)?

Am Wednesday 05 May 2004 08:42 am schrieb Thomas Lotterer:

Hi Thomas,

> This should not be a problem with the kolab package from OpenPKG 2.0.
> I remember we debugged this issue down into the kernel sources to find
> out O_DIRECT is fully broken in 2.2 and 2.4 kernels. We found out that
> RedHat completely ignores this flag to make software work. According to
> the HISTORY [1] OpenPKG was patched on 15-Sep-2003, see [2] and read the
> comment around O_DIRECT there.

Yes, your analysis is very much correct though the sources for Kolab 1.0.x as 
distributed by erfrakon show this problem.

Yours,
-- martin

Dipl.-Phys. Martin Konold

e r f r a k o n
Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker
Nobelstrasse 15, 70569 Stuttgart, Germany
fon: 0711 67400963, fax: 0711 67400959
email: martin.konold <at> erfrakon.de
angel_azrael | 5 May 15:42 2004
Picon
Picon

db-definition for ldap with postgres backend

Hi,

has anybody a db-definition and a install howto to build an slapd with 
postgres backend and schemes for kolab?

Thanks
Thomas Lotterer | 5 May 16:32 2004

[OpenPKG-SA-2004.019] OpenPKG Security Advisory (kolab) (Was: Re: Possible Kolab LDAP configuration information disclosure)

On Mon, Apr 26, 2004, Thomas Lotterer wrote:
> On Wed, Apr 21, 2004, Bernhard Reiter wrote:
> > On Wednesday 21 April 2004 09:19, Thomas Lotterer wrote:
> > 
> > > A simple and still close to solution approach is to protect the
> > > storage from being read by unauthorized persons. Which should be
> > > done.
> > 
> > Would you mind adding an item to the issue tracker for this?
> > 
> https://intevation.de/roundup/kolab/issue88
> 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

________________________________________________________________________

OpenPKG Security Advisory                            The OpenPKG Project
http://www.openpkg.org/security.html              http://www.openpkg.org
openpkg-security <at> openpkg.org                         openpkg <at> openpkg.org
OpenPKG-SA-2004.019                                          05-May-2004
________________________________________________________________________

Package:             kolab
Vulnerability:       information leakage, privilege escalation
OpenPKG Specific:    no

Affected Releases:   Affected Packages:           Corrected Packages:
OpenPKG CURRENT      <= kolab-20040426-20040426   >= kolab-20040503-20040503
                     <= perl-kolab-5.8.4-20040503 >= perl-kolab-5.8.4-20040505
(Continue reading)

NicoiT | 5 May 18:06 2004
Picon

free/busy info

Hi! 
I'm getting this when I try to get the free/busy information using kmail.
I cant find errors in the logs or anything that point's me the problem. Is
there a known problem about this or anybody knows how to sort it?

in Kmail
The software could not upload your free/busy list to the URL
webdavs://user <at> warp.globant.com <at> localhost/freebusy/user.vfb. There might be a
problem with the access rights, or you specified an incorrect URL. The system
said: Unknown proxy host webcache.
Please check the URL or contact your system administrator.

in the kmail's debug 
libkcal: icalformatimpl: writeFreeBusy: startDate: Wed May 5 2004: 9:54:17 am
End Date: Sun July 4 2004: 9:54:17 am
kio_http: (11197) ============ Sending Header:
kio_http: (11197) CONNECT localhost:443 HTTP/1.0
kio_http: (11197) User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux)
kio_http: (11197) Host: localhost
kio (KIOJob): error 45 webcache

Thanks for your time
Cheers Nicolas.
Jon Bendtsen | 5 May 22:20 2004
Picon

Re: [OpenPKG-SA-2004.019] OpenPKG Security Advisory (kolab) (Was: Re: Possible Kolab LDAP configuration information disclosure)

I dont understand how serious this is. Can an remote attacker gain 
access?

JonB

Gmane