Talk:RSA code: Difference between revisions

Line 28:
:* These are just ideas to toss around. I'll happily change my code to match whatever the task settles on.
: —[[User:Sonia|Sonia]] 05:22, 27 April 2011 (UTC)
 
:: Now this is a good discussion about drafts :)
 
:: I like the size of the number. Big enough to test bignums and small enough to fit within the margins. BTW if you try just plain bignum m^e%n your bignums may choke even with this one.
:: Where did you get you numbers from BTW?
:: You just choose ASCII encoding - the new/modified task would need to say so.
:: Any encryption task will need a disclaimer on the page (demonstration numbers, key to short, lack of random padding, not to mention subtle attacks if e is chosen improperly.
:: Blocking could be done in a another task. It's needed if m > n. And in the particular cases of the original task where the character encoding is sparse 30+ chars into 100s the decoding will blow up. With ASCII encoding it doesn't blow up but you get gibberish.
:: An RSA/keygen task would be another good task. There are even subtasks possible within that.
:: A general character encoding and blocking task would be good
:: An RSA/129 task might be good. But the 80 column limit would have to be forgiven OR use files and a formats output to "12345 .... 9999" with dots to some fixed width
:: Not overly interested in doing PKCS#n too.
:: It's useful to see the interim products. I liked that.
:: It may be useful to show the concept of signing, decrypting a message, than anyone can encrypt to get the plain text. But that was part of RSA 129 challenge so maybe better left to that task. Again, real signing is more complex.
:: How about (in summary) the new/modified task is something like this:
::: To Encrypt and Decrypt a short message or two using RSA with a demonstration key (we should all use the same one)
::: Simple ASCII encoding and decoding of the message
::: Give an error if m > n (i.e. would require blocking)
::: Exercise large integer support or libraries (no need to include, just reference unless they were purpose written for this task)
::: Show intermediate results
::: No UI - it should be a separate non-crypto tasks, hard code or simple input
::: Background on RSA
::: Dislaimer about real crypto
 
:: I'll post some code that follows your example. But it won't be until at least this evening.
 
:: How do we get a consensus on this? I don't like stealing a task and would like to hear from the Author. Would we create a new task and put something very visible up front in this saying something about it? Would we rename this to RSAdraftprototype or some such? Erasmus?
:: --[[User:Dgamey|Dgamey]] 11:04, 27 April 2011 (UTC)
 
===Split the task?===
Anonymous user