Is public free/busy information useful?

[Cornelius Hald]

Thanks for the detailed information! So I'll restrict access to that URL
to internal users only. Good to know I won't break any other clients.

Also thanks for adjusting the upcoming default configuration. Always
good for new users to have a nice default configuration.

Cheers,
Conny

On Tue, 2015-02-24 at 22:27 +0000, Daniel Hoffend wrote:
> Update:
> 
> you've 2 options:
> 
> 1) configure apache to limit your freebusy configuration
> 
> 2) configure freebusy to add authentication/trustednetworks
> 
> You might wanna take a look on the default configuration
> http://git.kolab.org/kolab-freebusy/tree/doc/kolab-freebusy.config.ini
> 
> A short test tells me that a combination of (httpauth + trustednetworks 
> (localhost + server ip) worked for me.
> 
> I've updated the setup_freebusy component so freebusy will be 
> autoconfigured this way with kolab 3.4.
> 
> --
> Regards
> Daniel
> 
> ------ Originalnachricht ------
> Von: "Daniel Hoffend" <dh at dotlan.net>
> An: "Cornelius Hald" <hald at icandy.de>; "Kolab Mailinglist" 
> <users at lists.kolab.org>
> Gesendet: 24.02.2015 18:02:41
> Betreff: Re: Is public free/busy information useful?
> 
> >Hi Conny
> >
> >You're free to limit the access to the /freebusy url using allow/deny 
> >in the apache2 configuration. I guess it's useful to open the freebusy 
> >url to organizations that are linked together to share freebusy 
> >informations.
> >
> >It's up for discussion if we should limit it to localhost only in the 
> >default installation or keep it that way (was easier to debug stuff in 
> >the beginning). Securing your services is a complete section on its 
> >own.
> >
> >--
> >Regards
> >Daniel
> >
> >
> >
> >------ Originalnachricht ------
> >Von: "Cornelius Hald" <hald at icandy.de>
> >An: "Kolab Mailinglist" <users at lists.kolab.org>
> >Gesendet: 24.02.2015 12:10:33
> >Betreff: Is public free/busy information useful?
> >
> >>Hi,
> >>
> >>I was just wondering whether or not it is a good idea that the 
> >>free/busy
> >>URL is accessible from everywhere.
> >>
> >>As far as I understand the Roundcube calendar is using it to check
> >>whether or not invited people and resources are free or busy. But is
> >>there also something like a internet standard that defines how other
> >>calendar clients resolve that URL? So that Evolution, Outlook, etc.
> >>could query that information as well?
> >>
> >>If not, that URL should probably be only readable by roundcube, right?
> >>
> >>Thanks!
> >>Conny
> >>
> >>_______________________________________________
> >>users mailing list
> >>users at lists.kolab.org
> >>https://lists.kolab.org/mailman/listinfo/users