One of the problems with #3 and above is the people who
want your code will probably spend more money and time
figuring out a way to steal the uncompiled code than they
would spend trying to hack the code.
And they most likely have a lot of corrupt connections and
money to spend.
JB
> On Jan 6,
I agree. It's easy to imagine that one can acheive absolute security, but in
practice it is impossible by nature. Just someone standing over your shoulder
or putting a spy camera in place is all that would be needed. The idea then is
to make it as difficult and impractical as possible given the
Inputs often pose a bigger risk than core dumps.
Where you ask:
"Any suggestions to make it as secure as possible?"
...we might instead ask:
"Any suggestions to make it as secure as *practical*?"
...or even:
"Any suggestions to make it as secure as *cost-effective*?"
There are always ways to m
That is a very interesting question!
If the user enters the password or did I hardcode a password
so what follows can only be executed if it included the text I
put into the variable.
I am in this case hardcoding it in myself. This could be text
that is encrypted but it is still there even befor
How does the password come into the variable?
--
Richard Gaskin
Fourth World Systems
JB wrote:
What if I have secure info like a password stored
in a local variable and then I clear that info by
putting empty into that local variable.
How secure is that procedure? I understand a
local varia
It seems I really do not need to worry too much because
if I understood it correctly the memory of the variable at
the end of the execution of that code is not only released
but it is also deleted. Since the variable I am concerned
about is used at the end of the code it does not exist after
I use
I was going to say also that unless the script was in a protected stack, it
WOULD be very trivial to install Livecode, put a breakpoint just before where
you delete the variable, then do a memory dump at that point.
Bob S
> On Jan 3, 2020, at 12:58 , Bob Sneidar via use-livecode
> wrote:
>
Well its really about what is going on under the hood. Memory dump for Macs is
not trivial from what I read. Apparently it involves turning off system
integrity and then booting into a special mode. At that point I stopped
reading. Not something I care to do with a production system.
Bob S
I have it figured out.
You use it to delete each element of the array and
that is the same as writing null to each element of
the variable.
I think they mean if you do not delete each element
using this method all you are doing is putting empty
into the variable and that would be the same as if
y
Is there a easy way to do a memory dump in Livecode?
Can I read the blocks of only memory for that variable?
In c the blocks are a array numbered from 0 to the size
of the variable which would be the length of the variable
in Livecode and you can access individual blocks and
that is how you write a
I think a memory dump and search of the contents is about the only thing you
can do to be sure.
Bob S
> On Jan 3, 2020, at 11:11 , JB via use-livecode
> wrote:
>
> Hi Bob,
>
> yeah, I am not sure exactly what it means either.
> Different ways of doing the same thing?
>
> JB
___
Hi Bob,
yeah, I am not sure exactly what it means either.
Different ways of doing the same thing?
JB
> On Jan 3, 2020, at 11:09 AM, Bob Sneidar via use-livecode
> wrote:
>
> I'm not sure what this means. When you use delete variable on a script local,
> it clears the contents of the variab
I'm not sure what this means. When you use delete variable on a script local,
it clears the contents of the variable, but the variable still exists, that is
if you can use the Script Editor variable watcher as any kind of irrefutable
evidence.
Bob S
> On Jan 3, 2020, at 11:04 , JB via use-li
Hi Tom,
Thanks for the fast reply & info!
That was an interesting link. Here are a
few lines from the link,
--
The delete variable command not only removes the contents of the variable, but
deletes it entirely from memory. If you delete a key from an array variable,
that element of th
A memory dump can reveal everything stored in memory for a particular
process.
the delete variable command is what you are looking for.
https://livecode.fandom.com/wiki/Delete_variable
On Fri, Jan 3, 2020 at 1:22 PM JB via use-livecode <
use-livecode@lists.runrev.com> wrote:
> What if I have
15 matches
Mail list logo
