Hi Mark So it must be the auto-completes that have the wrong possible values added to its list. Type 'encrypt' into the script editor and go to the bottom, then right and there are every possible iteration based on the syntax given in the dictionary. This does not match up with your description so perhaps needs looking in to.
Thanks for your help Sean On Thu, 16 Dec 2021 at 17:36, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > On 2021-12-16 17:09, Sean Cole via use-livecode wrote: > > Thanks Mark, > > > > New problem. Trying to use aes-256-ctr instead. I'm following the > > syntax in > > the dictionary but it throws a red cross on it: > > > > encrypt tData using "aes-256-ctr" with key tMyKey and salt tMySalt > > I think you can either specify a key, or a password with an optional > salt. > > If you specify a password it uses the provided salt (or a random one if > one is not provided) to generate a key of the correct length (the bit > length of the cipher). > > If you provide a key then it uses that verbatim to encrypt the data (in > this case the key must be the correct number of bits as defined by the > chosen cipher - 256 in this case). > > Warmest Regards, > > Mark. > > -- > Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ > LiveCode: Everyone can create apps > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
