>Why not put media (text, images) in a MetaCard stack as a wrapper, then
set
>a password for it for transport?
Agreed. Even though custom properties get encrypted when saved as a file,
any reasonably experienced MC developer can open the stack and get access
to the custom properties using customkeys and the like. For now setting
a script is the way to go, to get around any syntax errors using the
script editor you would do something like:
set the script of btn "hiddenbutton" to mydata
and insert the following script into front:
on scriptparsingerror
end scriptparsingerror
on errordialog
end errordialog
Now that MC has no script limit there's no problem with the length of the
data but their may be problems with encrypting binary data..since scripts
can't contains binary data. To work around this you can use the
base64encode and decode functions like so:
set the script of btn "cryptfile" to base64encode(url ("binfile:"&it))
put base64decode(the script of btn "cryptfile") into url ("binfile:"&it)
>So here's the question: Just how secure is MC's encryption compared to,
>say, PGP or other popular methods? Would it be considered suitable for
>transporting medical record data?
Seems pretty secure to me. They would not only have to figure out the the
MC encryption but also know that it's base64ed and zipped.
Tuviah
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
