#8937: Implementation of AES with different key sizes
-----------------------------------------------------------------------------+
Reporter: amca01 |
Owner: amca01
Type: enhancement |
Status: needs_info
Priority: minor |
Milestone: sage-feature
Component: cryptography |
Keywords: AES
Work_issues: Currently there are a lot of doctest fails, I don't know why. |
Upstream: N/A
Reviewer: |
Author: Alasdair McAndrew
Merged: |
Dependencies:
-----------------------------------------------------------------------------+
Changes (by kini):
* status: new => needs_info
Comment:
On lines 12 and 13 of your file, you say that this is already implemented
in Sage. May I ask what the benefit of your code is over the current
implementation, then?
By the way, if you would like to contribute code to Sage, please generate
a patch file against the Mercurial repository in `$SAGE_ROOT/devel/sage/`
. The code should be either added to an existing `.py` or `.pyx` file, or
in a new `.py` or `.pyx` file, somewhere in `$SAGE_ROOT/devel/sage`,
rather than in a `.sage` file.
I also notice that there is another version of `aes.sage` that you
uploaded to the wiki page TracTickets (in fact that's how I came across
this ticket). Can that one be ignored/deleted? It's older than the one
you've uploaded to this ticket.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8937#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
