This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Category:OWASP EnDe RoadMap"
From OWASP
(more requirements) |
(API doc) |
||
| Line 7: | Line 7: | ||
== Pending or Planed Requirements / Improvements == | == Pending or Planed Requirements / Improvements == | ||
=== API === | === API === | ||
| + | * generating some documentation | ||
* implementing sha384, sha512 encryption | * implementing sha384, sha512 encryption | ||
* implementing more hashes like Adler-32, Ghost, Haval, Tiger, ... | * implementing more hashes like Adler-32, Ghost, Haval, Tiger, ... | ||
Revision as of 14:39, 23 June 2008
- Abstarct
EnDe consist of two parts: the core library (API) and the browser interface (GUI). The issues are mapped to either of these categories.
Current State
EnDe is currently (5/2008) stable according the offered functionality.
Pending or Planed Requirements / Improvements
API
- generating some documentation
- implementing sha384, sha512 encryption
- implementing more hashes like Adler-32, Ghost, Haval, Tiger, ...
- implementing more encryptions like BlowFish, CAST, DES, TrippleDES, GOST, Loki97, RC2, SaferPlus, Serpent, TwoFish
- implementing codings like UTF-EBCDIC
- building an object oriented API beside the existing procedural API
GUI
- replace the hardcoded dispatcher with a generated one
Fixed / Completed
(will be added as needed;-)
This category currently contains no pages or media.
