Thanks Vade,
Your comment is the calling card of an experienced QC developer ;-)
Can you please help me join the dots a bit b/c I'm a designer who
dabbles in JS and Ruby coding not a developer per se.
I've searched the keywords in your post. I read this cwright Kineme
thread amongst others and Apple docs: QCComposition
Some things remain unclear to me — and I'm just talking a concept
level of "is this currently achievable and secure", not about
particular execution methods of your recommended path.
It's seems important to me that the decrypted composition resides in
memory not written, even temporarily, to HD in plain-text. A force
quit of hosting app like Keynote or QC Editor then search ".qtz" &
sort by date will turn up the secret composition in plain text form
otherwise (as pointed out by Christopher on the Kineme thread).
Are you talking about writing a QC composition in Xcode that can load
and decrypted the NSData blob from another file? Or are we talking
about a writing a QC plugin that loads the NSData and decodes it and
somehow creates a QCComposition object that can bind to the plugin
patch's ports in QC.
I've only ever made QC compositions in the QC Editor and was unaware
other methods of generation are possible — be they write Cocoa code in
Xcode or a runtime generation from text file scenario so this is super
hazy to me. :-\
Important requirements from my POV:
There's some kind of indefinable KN_Theme.qtz (or .mov) file that the
user can copy instances of to their documents folder or wherever and
it doesn't contain the secret code/images accessible form (plaintext).
This file will presumably load and bind to the encrypted secret file
and also some kind of .txt or .plist file that I can use to allow
users to edit the top level published input ports without going into
QC Editor (for various usability reasons). That's required since KN
precludes the ability to access a.qtz file's published ports.
The encryption key remains secret from a inquisitive competitor! Where
would it be stored or would it auto-generated at runtime and stay
secret somehow? Or would it be stored in the Keychain at installation
time thereby becoming safe.
There's a encrypted file that gets created at installation of KN Theme
product, probably located in a Library folder which gets loaded.
The encrypted file, when decrypted into a QC composition is not
written to HD where it can be interrogated at runtime with a Force
Quit and search for recent .qtz files.
Appreciate your patience,
Alastair Leith
On 19/06/2011, at 10:29 AM, vade wrote:
You can manage this yourself via QCComposition compositonWithData.
Look up how to encrype NSData blobs, and there you go :)
On Jun 18, 2011, at 1:30 AM, Alastair Leith wrote:
Please duplicate this request if it is of interest to you.
I've wanted this for a couple of years to publicly sell my Keynote
work online. Themes and the like. iMovie QC support adds to the
value and there's talk (however misguided?) about FCP X doing more
in the way of QC integration. Basically to have the FxPlugin level
security with QC files so distribution and sale of effects/
transitions/bkgd themes is less risky of being ripped off wholesale
and cost free to whomever would do such a horrible thing.
http://openradar.appspot.com/radar?id=1229403
The machine does not isolate man from the great problems of nature
but plunges him more deeply into them.
Antoine de Saint-Exupery
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected]
)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/doktorp%40mac.com
This email sent to [email protected]
The machine does not isolate man from the great problems of nature but
plunges him more deeply into them.
Antoine de Saint-Exupery
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
