EldoS | Feel safer!

Software components for data protection, secure storage and transfer

input too long

Also by EldoS: CallbackRegistry
A component to monitor and control Windows registry access and create virtual registry keys.
Posted: 10/14/2009 05:27:54
by Mykola Olshevsky (Basic support level)
Joined: 07/07/2005
Posts: 450

As I told, such encryption scheme doesn't make any sense - public exponent, which you are using for decryption is the same for all RSA keys (65537).
However, SecureBlackbox supports this as well.
Posted: 10/14/2009 05:44:45
by Eugene Mayevski (EldoS Corp.)

Joao Santos wrote:
I'm sorry, but I've always used that kind of schema.

You always misused cryptography. Please check one of these books for detailed information.

Sincerely yours
Eugene Mayevski
Posted: 10/14/2009 08:02:42
by Joao Santos (Standard support level)
Joined: 10/07/2009
Posts: 12

Yes, it looks like you are right... damn Lockbox :)


In an asymmetric key encryption scheme, anyone can encrypt messages using the public key, but only the holder of the paired private key can decrypt. Security depends on the secrecy of that private key.

In some related signature schemes, the private key is used to sign a message; but anyone can check the signature using the public key. Validity depends on private key security.

Just one question, I was mainly using the RSA for a simple registration schema, where I generated both keys, the client was using the Public Key and my Key Generation was using the private key to generate the license.

According to this, now I must do the exact opposite, (KeyGen with public Key and client with the private). Is this correct?
Posted: 12/17/2009 12:51:58
by Ami Goldi (Basic support level)
Joined: 12/09/2009
Posts: 3

SecureBlackBox doesn't allow attached signing of data using ElRSAPublicKeyCrypto object, only detached. However, you can use low level SBRSA.Decrypt function to accomplish this.

Also, you could increase the size of your private key to accommodate encrypting larger data. I ran into a similar problem where my shared secret was just over 128 bytes, so I used a 2048 bit key.



Topic viewed 4501 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS Corporation will operate as a division of /n software inc. For more information, please read the announcement.

Got it!