Ethereal-dev: Re: [Ethereal-dev] Suppport inhouse use

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Wed, 31 Aug 2005 17:31:32 +0200
On Wed, Aug 31, 2005 at 02:40:14PM +0200, Thomas Boehne wrote:
> On Wednesday 31 August 2005 14:00, Jaap Keuter wrote:
> > With the risk of getting flamed I want to float this idea. Currently
> > Ethereal can 'leak' information to the world by refering back to the
> > Wiki as online protocol reference.
> 
> I patched my gtk/main.c to redirect accesses for my own plugins to our
> local Wiki, which works quite well. However, it would be nicer if
> there was an API to set the URL from the plugin code (thus allowing
> each plugin to have it's own URL). So instead of adding a boolean
> field hfinfo->proprietary I would add a pointer to a URL (which should
> default to wiki.ethereal.com, if unset).

I'm stronly against either solution.
a) I'm no fan of proprietary stuff and if people really feel like using
   them then they should patch their version of ethereal - either we
   put the dissector into ethereal - that's fine, or we don't. But I see
   no reason *at all* to fix problems that may only occur if people use
   proprietary dissectors.
b) Making the URL configurable we forster private clones of the wiki that
   will quite likely be "enhanced" even on "public" dissectors.

 ciao
       Joerg
-- 
Joerg Mayer                                           <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.