Folks,
A stack that demonstrates the various kinds and best practices for encryption
would be very useful, as the privacy issue has become so important. When I get
encrypted communication with a server worked out, I’ll post my findings for
feedback from those more knowledgeable. Examples of
A salt is simply a string you use to "seed" the hash to make it more difficult
to decrypt using rainbow tables or brute force. The decrypting end must also
know your salt string to decrypt it.
Bob S
> On Jun 6, 2018, at 14:16 , prothero--- via use-livecode
> wrote:
>
> I’ve been having
THAT I didn't know! I'm using reversible encryption for my stored passwords!
DOH! I'll fix that right away.
Bob S
> On Jun 6, 2018, at 22:10 , Brian Milby via use-livecode
> wrote:
>
> One big difference is that encrypt is reversible and messagedigest is not.
> Generally for password
Correct
On Jun 7, 2018, 10:01 AM -0500, proth...@earthlearningsolutions.org , wrote:
> Folks,
> What I get out of this is, for password protection, you use hashed encryption
> where you don’t need to return the original password. Only the hashed
> password is used to validate the login.
>
>
Hi all.
I just noticed by accident I can use something like this and it works:
dispatch populateRecord to group cDGName of stack cSubStack
cDGName is "dgDevices" and cSubstack is "Devices". Notice the absence of a card
reference! Apparently, even though the owner of the datagrid group is the
Argh. I thought I solved in this in my app. But LO... it appears to quit...
but is actually not quitting... it leaves a "corrupt" stack on the phone
(android) and when you try to restart it, it opens to splash screen stack, but
no messages are firing. It is "stuck" ; does not appear to user
Okay I think I get it. I noticed the beginning of the hash contained "Salted__"
but I didn't know why! Are you saying I can strip that along with the next 8
bytes, and the hash will be intact, and I can decrypt it without the salt??
Bob S
> On Jun 6, 2018, at 21:06 , Brian Milby via
Folks,
What I get out of this is, for password protection, you use hashed encryption
where you don’t need to return the original password. Only the hashed password
is used to validate the login.
However, if you need to recover the original encrypted text, like for an sql
query that you sent to
Yes indeed, it references the datagrid on the currentCard! If there is no such
object on the current card, then even if there is one on another card that is
not the currentCard, it throws an error, as you would expect!
That is actually quite cool.
Bob S
> On Jun 7, 2018, at 08:54 , Bob
If you strip the first 16 bytes then you must provide the salt to decrypt. If
you leave the salt, then you just need the password to decrypt.
On Jun 7, 2018, 9:45 AM -0500, Bob Sneidar via use-livecode
, wrote:
> Okay I think I get it. I noticed the beginning of the hash contained
> "Salted__"
This is not an easy thing to fix and can be broken easily. The app in memory is
not corrupt but the restart of the app is probably exposing an LC engine bug.
Details for geeks...
To handle the Android unique app restart protocol: After you "Quit" or the app
gets hibernated so to speak by the
When I first reported it, the problem was that the quit command unloaded
all the libraries but left the app in memory. Sounds like what you see now.
In my app it just crashes, but probably for the same reason.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software |
It could be solved if we had suspend and resume messages but I heard this
is difficult to implement on Android.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On June 7, 2018 12:49:10 PM Ralph DiMola via use-livecode
wrote:
This is
yeah it is Bob.its one of the reasons why livecode is so flexible and
such a joy to work with.
On Thu, Jun 7, 2018 at 12:00 PM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Yes indeed, it references the datagrid on the currentCard! If there is no
> such object on
On Tue, Jun 5, 2018 at 12:36 PM, Ralf Bitter via use-livecode <
use-livecode@lists.runrev.com> wrote:
>
> Unfortunately I am observing an annoying screen flicker
> during the startup sequence while the UI stack is opened
> and the Levure standalone is closed.
> The iOS splash screen, as defined
Cool!
On Thu, Jun 7, 2018 at 5:08 PM, David Epstein via use-livecode <
use-livecode@lists.runrev.com> wrote:
> While trying Mike Bonner's suggestion of "manual" measuring, I learned the
> answer: a regular polygon whose official length is L and width is W is
> inscribed in the oval whose length
While trying Mike Bonner's suggestion of "manual" measuring, I learned the
answer: a regular polygon whose official length is L and width is W is
inscribed in the oval whose length is L and width is W. So for an equilateral
triangle the area will be 3/4 * 3^.5 * R^2 (where R = L = W).
David
I've made a brief demo stack that shows one way of handling passwords.
https://github.com/bwmilby/lc-misc/tree/master/PasswordDemo
I used my ScriptTracker to export the actual scripts and make them
available to view online. I also included an image of the stack layout. I
used MD5 for the hash
Thanks, Brian.
Bill
William Prothero
http://ed.earthednet.org
> On Jun 7, 2018, at 8:29 PM, Brian Milby wrote:
>
> I've made a brief demo stack that shows one way of handling passwords.
> https://github.com/bwmilby/lc-misc/tree/master/PasswordDemo
>
> I used my ScriptTracker to export the
On 2018-06-06 22:29, Bob Sneidar via use-livecode wrote:
I do the same thing, but if they can get to your code, they can
discern how you get your salt.
Yes - essentially - although I did miss out making one important
point...
If you are using community (i.e. GPL) then there is nothing you
20 matches
Mail list logo
