November 2008 - calendarserver-dev - lists.macosforge.org

Re: [CalendarServer-dev] [CalendarServer] #80: URL wrong in README
by CalendarServer 24 Nov '08

24 Nov '08

#80: URL wrong in README -------------------------------+-------------------------------------------- Reporter: njh@… | Owner: wsanchez@… Type: Defect | Status: closed Priority: 4: Nice to have | Milestone: Component: Infrastructure | Severity: Other Resolution: Software changed | Keywords: readme documentation -------------------------------+-------------------------------------------- Comment(by ygn00@…): modifications [http://www.nikeshoeswholesale.com to] existing code, you agree [http://www.nike-trainer.com by] submitting your modifications that the modifications -- Ticket URL: <http://trac.calendarserver.org/ticket/80#comment:3> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #79: Add list of system requirements
by CalendarServer 24 Nov '08

24 Nov '08

#79: Add list of system requirements ------------------------------+--------------------------------------------- Reporter: cdaboo@… | Owner: wsanchez@… Type: Defect | Status: assigned Priority: 1: Blocker | Milestone: CalendarServer-2.0 Component: Infrastructure | Severity: Other Keywords: | ------------------------------+--------------------------------------------- Comment(by ygn00@…): add a list [http://www.nikeshoeswholesale.com of] software requirements [http://www.nike-trainer.com for] the server - specifically things we assume are already installed -- Ticket URL: <http://trac.calendarserver.org/ticket/79#comment:6> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

caldav-schedulingchanges.txt
by Mark Cockfield 22 Nov '08

22 Nov '08

I think there may be an inconsistency in section 4.1.1 of caldav-schedulingchanges.txt: Description: This property SHOULD be defined on all scheduling messages that have been automatically processed by the server. If present, it contains a single CS:calendar-changes XML element. Definition: <!ELEMENT schedule-changes (dtstamp, action) > <!ELEMENT dtstamp CDATA>  <!ELEMENT action (create|update|cancel|reply)>  <!ELEMENT create EMPTY> All other references are to a schedule-changes XML element...? Regards, Mark

1 0

PyKerberos with mod_spnego.apple
by Paul Windey 21 Nov '08

21 Nov '08

Hi, When I use test.py in PyKerberos against an original Mac OS X Server running caldav it seems to works fine. (port 8008 , directory /principals/) However if I run it against the Apache 2 server shipped with OS X Server 10.5 (port 80 or 443 ; directory /some-protected-realm/) and a realm protected with Kerberos it fails miserably, resulting in *** Running HTTP test Second HTTP request did not result in a 2xx response: 401 and a web server error mod_spnego_apple: Cannot get SPNEGO handle from token: -9 binaryTokenLen=595, base64Len=598 So it seems that PyKerberos authenticates fine against the python server behind caldav but NOT against the stock apple spnego module shipped with the server. Is this the expected behavior or a flagrant bug ? This test was prompted by efforts of Tim Olsen who wrote a kerberos authetication extension for mercurial (hg revision control software) to help me use it on a Mac Os X server. Thanks for your opinion and help on this matter Sincerely Paul Windey Prof. of Physics Université Pierre et Marie Curie windey(a)lpthe.jussieu.fr

2 1

Re: [CalendarServer-dev] [CalendarServer-changes] [3245] CalendarServer/tags/release/CalendarServer-1.3/
by Guido Günther 17 Nov '08

17 Nov '08

Hi Winfredo, On Tue, Oct 28, 2008 at 11:21:32AM -0700, source_changes(a)macosforge.org wrote: > Revision: 3245 > http://trac.macosforge.org/projects/calendarserver/changeset/3245 > Author: wsanchez(a)apple.com > Date: 2008-10-28 11:21:32 -0700 (Tue, 28 Oct 2008) > Log Message: > ----------- > Tag 1.3. Small changes, but has been stable a while. Diffing 1.3 vs. 1.2 shows: config.py |13628 ++++++++++++++++++++++++++++++++++++++++++++++++++ static.py |16712 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- are these the only changes scheduled for 1.3? -- Guido

3 8

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP
by CalendarServer 14 Nov '08

14 Nov '08

#260: OpenLDAP ----------------------------------------+----------------------------------- Reporter: jusiskin(a)franticfilms.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ----------------------------------------+----------------------------------- Comment(by wsanchez(a)apple.com) Meh, it was pretty bizarre. -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:11> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #267: Add Web UI for managing some user settings on the server
by CalendarServer 13 Nov '08

13 Nov '08

#267: Add Web UI for managing some user settings on the server ---------------------------------+------------------------------------------ Reporter: wsanchez(a)apple.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ---------------------------------+------------------------------------------ Comment(by ggm(a)apnic.net) Another advantage of this is that it would get over some of the limitations of Directory binding in the client, to map from names to uuid/guid. If the web interface is sufficiently generalized, then it can RESTify into a service binding in clients later on. -- Ticket URL: <http://trac.calendarserver.org/ticket/267#comment:1> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP
by CalendarServer 13 Nov '08

13 Nov '08

#260: OpenLDAP ----------------------------------------+----------------------------------- Reporter: jusiskin(a)franticfilms.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ----------------------------------------+----------------------------------- Comment(by ggm(a)apnic.net) Replying to [comment:9 wsanchez@…]: > Note: "bizarre schema" is gone in trunk, though it still relies on OpenDirectory. many thanks. I will try to avoid pejoratives in comments in future. -G -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:10> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP
by CalendarServer 13 Nov '08

13 Nov '08

#260: OpenLDAP ----------------------------------------+----------------------------------- Reporter: jusiskin(a)franticfilms.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ----------------------------------------+----------------------------------- Comment(by wsanchez(a)apple.com) Note: "bizarre schema" is gone in trunk, though it still relies on OpenDirectory. -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:9> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP
by CalendarServer 12 Nov '08

12 Nov '08

#260: OpenLDAP ----------------------------------------+----------------------------------- Reporter: jusiskin(a)franticfilms.com | Owner: wsanchez(a)apple.com Type: Feature | Status: new Priority: 3: Important | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Other Resolution: | Keywords: ----------------------------------------+----------------------------------- Comment(by ggm(a)apnic.net) I know this project is not a democracy (joke!) but please PLEASE can you prioritize an adoption of this LDAP change? Requiring Apple Directory and the bizarre schema is making it very hard to integrate a singleton iCal server in an otherwise openldap world. Since this change also provides PAM backed pmauth validation of the plaintext password, insecure though it is, I think it will make other people happy too: In principle, it removes the need for Kerberos doesn't it? -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:8> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0