[PHP] image protection

2006-10-06 Thread tedd

Hi gang:

What would be the best way to protect images in a directory from 
being harvested?


I know that when an image is shown to the user, while there are some 
javascript tricks to deter the user, there is no real way to stop the 
user from capturing the image, for they already have it.


But, is there a way to protect a directory such that an application 
such as SightSucker (nice program btw), can't retrieve it's 
contents, while your php script can?


Thanks.

tedd
--
---
http://sperling.com  http://ancientstones.com  http://earthstones.com

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] image protection

2006-10-06 Thread Eric Butera

On 10/6/06, tedd [EMAIL PROTECTED] wrote:

Hi gang:

What would be the best way to protect images in a directory from
being harvested?

I know that when an image is shown to the user, while there are some
javascript tricks to deter the user, there is no real way to stop the
user from capturing the image, for they already have it.

But, is there a way to protect a directory such that an application
such as SightSucker (nice program btw), can't retrieve it's
contents, while your php script can?

Thanks.

tedd
--
---
http://sperling.com  http://ancientstones.com  http://earthstones.com

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php





You could try http://alistapart.com/articles/hotlinking.

Another way that you could do it is setting a session variable on the
page that you know your images are going to be viewed from.  Then on
the script that your images are linked in through (via
page.php?image=x) check for that session variable.  At least with this
second method it forces the robot to accept a session cookie.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] image protection

2006-10-06 Thread Børge Holen
lurkin' around trying to keep images from others, while still have them shown 
on yer own page seems a bit futile.
watermark 'em.
other stuff to do is use flash witch I've never done. (due to PPC 
restrictions)
I've done some of this auto open/close windowing js, witch also includes 
rightclick disable inside the window; inserting an 1x1 gif ontop, keeping ppl 
away from direct access of the opened php file with a check of witch location 
it was accessed from. Insert no-cache in the metadata.  This worked on every 
browser except Opera, witch have some option to disable JS without loosing 
focus from an window. whereas the gif came in handy This worked on none 
to eager ppl, while on the other hand; If this image popup was run one time. 
it could be used one time directly from the address bar due to the browser 
cache or the session in witch the script were accessed, dunno. Anyone know?

Say, stay with WM.

On Friday 06 October t2006 19:44, tedd wrote:
 Hi gang:

 What would be the best way to protect images in a directory from
 being harvested?

 I know that when an image is shown to the user, while there are some
 javascript tricks to deter the user, there is no real way to stop the
 user from capturing the image, for they already have it.

 But, is there a way to protect a directory such that an application
 such as SightSucker (nice program btw), can't retrieve it's
 contents, while your php script can?

 Thanks.

 tedd
 --
 ---
 http://sperling.com  http://ancientstones.com  http://earthstones.com

-- 
---
Børge
Kennel Arivene 
http://www.arivene.net
---

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] image protection

2006-10-06 Thread Richard Lynch
On Fri, October 6, 2006 12:44 pm, tedd wrote:
 What would be the best way to protect images in a directory from
 being harvested?

Tell the client that correctly linked and tagged images INCREASE
traffic because the search engines can find them and suck people in,
so hiding them is a Bad Idea. :-)

 But, is there a way to protect a directory such that an application
 such as SightSucker (nice program btw), can't retrieve it's
 contents, while your php script can?

But it this way:
You can erect as many barriers as you like.

Some of them will stop some automated scripts.
Many of them will stop legitimate use.
Most of them will incovenience legitimate users.
None of them will stop a determined writer of an automated script.

[irony]
I type this message as my PHP script is surfing to our site on IE in
the background, trying to trigger an intermittent session disappearing
bug.
[/irony]

-- 
Some people have a gift link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php