My mistake. I was limiting my thinking to what is returned by cipherNames().
On May 15, 2013, at 2:37 PM, Dr. Hawkins wrote:
> On Wed, May 15, 2013 at 12:58 PM, Dar Scott wrote:
>
>> Unless something exotic has been added recently, they all are, in the
>> sense that you use the same key (and
On Wed, May 15, 2013 at 12:58 PM, Dar Scott wrote:
> Unless something exotic has been added recently, they all are, in the
> sense that you use the same key (and seed or IV, if used) for decrypting as
> you use for encrypting.
RSA is in there now . . .
--
Dr. Richard E. Hawkins, Esq.
(702) 5
On May 14, 2013, at 6:43 PM, Dr. Hawkins wrote:
> And whyle I'm asking such things, is one of the ciphers on livecode's list
> symmetrical?
Unless something exotic has been added recently, they all are, in the sense
that you use the same key (and seed or IV, if used) for decrypting as you use
Dr. Hawkins, I apologise for coming in late to this discussion, but let me see
if I can be of some assistance.
SYMMETRICAL encryption has 1 main purpose, which is to 'hide' data in an
encrypted format.
ASYMMETRICAL encryption, on the other hand, has 2 purposes: hide data, and
*sign* the data -
On May 14, 2013, at 5:43 PM, Dr. Hawkins wrote:
> On Tue, May 14, 2013 at 3:22 PM, kee nethery wrote:
>
>> There is nothing insecure about a symmetrical key. The insecurity with a
>> symmetrical key is that both people have to know it and getting it from
>> person A to person B safe and secure
On Tue, May 14, 2013 at 3:22 PM, kee nethery wrote:
> There is nothing insecure about a symmetrical key. The insecurity with a
> symmetrical key is that both people have to know it and getting it from
> person A to person B safe and secure is difficult. The public private key
> pair handles the t
On May 14, 2013, at 3:09 PM, Dr. Hawkins wrote:
> On Tue, May 14, 2013 at 2:08 PM, kee nethery wrote:
>
>> You embed your public RSA key into your app.
>> You pick a random symmetrical key and encrypt your payload using that key.
>> You encrypt the random symmetrical key with your private RSA
On Tue, May 14, 2013 at 2:08 PM, kee nethery wrote:
> You embed your public RSA key into your app.
> You pick a random symmetrical key and encrypt your payload using that key.
> You encrypt the random symmetrical key with your private RSA key.
> You append the encrypted random key to your encrypt
You embed your public RSA key into your app.
You pick a random symmetrical key and encrypt your payload using that key.
You encrypt the random symmetrical key with your private RSA key.
You append the encrypted random key to your encrypted payload and send that to
the customer.
You extract the enc
In earlier discussions, I had pretty much settled on using an RSA key pair
for my licensing (particularly, for per use licensing), giving the public
key to the user and retaining the private key.
It just occurred to me, though: given that this lets them decrypt the
entire license payload, which i
10 matches
Mail list logo
