|
Ok, I hacked up a simple authorization scheme. You can now set up users in the Preferences tool and assign them admin status. The users can use either a local password (the md5 of the password is stored), a POP3 server (the password is used via POP3 to authenticate against a remote server!) or - if you have the smbauth.py module and assorted library installed - NT domain credentials to login. With NT login you have to provide the PDC, the BDC and the Domain to use for password check. This helps people to set up the Python Desktop Server so that they can access one instance from different places. To enable the remote accessability and to actually make use of the users, you have to add the following two settings in your ~/.PyDS/etc/PyDSConfig.py: remotehostname = 'your long hostname here'
remoteip = 'your IP other than 127.0.0.1 here'
remoteport = 4334 # set as default After the next restart, an additional server is started up. The one on 127.0.0.1 is still without authentication, but the new one will use your users. An admin user is the only one allowed to access pages with POST method or access _redir methods. The latter one are the methods that do the destructive work. There is a way to say tools wether to check for Authentication data at all or wether admin is needed or not, this can be defined by the programmer. Currently all tools use authentication and need admin for _redir and POST. Ok, and what has this to do with moblogging? Actually it's my first start in that area, as I now have a Zaurus that actually has a decent webbrowser and so can make use of my home-PyDS from remote locations via GPRS mobile data connectivity  Happy hacking. |
