December 2009 - calendarserver-dev - lists.macosforge.org

[CalendarServer] #355: authenticate_gss_client_wrap() (PyKerberos) fails to wrap username correctly
by CalendarServer 05 Jan '10

05 Jan '10

#355: authenticate_gss_client_wrap() (PyKerberos) fails to wrap username correctly ----------------------------+----------------------------------------------- Reporter: rbasch@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: PyKerberos | Severity: Other Keywords: | ----------------------------+----------------------------------------------- In PyKerberos 1.1, authenticate_gss_client_wrap() (src/kerberosgss.c) miscalculates the length of the username string when wrapping it, by including the terminating null character in the length. This results in authentication failures. I am attaching a patch that seems to fix the problem. -- Ticket URL: <http://trac.calendarserver.org/ticket/355> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1

[CalendarServer] #354: username and password box
by CalendarServer 04 Jan '10

04 Jan '10

#354: username and password box --------------------------------+------------------------------------------- Reporter: jimallen@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Severity: Other Keywords: | --------------------------------+------------------------------------------- Hi, Our clients can get asked for their username and password to be entered while lightning or Sun is running. During this process one or more of the calendars are in error. Having said that, the calendar/s in error don't always play up, ie you can still read and write/create new entries while in error. I check the saved passwords and all details are correct. It would seem to happen at random with different people being effected on different times/days with different calendars. Sometimes a user or two cannot see a shared calendar when others can use it fine. The only solution seems to be to wait it out, which is not much help if you have stuff booked on the calendar you need to access. I have even tried reinstalling the calendar and upgrading to the latest version but with no effect. Can you help? -- Ticket URL: <http://trac.calendarserver.org/ticket/354> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 1

Use of Twisted web2
by Peter Mogensen 04 Jan '10

04 Jan '10

Hi, I've been looking into the state of Twisted and CalendarServer and I'm a little confused about the roadmap. Twisted developers write: "Twisted Web 2 was (emphasis past tense!) a complete re-write of Twisted Web, with a new HTTP/1.1 implementation and a new resource publishing model. We decided this was a mistake and development focus has shifted to porting the best parts of Twisted Web 2 back to Twisted Web where existing applications will benefit from them." But CalendarServer relies heavily on Web2 features (DAV/ACls), so it would seem that unless there will be a 1-1 migrate path from Web2 to never versions of Twisted.web for these features, then CalendarServer is stuck on an unmaintained branch of Twisted. In other places people mention that there's plan to merge the dav-take-two-3081-4 branch back onto twisted trunk as soon as it's ready, but from the above that seem like it's an old abandoned plan? Could anyone elaborate on the plans for Twisted in CalendarServer? /Peter

2 1

Ticket 148, remove ACL method
by Peter Mogensen 04 Jan '10

04 Jan '10

Hi, I'm a little puzzled by the change in this ticket to completely remove the ACL method. I realize that it'll make it easier for a specific application of calendarserver, in which the client doesn't offer ACL control and access is defined by predefined group or proxy principals, but it would make the calendarserver a lot less general a tool. It would also conflict with rfc4791 section 2. What are the arguments for doing this ? - aside from not having to solve the original problem i ticket 148. /Peter

2 1

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 17 Dec '09

17 Dec '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: glyph@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by elesueur@…): thanks, I was getting confused about the authentication section in the caldavd.plist config file. I eventually figured it out! -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:43> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 17 Dec '09

17 Dec '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: glyph@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rahul@…): A quick note. The possible values for "authMethod" currently are "PAM" and "LDAP". Replying to [comment:41 rahul@…]: > I have modified the patch to add two new options - authMethod and guidAttr. If guidAttr is defined, then the directory can be queried on guid as well i.e. urls of the form http://server.example.com:8008/principals/__uids__/85cba509-fdaa-5cae- b4ea-fbeb4612dd50/ could be used without any worry. > > Also I am attaching a sample caldav.plist to list the complete set of options (listed within ldap directory service). -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:42> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 17 Dec '09

17 Dec '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: glyph@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rahul@…): I have modified the patch to add two new options - authMethod and guidAttr. If guidAttr is defined, then the directory can be queried on guid as well i.e. urls of the form http://server.example.com:8008/principals/__uids__/85cba509-fdaa-5cae- b4ea-fbeb4612dd50/ could be used without any worry. Also I am attaching a sample caldav.plist to list the complete set of options (listed within ldap directory service). -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:41> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 15 Dec '09

15 Dec '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: glyph@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by elesueur@…): thanks for that - much appreciated. How do I configure CalendarServer to use this ldapdirectory authentication method? -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:40> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 14 Dec '09

14 Dec '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: glyph@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by rahul@…): I have uploaded the patch (ldapdirectory.patch) which works against calendarserver 2.3. This might work against trunk as well. Some points to note: 1. To use this patch, use urls of the from http://server.example.com:8008/calendars/users/admin/... and not http://server.example.com:8008/principals/__uids__/85cba509-fdaa-5cae- b4ea-fbeb4612dd50/... because support for querying the directory using guid is not added currently. 2. For authentication, PAM is used (the pam service name is "caldav"). If you want to use ldap server for authentication, you can just uncomment the LDAP authentication code and comment out the PAM authentication code in verifyCredentials function. This patch has not been extensively tested. So you might find some bugs in which case kindly post in this thread. -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:39> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0

Re: [CalendarServer-dev] [CalendarServer] #260: OpenLDAP directory service
by CalendarServer 14 Dec '09

14 Dec '09

#260: OpenLDAP directory service ---------------------------------------+------------------------------------ Reporter: jusiskin@… | Owner: glyph@… Type: Feature | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ---------------------------------------+------------------------------------ Comment(by elesueur@…): I'm looking at using this patch as well - Am I correct in assuming that it won't apply to the current trunk? I need to checkout version 1.2 and apply it to that tree? -- Ticket URL: <http://trac.calendarserver.org/ticket/260#comment:38> CalendarServer </> HTTP/WebDAV/CalDAV Server

1 0