pycs-devel archive weblog

A blog for archiving the pycs-devel mailing list

2003-5-16

Phillip Pearson: Re: [PyCS-devel] user supplied access restrictions for PyCS

Ooh, great. I've been thinking about what sort of API to make for
defining permissions in my standalone search engine, but seeing as
you've already defined this, I'll just use it ;-)

I'll make a tool to take a PyCS users.conf file and push it up to a
server using this API, and then if you get it so PyDS can set access
restrictions on > 1 server at once (wait until we've got integration
with my search engine though), everything will just come out
automatically.

Cheers,
Phil

On Thu, May 15, 2003 at 03:51:44PM +0200, Georg Bauer wrote:
> Hi!
>
> The following link:
>
> http://pyds.muensterland.org/weblog/2003/05/15.html#P118
>
> announces a description of a way to set up access restrictions on blogs
> with an XML-RPC API. This is to allow blogging tools to set up user
> accounts and access restrictions from within the tool. I am planning to
> build such a tool for the PyDS.
>
> It's much like a <Location ~ /^..../> ... </Location> block in Apache,
> only there is only _one_ password list and restrictions are always
> based on groups. The blogging tools can easily build a GUI on top of
> the API.
>
> One way to use this is to set up access restrictions for your backup
> path, so others can't access your backups. Or to set up private
> categories that are rendered and upstreamed, but should only be read by
> a group of visitors you personally know.
>
> Phil: I have applied patches to search.py, but since I don't use
> ht:/Dig, I can't test it. So you better look over my code before you
> upgrade pycs.net ;-)
>
> swish.py doesn't honor the access restrictions, but since it only gives
> out the URL, I don't see big problems with this. Users could use the
> swish searching to discover what a document might be about, though.
> Phil once wrote that he had applied patches to swish.py to hook it into
> the access stuff, but I can't find them and so didn't bother to add my
> own stuff ;-)
>
> This XML-RPC API is mostly ignorant of the kind of community server it
> runs on, so it could be implemented on top of PSS or RCS, too.
>
> Comments? Ideas? Bugs?
>
> bye, Georg
>
>
>
> -------------------------------------------------------
> Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
> The only event dedicated to issues related to Linux enterprise solutions
> www.enterpriselinuxforum.com
>
> _______________________________________________
> PyCS-devel mailing list
> PyCS-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pycs-devel

Georg Bauer: [PyCS-devel] user supplied access restrictions for PyCS

Hi!

The following link:

http://pyds.muensterland.org/weblog/2003/05/15.html#P118

announces a description of a way to set up access restrictions on blogs
with an XML-RPC API. This is to allow blogging tools to set up user
accounts and access restrictions from within the tool. I am planning to
build such a tool for the PyDS.

It's much like a <Location ~ /^..../> ... </Location> block in Apache,
only there is only _one_ password list and restrictions are always
based on groups. The blogging tools can easily build a GUI on top of
the API.

One way to use this is to set up access restrictions for your backup
path, so others can't access your backups. Or to set up private
categories that are rendered and upstreamed, but should only be read by
a group of visitors you personally know.

Phil: I have applied patches to search.py, but since I don't use
ht:/Dig, I can't test it. So you better look over my code before you
upgrade pycs.net ;-)

swish.py doesn't honor the access restrictions, but since it only gives
out the URL, I don't see big problems with this. Users could use the
swish searching to discover what a document might be about, though.
Phil once wrote that he had applied patches to swish.py to hook it into
the access stuff, but I can't find them and so didn't bother to add my
own stuff ;-)

This XML-RPC API is mostly ignorant of the kind of community server it
runs on, so it could be implemented on top of PSS or RCS, too.

Comments? Ideas? Bugs?

bye, Georg