I can't help this guy, I don't understand what he is planning to do, so
someone else might give it a try. It sounds like a signature check on a
signed nonce or something.
Can't help you Leo unless you either happen to speak German or work on
your English, big time. Maybe it makes sense to draw some image showing
what the client does and what the server does, I don't know. :/ I mean
there is "I" then there is "user" as well as "application". Is the
application running at your server("I")? Or at the clients("user")
system? Who has the private key, and who the public? Are you trying to
implement a simple challenge-response pattern? Is the client challenging
the server, or the server challenging the client?
Greets Elias
On 2/9/11 2:11 AM, Leo Mifare wrote:
Hi Elias,
Yes. I think this is rarely used.
Actually, my need is I want to separate "unique data" (which encrypted
with my PrivateKey) for each user, so whenever user authenticate to my
application, i will check the "unique data" (decrypted with my
PublicKey) , and verify the format. If the format is wrong, means
verification is failed then authentication is failed.
The unique data is formatted, so whenever i want to encrypt / create
"unique data" and decrypt / verify "unique data", the data format is
constructed and checked. Every step to create and verify "unique
data" have to comply to Unique Data Format.
And actually the Public Key is not 100% Real Public, i only want
distribute the Public Key for my "branches".
RSA Key size that i want to use is 1024 bits.
Please help me regarding this.
Thanks,
Leo
On Tue, Feb 8, 2011 at 5:56 PM, Elias Önal <[email protected]
<mailto:[email protected]>> wrote:
Hey,
why do you want to encrypt data using the private key? That
process is usually known as "signing" and you should be really
careful doing so. In some cases it might even break the algorithm
when done wrong! *cough* ElGamal *cough* *cough*
Greets Elias
--
You received this message because you are subscribed to the
"Crypto++ Users" Google Group.
To unsubscribe, send an email to
[email protected]
<mailto:[email protected]>.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
