-
This is a known problem and is being worked on. pdbsql 0.2 works until 3.0.24. We expect to release 0.3 for 3.0.25 and up in a about a week and a half.
Thank you for reporting this, and thanks for the link. I'll make sure it's monitored occasionally.
2007-06-14 21:57:50 UTC in Samba SQL password backend modules
-
Ok, after some hours of fiddling, I got it to work when cross compiling for 32-bit with gcc 4.1
It would appear that vncsnapshot is not 64-bit compatible.
2007-06-01 19:03:34 UTC in VNCSnapshot
-
Just retested, same platform, latest CVS, still not working.
2007-06-01 18:28:32 UTC in VNCSnapshot
-
This is on Debian sarge on amd64, btw.
2007-06-01 18:21:52 UTC in VNCSnapshot
-
When connecting to a RealVNC 4.1.1 server:
$ vncsnapshot 192.168.68.2 test.jpg
VNC server supports protocol version 3.8 (viewer 3.3)
Password:
VNC authentication succeeded
Desktop name ""
Connected to VNC server, using protocol version 3.3
VNC server default format:
32 bits per pixel.
Least significant byte first in each pixel.
True colour: max red 255 green 255 blue 255, shift...
2007-06-01 18:13:02 UTC in VNCSnapshot
-
synnack committed revision 72 to the Samba SQL password backend modules SVN repository, changing 3 files.
2007-01-16 08:53:37 UTC in Samba SQL password backend modules
-
synnack committed revision 71 to the Samba SQL password backend modules SVN repository, changing 3 files.
2007-01-16 08:51:22 UTC in Samba SQL password backend modules
-
>I imagine it has bugs because (a) it uses the DTSTART etc. values in the raw, from the original calendar items put by whatever calendar put them there, and (b) it doesn't include the VTIMEZONE values that were included with those.
What do you mean by "Whatever calendar put them there?", it should be just the calendar(s?) of the user of which the freebusy data is requested, right?
I think...
2006-11-21 10:29:29 UTC in DAViCal CalDAV Server
-
It's actually rather simple, it's a vCalendar format without contents of the events. it is requested for a user in (for example, mostly configurable) the following url: https://rscds.example.net/freebusy.php/email@address.ifb
Posting freebusy information isn't necessary, because we want the CalDAV information viewable in freebusy format, not add empty 'busy' events to the store.
It is then...
2006-11-20 11:16:48 UTC in DAViCal CalDAV Server
-
It should be fairly easy to support kerberos authentication through mod_auth_kerb. This could then forward authentication to PostgreSQL.
And the credentials can be accessed through $_SERVER['PHP_AUTH_*'] when basic authentication is activated.
ACL/relationships could be done very much the same as it exists now.
2006-11-15 16:07:18 UTC in DAViCal CalDAV Server
