This wiki has been migrated to and is now deprecated. Please use that site instead.
Differences between revisions 20 and 22 (spanning 2 versions)
Revision 20 as of 2006-04-25 13:14:04
Size: 2059
Editor: JoergMayer
Comment: mark 0.99.0 as released
Revision 22 as of 2006-04-26 19:43:37
Size: 2719
Editor: GeraldCombs
Deletions are marked like this. Additions are marked like this.
Line 26: Line 26:
  * Add GNU TLS and libgcrypt to the Windows installer  * Add GNU TLS and libgcrypt to the Windows installer
 * Fix blocker bugs:
  * [ 396] - Saving flow data crashes Ethereal
  * [ 699] - "Order" buttons not working properly in Coloring Rules window
  * [ 757] - Crashes when multiple tap interfaces exist

 * Fix blocker bugs:
  * [ 852] - Follow TCP stream crashes on particular data with X Window System error
  * [ 886] - Ethereal crashes whenever user tries to rearrange columns


This is a tentative roadmap for stable releases of Ethereal up to 1.0 and beyond. It is by no means final, and there is no timeline.



  • April 24, 2006


  • None.


  • Fix security-related Coverity bugs
  • Add some reasonable example files for filters, rules, .... (Done in 14595)
  • Fix Bugzilla "blocker" bugs
  • Updated Lua for Windows. (GNU TLS/libgcrypt will be added pending an ECCN assignment from the U.S. Department of Commerce)






  • Version checking.
  • Windows updater.
  • TCP reassembly updates



  • Use the "User's Guide" as the online help system for Ethereal releases
  • Finish TCP reassembly



  • make plugin ABI stable, so binary plugins will be working with more than one Ethereal version

Beyond V1.0

  • Finish the native Windows interface and integrate it with the main trunk
  • Make the capture filter syntax the same as the display filter syntax?
  • Add privilege separation for dissection
  • Add thread/multiprocessor support

... well, maybe all the points mentioned in the WishList!


  • Security improvements (see also: ["Security"])
    • Add privilege separation for POSIX environments (in progress)
    • Add a similar mechanism for the Windows environment
    • Enhance the API to make it easier to write secure code (e.g. add tvb_get_gstring())?
  • Documentation of library API's (e.g. wiretap)
  • Make some of the plugins regular dissectors?


That ECCN looks like a no-brainer to me: Network analyzers . . . . . . . . . . 3A002.e

The lady I spoke with at the BIS seemed to think that we'd still have to comply with the encryption section of the EAR -- Gerald

Development/Roadmap (last edited 2020-07-03 15:42:04 by GeraldCombs)