Re: multi-line constants? (for RSA keys)
I suppose, but the elegance of working in the IDE leads me to develop accordingly. If then when I compile an app for the first time I discover my methods will not work, I am tempted rather to find a way to make it work, and eschew changing the way I develop. But one leg is both the same I suppose. Password protecting substacks and saving them out of the application will work for me. It’s not like I am developing for the NSA anyway. Bob On Apr 3, 2014, at 19:08 , Peter Haworth p...@lcsql.commailto:p...@lcsql.com wrote: I think the real solution is to store persistent values in a file or a database. Pete ___ 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
Re: multi-line constants? (for RSA keys)
Thanks, I think I remember what the issue was now. If you want your stacks to be writable, they cannot be part of the app. Is that correct? So if the application has the need to save things like persistent properties and such, you HAVE to separate the substacks, thereby making them runnable in the IDE. So the only real solution it seems to me is to password protect all the substacks before compiling, and then write code into the stacks to prevent them from running if they are the topStack of themselves. Bob On Mar 31, 2014, at 10:37 , J. Landman Gay jac...@hyperactivesw.com wrote: On 3/31/14, 10:10 AM, Bob Sneidar wrote: It was my impression that the mainstack gets*glued* together with the runtime engine and is not accessible in the same way the substacks are, which are merely included in a subfolder or in the case of OS X, in the package. Is this no longer the case? Or have I simply misunderstood all this time? If the substacks are true substacks, they are glued to the engine the same way the mainstack is. This is the standard way substacks work. All stacks in a standalone are part of the same file on disk and received the same protection. However, there is a checkbox in standalone settings that allows you to save out substacks as separate files during the build. If you choose to do that, then they are no longer substacks, they are removed from the file and turned into individual document stacks. Those are the same as any other stack you'd use during development and as such, they are no longer part of your app. They're just loose in the folder (or in the bundle on Macs) and can be opened by anyone with a copy of LiveCode, no tricks required. The scripts will be obscured if the stack is password protected but everything else, including properties, will be accessible because it's just a plain old stack now. So if you want the same protection you'd get in the mainstack, just make sure you don't have that checkbox selected. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: multi-line constants? (for RSA keys)
I think the real solution is to store persistent values in a file or a database. Pete lcSQL Software http://www.lcsql.com Home of lcStackBrowser http://www.lcsql.com/lcstackbrowser.html and SQLiteAdmin http://www.lcsql.com/sqliteadmin.html On Thu, Apr 3, 2014 at 5:50 PM, Bob Sneidar bobsnei...@iotecdigital.comwrote: Thanks, I think I remember what the issue was now. If you want your stacks to be writable, they cannot be part of the app. Is that correct? So if the application has the need to save things like persistent properties and such, you HAVE to separate the substacks, thereby making them runnable in the IDE. So the only real solution it seems to me is to password protect all the substacks before compiling, and then write code into the stacks to prevent them from running if they are the topStack of themselves. Bob On Mar 31, 2014, at 10:37 , J. Landman Gay jac...@hyperactivesw.com wrote: On 3/31/14, 10:10 AM, Bob Sneidar wrote: It was my impression that the mainstack gets*glued* together with the runtime engine and is not accessible in the same way the substacks are, which are merely included in a subfolder or in the case of OS X, in the package. Is this no longer the case? Or have I simply misunderstood all this time? If the substacks are true substacks, they are glued to the engine the same way the mainstack is. This is the standard way substacks work. All stacks in a standalone are part of the same file on disk and received the same protection. However, there is a checkbox in standalone settings that allows you to save out substacks as separate files during the build. If you choose to do that, then they are no longer substacks, they are removed from the file and turned into individual document stacks. Those are the same as any other stack you'd use during development and as such, they are no longer part of your app. They're just loose in the folder (or in the bundle on Macs) and can be opened by anyone with a copy of LiveCode, no tricks required. The scripts will be obscured if the stack is password protected but everything else, including properties, will be accessible because it's just a plain old stack now. So if you want the same protection you'd get in the mainstack, just make sure you don't have that checkbox selected. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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 ___ 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
Re: multi-line constants? (for RSA keys)
On 4/3/14, 7:50 PM, Bob Sneidar wrote: Thanks, I think I remember what the issue was now. If you want your stacks to be writable, they cannot be part of the app. Is that correct? So if the application has the need to save things like persistent properties and such, you HAVE to separate the substacks, thereby making them runnable in the IDE. So the only real solution it seems to me is to password protect all the substacks before compiling, and then write code into the stacks to prevent them from running if they are the topStack of themselves. I think you mean mainstack. But Pete had it right. Store user data outside the stack somewhere. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: multi-line constants? (for RSA keys)
Really? Has this changed? I remember a thread some time ago where it was stated that a substack can be extracted as is from a compiled project and run in the IDE. Granted, if the stacks are password protected, it would be very difficult to get to the code, but they are not “compiled” the way the mainstack is. It was my impression that the mainstack gets *glued* together with the runtime engine and is not accessible in the same way the substacks are, which are merely included in a subfolder or in the case of OS X, in the package. Is this no longer the case? Or have I simply misunderstood all this time? Bob Sneidar IT Technician Integrated Office Technology bobsnei...@iotecdigital.commailto:bobsnei...@iotecdigital.com 424-233-7201 On Mar 28, 2014, at 19:51 , J. Landman Gay jac...@hyperactivesw.commailto:jac...@hyperactivesw.com wrote: On 3/28/14, 6:47 PM, Bob Sneidar wrote: It is my understanding (somewhat limited I admit) that any code you do not want others to have access to should be put in the mainstack of a compiled application. If you have any substacks they will of course be accessible by anyone with a little know how. Actually, if they really are substacks, they are part of the same file on disk and have the same security/obscurity as the mainstack. Separate document stacks, of course, can be opened by anyone with a copy of LiveCode. -- Jacqueline Landman Gay ___ 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
Re: multi-line constants? (for RSA keys)
On 3/31/14, 10:10 AM, Bob Sneidar wrote: It was my impression that the mainstack gets*glued* together with the runtime engine and is not accessible in the same way the substacks are, which are merely included in a subfolder or in the case of OS X, in the package. Is this no longer the case? Or have I simply misunderstood all this time? If the substacks are true substacks, they are glued to the engine the same way the mainstack is. This is the standard way substacks work. All stacks in a standalone are part of the same file on disk and received the same protection. However, there is a checkbox in standalone settings that allows you to save out substacks as separate files during the build. If you choose to do that, then they are no longer substacks, they are removed from the file and turned into individual document stacks. Those are the same as any other stack you'd use during development and as such, they are no longer part of your app. They're just loose in the folder (or in the bundle on Macs) and can be opened by anyone with a copy of LiveCode, no tricks required. The scripts will be obscured if the stack is password protected but everything else, including properties, will be accessible because it's just a plain old stack now. So if you want the same protection you'd get in the mainstack, just make sure you don't have that checkbox selected. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: multi-line constants? (for RSA keys)
Not if the custom prop is in the mainstack of a compiled application. It is my understanding (somewhat limited I admit) that any code you do not want others to have access to should be put in the mainstack of a compiled application. If you have any substacks they will of course be accessible by anyone with a little know how. Bob On Mar 22, 2014, at 19:58 , Dr. Hawkins doch...@gmail.commailto:doch...@gmail.com wrote: - custom prop - since you're generating it externally - put it in a fixed-name file, and have your script read that file in But then it would be readable :) ___ 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
Re: multi-line constants? (for RSA keys)
On 3/28/14, 6:47 PM, Bob Sneidar wrote: It is my understanding (somewhat limited I admit) that any code you do not want others to have access to should be put in the mainstack of a compiled application. If you have any substacks they will of course be accessible by anyone with a little know how. Actually, if they really are substacks, they are part of the same file on disk and have the same security/obscurity as the mainstack. Separate document stacks, of course, can be opened by anyone with a copy of LiveCode. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ 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
Re: multi-line constants? (for RSA keys)
On 22/03/14 21:21, Dr. Hawkins wrote: RSA keys, as generated, are multiple lines, like -BEGIN PUBLIC KEY- ABC123 DEF456 -END PUBLIC KEY- I'm trying to do something like constant mykey= -BEGIN PUBLIC KEY- \ ABC123\ DEF456\ -END PUBLIC KEY- but it appears that you can't concatenate strings like this . . . (using 6.6.0) Is there a clean solution for this? Where are you getting your RSA key from? If, for the sake of argument, you have it loaded into your stack as a string variable you could do something like this: put line 1 of RSA after myKey put line 2 of RSA after myKey put line 3 of RSA after myKey put line 4 of RSA after myKey Richmond. ___ 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
Re: multi-line constants? (for RSA keys)
On Sat, Mar 22, 2014 at 12:37 PM, Richmond richmondmathew...@gmail.comwrote: Where are you getting your RSA key from? I'm generating it externally; it is to create the license keys for purchasers. I suppose putting it into a constant instead of a variable really doesn't accomplish anything . . . -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 ___ 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
Re: multi-line constants? (for RSA keys)
On 22/03/2014 19:21, Dr. Hawkins wrote: RSA keys, as generated, are multiple lines, like -BEGIN PUBLIC KEY- ABC123 DEF456 -END PUBLIC KEY- I'm trying to do something like constant mykey= -BEGIN PUBLIC KEY- \ ABC123\ DEF456\ -END PUBLIC KEY- but it appears that you can't concatenate strings like this . . . (using 6.6.0) Is there a clean solution for this? constant doesn't allow any form of expression, you can't even do constant mykey = abc def A clean solution ? - assign to a variable instead - custom prop - since you're generating it externally - put it in a fixed-name file, and have your script read that file in btw if I take the above code, and convert from using a constant to a variable, I'd get put -BEGIN PUBLIC KEY- \ ABC123\ DEF456\ -END PUBLIC KEY- into myVar but that means it's become a single line, instead of 4 lines. Should it be put -BEGIN PUBLIC KEY- CR \ ABC123 CR \ DEF456 CR \ -END PUBLIC KEY- into myVar ?? -- Alex. ___ 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
Re: multi-line constants? (for RSA keys)
On Sat, Mar 22, 2014 at 5:35 PM, Alex Tweedly a...@tweedly.net wrote: constant doesn't allow any form of expression, you can't even do constant mykey = abc def *sigh* I was hoping that was doing something wrong. A clean solution ? - assign to a variable instead This is what I've been doing - custom prop - since you're generating it externally - put it in a fixed-name file, and have your script read that file in But then it would be readable :) btw if I take the above code, and convert from using a constant to a variable, I'd get put -BEGIN PUBLIC KEY- \ ABC123\ DEF456\ -END PUBLIC KEY- into myVar but that means it's become a single line, instead of 4 lines. Should it be put -BEGIN PUBLIC KEY- CR \ ABC123 CR \ DEF456 CR \ -END PUBLIC KEY- into myVar Yes, I blew that typing it in . . . -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 ___ 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
