Talk:RSA code: Difference between revisions

(→‎Solutions are starting to diverge: more on how to get to new/modified task)
Line 36:
::* 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.
:::''In the general case, block size for encoded text, represented as text, will need to be at least 1 character larger than the unencrypted text. And 1 character is only possible when the block size was picked to be the largest possible for N. (And there is also the issue of determining the original message length -- humans can maybe ignore padding but our programs are easily confused)'' --[[User:Rdm|Rdm]] 14:00, 27 April 2011 (UTC)
::* 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
Line 56 ⟶ 57:
:: 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? Do we copy to new and mark the others incorrect? Erasmus?
:: --[[User:Dgamey|Dgamey]] 11:04, 27 April 2011 (UTC)
 
:::I think the first thing to do is create a category (or maybe categories?) for these tasks. Then mark this task with that category. Then do up some draft task pages and see if they attract interest. I think that this one can be cleaned up, later, perhaps after we have had some practice with formulating tasks related to encryption, or perhaps by the original author. --[[User:Rdm|Rdm]] 14:00, 27 April 2011 (UTC)
 
===Split the task?===
6,951

edits