Difference between revisions of "Category:OWASP EnDe RoadMap"

From OWASP
Jump to: navigation, search
(initialization)
(more requirements)
Line 1: Line 1:
 
 
;Abstarct
 
;Abstarct
 
EnDe consist of two parts: the core library (API) and the browser interface (GUI). The issues are mapped to either of these categories.
 
EnDe consist of two parts: the core library (API) and the browser interface (GUI). The issues are mapped to either of these categories.
Line 9: Line 8:
 
=== API ===
 
=== API ===
 
* implementing sha384, sha512 encryption
 
* implementing sha384, sha512 encryption
* implementing other encryptions like Adler, ...
+
* 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
 
* building an object oriented API beside the existing procedural API
  

Revision as of 09:25, 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.

Contents

Current State

EnDe is currently (5/2008) stable according the offered functionality.

Pending or Planed Requirements / Improvements

API

  • 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.