 External Editor
 Yamb
 Web iPhoto Access
 29 membres
Utilisateurs en ligne
( personne )
147710 visiteurs
12 visiteurs en ligne
|
| Sujet n°64 |
Install on Linux
par rpaskowitz - visiteur
le 22/02/2006 @ 21:48 |
 |
This looks like just the thing I want for my photos, but I don't have a mac server.
I'm willing to put some work in to make it work on linux, but am hitting a couple walls.
1) `changeperm` the mach-o executable. Is the source available? I'll need to get that compiled
2) I get the following on first login:
Warning: Unexpected character in input: '' (ASCII=15) state=1 in /usr/local/dh/cgi-system/php.cgi on line 1247
Parse error: syntax error, unexpected T_STRING in /usr/local/dh/cgi-system/php.cgi on line 1247
|
 |
| Réponse n°21 |
par rpaskowitz -  ( 3 messages )
le 23/02/2006 @ 01:28 |
|
It's not about sniffing the wire, it's the fact that any random person could come along type in the (albeit difficult to guess) file name, and view the file.
Or someone that has access to some albums but not others could attempt to view photos they were not authorized to.
The overhead in pulling these thumbnails, once generated is minimal. The code checks if a thumbnail exists, and if so, spits it out to the browser.
Thumbnail generation will of course have some overhead, but is a one time thing for photos.
Testing here shows that generated images load nearly instantaneously(even with no browser cache). |
 |
| Réponse n°22 |
par Poochie - visiteur
le 23/02/2006 @ 01:37 |
|
I still don't see the difference.
Method "temp folder":
- request id + parameters
- get the photo and put the thumb in the tmp folder
- sent the thumb
If I request an unauthorized photo then the protection system forbids me to do so.
If I replace the source image in the php code nothing forbids me (I think, obviously) to keep the other security routines.
Anyway the problem is what is wasting so much cpu on loading a new thumb page. Reloading the same page on another computer will result in having to wait again for the whole page to be generated so slowly. |
|
| Réponse n°23 |
par rpaskowitz - ( 4 messages )
le 23/02/2006 @ 02:13 |
|
That's a silly amount of overhead to copy a file to a temp folder and then serve it up from there. It also does nothing at all for the privacy matter as 'any random joe' could come along and access the temp folder directly.
Sure, you'd be stopped when requesting it from wipha, but should someone find out the URL to the temp image, they'd have direct access through the httpd, wipha wouldn't know a thing about it. |
| |
|
|
![[fr]](inc/lang/fr.gif)
![[en]](inc/lang/en.gif)
Haut 
Site créé avec GuppY v4.5.14 © 2004-2005 - Licence Libre CeCILL