From: Bryan K. <br...@wu...> - 2001-11-02 04:22:55
|
Well, let's have a quick discussion: How would we like password protection to work? There are two ways I can think of which seem to fit nicely: a) single file with username:password:album1,album2,album3 Pro: Single file Easy to modify and add new albums for a user. Cons: Allow based password protection, ie, deny all but the albums you specify. Could get nasty with lots of albums. - suggestion, make a * and -album1, although this would require more parsing, it would allow you to do something like: username:password:*,-album1,-album2 What do you do about nested albums? (album1/album2)? requires special file handling to create the password file. b) .htpasswd files in each album you want protected, as well as a master .htpasswd in the script dir. Pro: * Simple design. * Files can be created with the htpasswd util distributed with apache. * deny based. If you want to allow access to an album you don't put a .htpasswd in the dir (and also don't have the master one) * works well with nested albums. (searches down the tree for a password file) * Works the same way as the current config override system. Cons: * Multiple files. * Slightly more work to upkeep, although good design of the album heirarchy could minimise that. * Might have to have the same password file in multiple locations. - Could be solved with soft links * Can't have a master password file without closing all the album dirs. Any thoughts? I currently have a working version of type 2, take a look at http://wuzzle.org/photos/new/phpix You should be able to view the main page fine, and CVS, but if you try view Sample Album, it should prompt you for a user/pass. user: test pass: ook I can modify it for type a) pretty easily. or possibly a hybrid. Now that the framework is in, the way we want to apply it is easily changed. Bryan On Thu 2001-11-01 (10:11), Neale Pickett wrote: > So then, Bryan Kilian <br...@wu...> is all like: > > Okie, I made a bit of a change in the way phpix works. I offloaded the > > images onto a separate script, which deals with resizing and caching. > > Good idea! perl -e 'map{print(pack(V,exp("21.$_")))}(21512211,40167979,2548395575,2745918245)' |