On Mar 21, 2006, at 10:13 AM, Richard Gaskin wrote:
So while it keeps people who don't have Rev from extracting data,
it still leaves data vulnerable to those who do.
Exactly the problem...
Scott wrote:
but I would guess the likelihood of your users owning a copy of
Rev is lower than
OK further testing I finally settled on a compromise taking Key Ray's
suggestion but not using compressed imageData, I don't see any
advantage (I could be missing something) to using compressed
imageData over simple jpg storage. Either format would be equally
hackable...
I think this
Sivakatirswami wrote:
OK further testing I finally settled on a compromise taking Key Ray's
suggestion but not using compressed imageData, I don't see any
advantage (I could be missing something) to using compressed
imageData over simple jpg storage. Either format would be equally
Recently, Sivakatirswami wrote:
I think this comes close to making the images at least some what
obscurely stored.
--create a substack
--import images into custom props as jpegs,
--One could put these props in something a available as a card
property or something very obscure, like a
Recently, I wrote:
field contents are
encrypted along with the rest of the stack data when a stack is password
protected, while custom props are not
...or maybe custom props *are* encrypted. That's weird, I could have sworn
that custom props were visible when viewing stack data in a text
Scott Rossi wrote:
Recently, I wrote:
field contents are
encrypted along with the rest of the stack data when a stack is password
protected, while custom props are not
...or maybe custom props *are* encrypted. That's weird, I could have sworn
that custom props were visible when viewing
On Mar 18, 2006, at 2:39 AM Mar 18, 2006, Sivakatirswami wrote:
if the environment is development then quit
does that not prevent someone from opening it up in the IDE?
mmm. I'm reviewing all the memos to date on this and see you
already mentioned this.
OK yes, I think this is doable
1) The bad guys are in my dream world are other owners of the Rev
IDE, which has in this future world, become as ubiquitous as Acrobat
Professional. It implies that Rev actually does become wildly
popular... In that world, not all will be as scrupulous as our
current obviously rapidly
At 11:40 PM -1000 3/17/06, Sivakatirswami wrote:
see a drop dead simple option to block viewing of substacks in the IDE...
If you place in the stack script of one of these files you are sending
'out into the world' (iow - not an in-house production file that you
might use later for working
On Mar 18, 2006, at 12:27 AM, sims wrote:
At 11:40 PM -1000 3/17/06, Sivakatirswami wrote:
see a drop dead simple option to block viewing of substacks in the
IDE...
If you place in the stack script of one of these files you are sending
'out into the world' (iow - not an in-house
On Mar 18, 2006, at 12:27 AM, sims wrote:
At 11:40 PM -1000 3/17/06, Sivakatirswami wrote:
see a drop dead simple option to block viewing of substacks in the IDE...
If you place in the stack script of one of these files you are sending
'out into the world' (iow - not an in-house production
At 12:39 AM -1000 3/18/06, Sivakatirswami wrote:
if the environment is development then quit
With one app I...
placed QuickTime videos into a userprop inside of individual files
that had the above script.
I then had an app open that file, grab the userprop, and create a QT
video as a
In a message dated 3/18/06 7:20:17 AM, sims [EMAIL PROTECTED] writes:
At 11:40 PM -1000 3/17/06, Sivakatirswami wrote:
see a drop dead simple option to block viewing of substacks in the IDE...
If you place in the stack script of one of these files you are sending
'out into the world' (iow - not
In a message dated 3/18/06 7:20:17 AM, sims [EMAIL PROTECTED] writes:
At 11:40 PM -1000 3/17/06, Sivakatirswami wrote:
see a drop dead simple option to block viewing of substacks in the IDE...
If you place in the stack script of one of these files you are sending
'out into the world' (iow -
At 9:10 PM +0100 3/18/06, sims wrote:
oes that not prevent someone from opening it up in the IDE?
Maybe. Try typing this into the message box and see what happens:
edit script of stack MyProtectedProject
Ummm...oh, I see what you mean.
Back to the drawing board.
ciao,
sims
FYI, setting a customProp with the compressed image data actually
increases the size of the stack if those images were resized to
larger than their original incoming size (that's expected behavior)
This presents somewhat of a conundrum. Since the import of a 3 X 5
jpeg whose original
Why can't you protect the access online to the files on a secure
server rather than try to protect the media? Who or what are the 'bad
guys'??
sqb
FYI, setting a customProp with the compressed image data actually
increases the size of the stack if those images were resized to
larger than
On Mar 17, 2006, at 8:57 AM, Stephen Barncard wrote:
Why can't you protect the access online to the files on a secure
server rather than try to protect the media? Who or what are the
'bad guys'??
sqb
Can the files be outside the application in a data folder perhaps?
If so, you could
Dream with me for a moment:
Revolution Players of various shapes and flavors have become as
ubiquitous as copies of Acrobat Reader. The Revolution IDE is
deployed to the same number of seats as Acrobat Professional.
Enter new problem: Digital Rights Management: how to protect images
and
Hi Sivakatirswami,
On 07 Mar 2006, at 10:42, Sivakatirswami wrote:
Dream with me for a moment:
-snip-
Insights anyone?
A possibility to protect your images is to encrypt them using a
blowfish or another algo (included in the enterprise version) and put
the result into fields or
On 3/7/06 3:42 AM, Sivakatirswami [EMAIL PROTECTED] wrote:
Not so for a Rev stack. If you deployed a rich media library as
stacks that had copyright images stored in a substack, even if one
sets a password on a stack, any other developer could open substack
image library and go through the
well, the point is to protect it *also* when looking in the REv's IDE
inspector.
If you put the images into customProps and then put a password on
the stack... will that prevent uses who have the IDE from getting at
them? (I'll try it.)
Sivakatirswami
On Mar 07, 2006, at 5:40 AM, Ken Ray
On 3/7/06 1:05 PM, Sivakatirswami [EMAIL PROTECTED] wrote:
well, the point is to protect it *also* when looking in the REv's IDE
inspector.
If you put the images into customProps and then put a password on
the stack... will that prevent uses who have the IDE from getting at
them? (I'll try
At 1:53 PM -0600 3/7/06, Ken Ray wrote:
On 3/7/06 1:05 PM, Sivakatirswami [EMAIL PROTECTED] wrote:
well, the point is to protect it *also* when looking in the REv's IDE
inspector.
If you put the images into customProps and then put a password on
the stack... will that prevent uses who
On 3/8/06, Ken Ray [EMAIL PROTECTED] wrote:
No, they can get to them, but they won't know what how to decipher the
binary data you put in there.
Of course everyone has only mentioned the images, although the same can
apply to the text in your text fields. This all seems very complex to me.
25 matches
Mail list logo
