By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,677 Members | 1,094 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,677 IT Pros & Developers. It's quick & easy.

error: "illegal key size..." thrown when encrypt with RSA

P: n/a

Hello everyone:

I am using vb.net 2003, sqlserver2000 database, and windows 2000
professional OS.

In the program, I encrypt the login user's userid and passed with
RSACryptoServiceProvider. It is work fine in my compute,

but when i set up it on the client computer(which have assembled IE6.0 SP1,
..net framework 1.1 and MDAC 2.7. and the

crytion key displayed in the IE help is 128-bit), it always throw
error:"illegal key size for this algorithm".

Appreciate for any help!!

Thanks in advance!!!
Thanks

cqe

Jul 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
When you get "illegal key size for this algorithm" for the encrypted login,

that is actually the encryped login. There is about a 1 in 10 billion
chance that the encrypted login would actually be a readable sentence, but
there you go.

Count yourself lucky!
"qe_Cui" <qe****@rtisoftware.com> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl...

Hello everyone:

I am using vb.net 2003, sqlserver2000 database, and windows 2000
professional OS.

In the program, I encrypt the login user's userid and passed with
RSACryptoServiceProvider. It is work fine in my compute,

but when i set up it on the client computer(which have assembled IE6.0 SP1, .net framework 1.1 and MDAC 2.7. and the

crytion key displayed in the IE help is 128-bit), it always throw
error:"illegal key size for this algorithm".

Appreciate for any help!!

Thanks in advance!!!
Thanks

cqe

Jul 21 '05 #2

P: n/a
Jeff Clark <JeffC@NO_SPAMreturnventures.com> wrote:
When you get "illegal key size for this algorithm" for the encrypted login,

that is actually the encryped login. There is about a 1 in 10 billion
chance that the encrypted login would actually be a readable sentence, but
there you go.

Count yourself lucky!


No, I don't think that's likely to be it. If it's throwing an
exception, that's very different from the result just happening to be
that sentence.

To the OP: Can you come up with a short but complete program which
demonstrates the problem?

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too
Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.