This wiki has been migrated to https://gitlab.com/wireshark/wireshark/-/wikis/home and is now deprecated. Please use that site instead.
Differences between revisions 67 and 68
Revision 67 as of 2006-08-30 11:34:36
Size: 3488
Editor: cacher6
Comment: Add a link to coverity
Revision 68 as of 2006-10-10 15:27:43
Size: 3633
Editor: GeraldCombs
Comment: Add bug 1096.
Deletions are marked like this. Additions are marked like this.
Line 66: Line 66:
 * [http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1096 1096] - Wireshark fails to start on Windows when it can't acquire a crypto context.

Roadmap

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

0.99.0

Released:

  • April 24, 2006

Pending:

  • None.

Complete:

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

0.99.1

The 0.99.1 release has been abandoned, as discussed in [http://www.wireshark.org/lists/wireshark-dev/200607/msg00001.html this thread] on the wireshark-dev list.

0.99.2

Released:

  • July 17, 2006

Pending:

  • None.

Complete:

0.99.3

Released

  • Aug 23, 2006

Pending:

  • None.

Complete:

0.99.4

Pending:

Complete:

1.0

Pending:

  • make plugin ABI stable, so binary plugins will be working with more than one Wireshark 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!

Unsorted

  • 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?
  • Solve the Preferences/Filter "Save" button confusion. That's the last one on my "personal GUI list" that's regular confusing newbies IMHO. Maybe it's simply solved by adding a Preference setting "Explicit saving changes" which defaults to off. UlfLamping

Discussion

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)